- A browser extension that enables Chromecast support for
- casting web apps (like YouTube, Netflix or BBC iPlayer),
- HTML5 media and screen/tab sharing.
-
-
- Requires a native bridge app to connect with receiver
- devices. Currently supported on Windows, macOS and
- Linux.
-
-
- No full public release yet! Pre-release beta version is
- incomplete and likely buggy.
-
-
- Latest release is missing macOS x86 build and Windows
- 32-bit build. See
- #209
- for more info. Older releases are
- available.
-
- For sites with built-in cast support,
- click the cast button in the page and
- select the destination in the receiver
- selector popup. You may have to add the
- site to the whitelist to get the cast
- button to appear.
-
-
- For other sites, there is a "Cast..."
- item in the context menu when
- right-clicking on a media player. This
- may not be visible depending on whether
- the site has chosen to obscure the
- player with an overlay or if the media
- is DRM-encumbered (see below).
-
-
- Clicking the toolbar button will open
- the popup, but depending on the context,
- it may not be possible to cast anything.
-
-
- As a last resort, casting the tab or
- screen may provide a means of displaying
- this media on the Chromecast, but it has
- its own limitations: the performance is
- very poor and there's no audio casting.
-
-
-
-
-
-
-
-
-
Why do I need the bridge?
-
-
-
Access to TCP/UDP sockets.
-
- Network discovery for Chromecast devices
- relies on mDNS, the implementation of
- which is reliant on being able to send
- UDP packets. Communication with the
- Chromecast device itself relies on a TCP
- connection. The current workaround is to
- offload that work to a native companion
- application that the extension can then
- launch and communicate with.
-
-
- It's possible that this functionality
- will be re-exposed to extensions, in
- which case the bridge will be made
- redundant:
-
- "No bridge found" with Firefox
- snap/Flatpak package
-
-
-
-
- Whilst running inside a sandboxed
- version of Firefox, the extension is
- unable to start the bridge by itself.
- The bridge must be started in
- daemon mode, and the
- "Enable backup daemon connection"
- option enabled in the extension.
-
-
-
-
-
-
-
-
- How do I completely remove the bridge?
-
-
-
-
-
-
Windows
-
- Removing the bridge on Windows
- should be as easy as running the
- uninstaller (C:\Program
- Files\fx_cast\uninstaller.exe) found in the control panel or
- settings application.
-
-
- To manually uninstall, remove
- the following files/folders and
- registry keys:
-
- Why is there no sound when casting a
- screen or tab?
-
-
-
-
- API limitations. There's no method of
- obtaining the audio streams. Merging of
- audio streams from remote media is also
- not possible due to cross-origin issues.
-
- Compatibility with Chrome is far from
- perfect. Most sites will only enable
- their cast support if the browser
- reports itself as Chrome. Ensure that
- you've added the site to the whitelist.
- Some sites may not test their
- Chrome-specific code with Firefox, so
- it's possible that they're using
- incompatible/non-standard APIs.
-
-
- The API is also not fully implemented
- and is missing some methods (mostly
- queue management). The current
- implementation likely also has
- edge-cases and bugs which may cause
- issues.
-
- Unforunately, for DRM-encumbered media,
- there's no network-accessible URL to
- provide to the Chromecast and no means
- of accessing the media streams. The only
- way to cast on sites like this is via
- built-in Chromecast support (look for a
- cast button), which may not always be
- available.
-
-
-
-
-
-
-
-
- Why is it taking so long for a full
- release?
-
-
-
-
- Though I do enjoy working on this, it's
- (obviously) not a full-time thing. It's
- just a hobby project. You can help speed
- up development by contributing (see
- below).
-
-
-
-
-
-
-
-
How can I support development?
-
-
-
- Contributing code, translations,
- compatibility reports, or even reporting
- bugs is very helpful. See the
- contributing guide
- for more information.
-
+ For certain types of media, there is
+ a "Cast..." menu item in the browser
+ context menu for the media player
+ (if the player has a custom context
+ menu, try shift-clicking to bring up
+ the browser context menu).
+
+
+ This may not be visible depending on
+ whether the media is
+ DRM-encumbered
+ or has a network-accessible URL to
+ send to the Chromecast device.
+
+
+
+
+
+
+
+
+
Why do I need the bridge?
+
+
+
+ API limitations. Chromecast device
+ discovery requires an mDNS/DNS-SD
+ implementation, something which
+ isn't provided by (or possible with)
+ WebExtension APIs. Communicating
+ with Chromecast devices require
+ making TCP connections, which is
+ also not possible.
+
+ The bridge relies on system services
+ (Bonjour on Windows/macOS, Avahi on
+ Linux) to provide device discovery.
+ If the bridge isn't able to find any
+ devices, there may be a
+ configuration issue (either with the
+ system service or the network).
+
+
+ If you're using Arch Linux, Avahi is
+ not configured by default to resolve
+ .local hostnames via
+ the
+ NSS
+ which is required to resolve
+ Chromecast device addresses. See
+ more information
+ here.
+
+
Other issues include:
+
+
+ The devices you're looking for
+ may not be compatible. Chrome
+ also supports a limited number
+ of apps on some Smart TVs via an
+ older protocol called
+ DIAL
+ which
+ isn't currently
+ supported.
+
+
+
+ Some network configurations
+ may interfere with mDNS
+ packets. Virtual machine
+ network adapters typically
+ will not work out of the
+ box, for example.
+
+
+
+
+ There may be an issue with
+ the bridge causing it to
+ close unexpectedly. Check
+ the
+ Browser Console
+ for error logs and submit a
+ new issue on GitHub with
+ some more information (if
+ necessary).
+
+
+
+
+
+
+
+
+
+
+ Why isn't the bridge found when
+ using the Firefox snap/Flatpak
+ package?
+
+
+
+
+ Whilst running inside a sandboxed
+ version of Firefox, the extension is
+ unable to start the bridge by
+ itself. The bridge must be started
+ in
+ daemon mode, and the
+ "Enable backup daemon
+ connection"
+ option enabled in the extension.
+
+
+
+
+
+
+
+
+ How do I completely remove the
+ bridge?
+
+
+
+
Windows
+
+ Removing the bridge on Windows
+ should be as easy as running the
+ uninstaller found in the control
+ panel, settings application, or
+ application directory.
+
+
+ To manually uninstall, remove the
+ following files/directories and
+ registry keys:
+
+ Why is there no sound when casting a
+ screen or tab?
+
+
+
+
+ API limitations. There's no method
+ of obtaining the audio streams.
+ Merging of audio streams from remote
+ media is also not possible due to
+ cross-origin issues.
+
+ Compatibility with Chrome is far
+ from perfect. Most sites will only
+ enable their cast support if the
+ browser reports itself as Chrome, so
+ ensure that you've added the site to
+ the whitelist. Some sites may not
+ test their Chrome-specific code with
+ Firefox, so it's possible that
+ they're using
+ incompatible/non-standard APIs.
+
+
+ The Cast API is also not fully
+ implemented and has some stubbed
+ methods. The current implementation
+ likely also has edge-cases and bugs
+ which may cause issues.
+
+ Unforunately, for DRM-encumbered
+ media, there's no network-accessible
+ URL to provide to the Chromecast and
+ no means of accessing the media
+ streams. The only way to cast on
+ sites like this is via built-in
+ Chromecast support, which may not
+ always be available.
+
+
+
+
+
+
+
+
+ Why is it taking so long for a full
+ release?
+
+
+
+
+ Though I do enjoy working on this,
+ it's (obviously) not a full-time
+ thing. It's just a hobby project.
+ You can help speed up development by
+ contributing (see below).
+
+
+
+
+
+
+
+
How can I support development?
+
+
+
+ Contributing code, translations,
+ compatibility reports, or even
+ reporting bugs is very helpful. See
+ the
+ contributing guide
+ for more information.
+