Google Cast (Chromecast)
Fastevo's web player can send supported protected videos from Chrome to a compatible Chromecast or Google Cast TV. The browser becomes the remote; the TV starts its own authorized playback session and retrieves the media and Widevine license directly. This is not screen or tab mirroring.
Fastevo hosts and registers the Cast receiver. Your application does not
need its own Google Cast app ID, receiver URL, new playback token format, or
changes to its existing t= link, iframe, or data-token injector.
Watching on a TV
- Open a supported video in desktop Chrome while the computer and Cast device are on the same network.
- Choose the Cast icon in the Fastevo player and select your TV.
- Once playback starts on the TV, use the player in Chrome to pause, seek, adjust volume when supported by the device, and select available subtitles or audio tracks. Choose Return to this device to resume locally.
The browser pauses local playback during handoff; the same content should not play on both screens. If a Cast request is rejected, the player shows an error and restores the local session. A lost connection can leave the TV playing; the browser will not claim success or stop an unconfirmed TV session silently.
Compatibility and access
- The current Cast integration is for protected video on demand on a Widevine-capable Cast device. It does not fall back to ClearKey, unprotected delivery, or a weaker DRM policy to make a TV play.
- The TV is a separate device with its own IP and playback authorization. Project rules, viewer identity, token expiry, Enhanced requirements, and network restrictions still apply. A browser that can play a video does not guarantee that every TV is authorized.
- Cast requires a valid original playback token when the TV session starts. Existing customer integrations keep their current token and embed format.
- The receiver supports available VTT subtitles and compatible audio tracks. The browser's remote controls show only capabilities reported by the TV or media session; some TVs require their physical remote for volume.
- Sandboxed third-party iframes must permit presentation. A parent page that explicitly forbids it cannot be overridden by the player.
Apple devices use AirPlay rather than Google Cast from Safari. AirPlay and native iPhone fullscreen have separate player settings and may be restricted by Enhanced protection.
Current limits
Live streams, audio-only content, images, and videos with ad-interstitial configurations are not part of this Cast release. Compatibility with every Cast model and sender browser has not been certified; desktop Chrome and a Widevine-capable Chromecast are the tested path.
The visible forensic dots and badge on the TV are currently disabled by Fastevo's receiver build setting. Browser playback retains its own protection; DRM authorization, session checks, security rules, and playback telemetry remain active on the TV. Do not rely on a TV recording containing the visible marker while this setting is off.
For developers
The sender passes the existing play token to Fastevo's receiver in the
versioned Cast LOAD contract. The receiver then requests its own authorized
session from the API. It does not receive the browser's license credential or
content keys. The player does not currently expose a documented public
castStarted callback to embedding applications; Cast status is shown in its
own UI. Backend playback telemetry includes Cast receiver sessions.
See Embedding the Fastevo MP2 Player and Player Configurations for the standard integration and AirPlay options.