From 2312a389fc907111756b247ce1ed8f29ce267bb4 Mon Sep 17 00:00:00 2001 From: "Thingvall, Nils" Date: Thu, 30 Apr 2026 11:24:26 -0600 Subject: [PATCH 1/6] Added notes about CAF applications and the addition of the MPL app. --- .../06-chromecast/01-chromecast-app-customization.md | 4 ++-- .../01-chromecast/06-enable-chromecast-on-the-sender.md | 6 ++++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md b/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md index a4b76d06d4a0..cb989d2942f5 100644 --- a/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md +++ b/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md @@ -108,9 +108,9 @@ your application is buffering or paused. ### Default Receiver application -If you are connected to THEOplayer's default Receiver application, you cannot modify its appearance. +If you are connected to THEOplayer's default Receiver application, you cannot modify its appearance. It is an application with THEOplayer functionality that uses Shaka for media playback. -If you want to change the UI, you need to [connect your sender application with a different Receiver application ID](../../../how-to-guides/03-cast/01-chromecast/01-connecting-from-custom-sender-applications.md). +If you want to change the UI, you need to [connect your sender application with a different Receiver application ID](../../../how-to-guides/03-cast/01-chromecast/01-connecting-from-custom-sender-applications.md). Also if you need to use Google's legacy Media Player Library (MPL) for playback, you will need to change the Receiver application ID. ### Custom Receiver application with THEOplayer Chromecast SDK diff --git a/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md b/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md index e2837a0e39e7..f1339280c2ad 100644 --- a/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md +++ b/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md @@ -20,7 +20,7 @@ The JavaScript snippet below illustrates how you include this Sender SDK. You ca ``` -Once this SDK is imported, THEOplayer will automatically add the Chromecast casting capability to your player (if you've enabled the Chromecast feature for your THEOplayer SDK). +Once this SDK is imported, THEOplayer will automatically add the Chromecast casting capability to your player (if you've enabled the Chromecast feature for your THEOplayer SDK). THEOplayer will use its default Chromecast receiver application if you do not specify an `appID` value on the configuration. ### Android SDK @@ -203,7 +203,7 @@ In order to enable Chromecast on the iOS SDK: ## Connect with custom Chromecast Receiver application {#custom-receiver-app} The THEOplayer SDK on your Sender application connects with THEO Chromecast Receiver application by default, -but you can connect it to a custom Chromecast Receiver application instead. +but you can connect it to a custom Chromecast Receiver application instead. The default THEO Chromecast Receiver application has THEOplayer functionality, but uses Shaka for media playback. If you want to use Google's legacy Media Player Library (MPL) for playback, you will need to use either a custom application or connect to THEO's MPL Receiver application. Note that the MPL receiver does not support HLS-CMAF streams. ### Web SDK @@ -222,6 +222,8 @@ let player = new THEOplayer.Player(element, { }); ``` +If you do not specify an `appID` value, the player will cast to the default THEOplayer Chromecast application. This is a Receiver application that has THEOplayer functionality integrated into it, but uses the Shaka player for media playback. If you require a Receiver application that uses Google's legacy Media Player Library (MPL), there is a Receiver application with THEOplayer functionality that uses MPL. Note that the MPL receiver does not support HLS-CMAF streams. + ### Android SDK To connect with a custom Chromecast Receiver application, you can create your own `CastOptionsProvider` by subclassing `com.google.android.gms.cast.framework.OptionsProvider` and implementing the `getCastOptions` method. From 6d44df35088d6afb5c8b6b3306025c5959a84dd6 Mon Sep 17 00:00:00 2001 From: "Thingvall, Nils" Date: Mon, 4 May 2026 09:22:11 -0600 Subject: [PATCH 2/6] Added MPL-only appID --- .../01-sdks/06-chromecast/01-chromecast-app-customization.md | 2 +- .../01-chromecast/06-enable-chromecast-on-the-sender.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md b/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md index cb989d2942f5..94f0c15f6b52 100644 --- a/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md +++ b/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md @@ -110,7 +110,7 @@ your application is buffering or paused. If you are connected to THEOplayer's default Receiver application, you cannot modify its appearance. It is an application with THEOplayer functionality that uses Shaka for media playback. -If you want to change the UI, you need to [connect your sender application with a different Receiver application ID](../../../how-to-guides/03-cast/01-chromecast/01-connecting-from-custom-sender-applications.md). Also if you need to use Google's legacy Media Player Library (MPL) for playback, you will need to change the Receiver application ID. +If you want to change the UI, you need to [connect your sender application with a different Receiver application ID](../../../how-to-guides/03-cast/01-chromecast/01-connecting-from-custom-sender-applications.md). Also if you need to use Google's legacy Media Player Library (MPL) for playback, you will need to change the Receiver application ID to `44BAE7D1`. ### Custom Receiver application with THEOplayer Chromecast SDK diff --git a/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md b/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md index f1339280c2ad..35f3da753bea 100644 --- a/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md +++ b/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md @@ -203,7 +203,7 @@ In order to enable Chromecast on the iOS SDK: ## Connect with custom Chromecast Receiver application {#custom-receiver-app} The THEOplayer SDK on your Sender application connects with THEO Chromecast Receiver application by default, -but you can connect it to a custom Chromecast Receiver application instead. The default THEO Chromecast Receiver application has THEOplayer functionality, but uses Shaka for media playback. If you want to use Google's legacy Media Player Library (MPL) for playback, you will need to use either a custom application or connect to THEO's MPL Receiver application. Note that the MPL receiver does not support HLS-CMAF streams. +but you can connect it to a custom Chromecast Receiver application instead. The default THEO Chromecast Receiver application has THEOplayer functionality, but uses Shaka for media playback. If you want to use Google's legacy Media Player Library (MPL) for playback, you will need to use either a custom application or connect to THEO's MPL Receiver application, using the `appID` value of `44BAE7D1`. Note that the MPL receiver does not support HLS-CMAF streams. ### Web SDK @@ -222,7 +222,7 @@ let player = new THEOplayer.Player(element, { }); ``` -If you do not specify an `appID` value, the player will cast to the default THEOplayer Chromecast application. This is a Receiver application that has THEOplayer functionality integrated into it, but uses the Shaka player for media playback. If you require a Receiver application that uses Google's legacy Media Player Library (MPL), there is a Receiver application with THEOplayer functionality that uses MPL. Note that the MPL receiver does not support HLS-CMAF streams. +If you do not specify an `appID` value, the player will cast to the default THEOplayer Chromecast application. This is a Receiver application that has THEOplayer functionality integrated into it, but uses the Shaka player for media playback. If you require a Receiver application that uses Google's legacy Media Player Library (MPL), there is a Receiver application with THEOplayer functionality that uses MPL. Its `appID` is `44BAE7D1`. Note that the MPL receiver does not support HLS-CMAF streams. ### Android SDK From 500b52f5fb51b3309c6ea0412efb823a54dcecab Mon Sep 17 00:00:00 2001 From: Nils Thingvall Date: Tue, 5 May 2026 09:10:23 -0600 Subject: [PATCH 3/6] Update theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md Co-authored-by: Fabien Lavocat <4154532+FabienLavocat@users.noreply.github.com> --- .../01-sdks/06-chromecast/01-chromecast-app-customization.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md b/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md index 94f0c15f6b52..ae24c45f3e21 100644 --- a/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md +++ b/theoplayer/getting-started/01-sdks/06-chromecast/01-chromecast-app-customization.md @@ -108,7 +108,7 @@ your application is buffering or paused. ### Default Receiver application -If you are connected to THEOplayer's default Receiver application, you cannot modify its appearance. It is an application with THEOplayer functionality that uses Shaka for media playback. +If you are connected to OptiView Player's default Receiver application, you cannot modify its appearance. It is an application with OptiView Player functionality that uses Shaka for media playback. If you want to change the UI, you need to [connect your sender application with a different Receiver application ID](../../../how-to-guides/03-cast/01-chromecast/01-connecting-from-custom-sender-applications.md). Also if you need to use Google's legacy Media Player Library (MPL) for playback, you will need to change the Receiver application ID to `44BAE7D1`. From 80bcc74836100423db14e66e0e1c4c4119f4c98e Mon Sep 17 00:00:00 2001 From: Nils Thingvall Date: Tue, 5 May 2026 09:10:43 -0600 Subject: [PATCH 4/6] Update theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md Co-authored-by: Fabien Lavocat <4154532+FabienLavocat@users.noreply.github.com> --- .../03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md b/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md index 35f3da753bea..9f55a15a94f5 100644 --- a/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md +++ b/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md @@ -20,7 +20,7 @@ The JavaScript snippet below illustrates how you include this Sender SDK. You ca ``` -Once this SDK is imported, THEOplayer will automatically add the Chromecast casting capability to your player (if you've enabled the Chromecast feature for your THEOplayer SDK). THEOplayer will use its default Chromecast receiver application if you do not specify an `appID` value on the configuration. +Once this SDK is imported, OptiView Player will automatically add the Chromecast casting capability to your player (if you've enabled the Chromecast feature for your OptiView Player SDK). OptiView Player will use its default Chromecast receiver application if you do not specify an `appID` value on the configuration. ### Android SDK From 723dfbe8f06c1912f6fa4fe4530f639f575e3dab Mon Sep 17 00:00:00 2001 From: Nils Thingvall Date: Tue, 5 May 2026 09:11:03 -0600 Subject: [PATCH 5/6] Update theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md Co-authored-by: Fabien Lavocat <4154532+FabienLavocat@users.noreply.github.com> --- .../03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md b/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md index 9f55a15a94f5..7503b2696c8d 100644 --- a/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md +++ b/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md @@ -203,7 +203,7 @@ In order to enable Chromecast on the iOS SDK: ## Connect with custom Chromecast Receiver application {#custom-receiver-app} The THEOplayer SDK on your Sender application connects with THEO Chromecast Receiver application by default, -but you can connect it to a custom Chromecast Receiver application instead. The default THEO Chromecast Receiver application has THEOplayer functionality, but uses Shaka for media playback. If you want to use Google's legacy Media Player Library (MPL) for playback, you will need to use either a custom application or connect to THEO's MPL Receiver application, using the `appID` value of `44BAE7D1`. Note that the MPL receiver does not support HLS-CMAF streams. +but you can connect it to a custom Chromecast Receiver application instead. The default Dolby OptiView Chromecast Receiver application has OptiView Player functionality, but uses Shaka for media playback. If you want to use Google's legacy Media Player Library (MPL) for playback, you will need to use either a custom application or connect to Dolby OptiView's MPL Receiver application, using the `appID` value of `44BAE7D1`. Note that the MPL receiver does not support HLS-CMAF streams. ### Web SDK From 736ed3aba541326d48ac64b4b847635c91775466 Mon Sep 17 00:00:00 2001 From: Nils Thingvall Date: Tue, 5 May 2026 09:11:18 -0600 Subject: [PATCH 6/6] Update theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md Co-authored-by: Fabien Lavocat <4154532+FabienLavocat@users.noreply.github.com> --- .../03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md b/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md index 7503b2696c8d..8f9eb57cd4a4 100644 --- a/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md +++ b/theoplayer/how-to-guides/03-cast/01-chromecast/06-enable-chromecast-on-the-sender.md @@ -222,7 +222,7 @@ let player = new THEOplayer.Player(element, { }); ``` -If you do not specify an `appID` value, the player will cast to the default THEOplayer Chromecast application. This is a Receiver application that has THEOplayer functionality integrated into it, but uses the Shaka player for media playback. If you require a Receiver application that uses Google's legacy Media Player Library (MPL), there is a Receiver application with THEOplayer functionality that uses MPL. Its `appID` is `44BAE7D1`. Note that the MPL receiver does not support HLS-CMAF streams. +If you do not specify an `appID` value, the player will cast to the default OptiView Player Chromecast application. This is a Receiver application that has OptiView Player functionality integrated into it, but uses the Shaka player for media playback. If you require a Receiver application that uses Google's legacy Media Player Library (MPL), there is a Receiver application with OptiView Player functionality that uses MPL. Its `appID` is `44BAE7D1`. Note that the MPL receiver does not support HLS-CMAF streams. ### Android SDK