I know there's no real requirement but I wish projects like this would give attribution where it's due. This project benefits hugely from pychromecast but there's nothing in the readme mentioning that. Just seems a bit off.
Isn't there a workaround to get Chromecast to accept user changes in DNS settings. Maybe use DHCP on the user's router to suggest user-chosen DNS servers. I have forgotten. The big show stopper with Chromecast is that Google makes it difficult for the user to set their own DNS servers. As I recall, with the early Chromecast models, users could replace the Google OS with a modified one that let users choose their own DNS servers. One technique used a Teensy. Subsequent Google updates I believe closed off that option.
Thanks for your work on pychromecast, I've looked and it's the best supported library for working with Chromecasts out there. It was also pleasant to integrate into this project.
Does the pychromecast project use semantic versioning? I've had to pin the library to a specific version after running into an API breaking change on what would be a minor or patch update to 7.X if the project used SemVer.
The logic should port nicely to other languages. In particular, it shows how to do things like playing a YouTube video using either the URL or just the hash, plus, of course, a way to play videos on the computer you're running the commands from.
Thank you for the library, but I wish you paid more attention to the backwards compatibility and didn't break it that often. The unannounced changes recently broke mkchromecast twice in different ways.
By the way, even the pychromecast examples broke with those updates. Very frustrating to see as a 1) user of mkchromecast, 2) user of pychromecast, 3) maintainer of both in Debian
If you don't want a Google device on your LAN and are willing to put in a little bit more work for that, I've found that remotely controlling an instance of mpv over the JSON IPC interface works well for me. I can send it URLs from the web or paths to local files. My client for this isn't currently public, but it's a rather easy interface that some of you may find it easy enough to integrate into your other systems.
(Note that it only listens on a Unix socket. With socat you can redirect that to a TCP socket though, preferably listening on a wireguard interface to keep the rest of your LAN from accessing it, since there's otherwise no security.)
Definitely not for everybody, but perhaps suitable for some.
Maybe it's late and I am misunderstanding ... Why would one not want a Google device on their LAN?
Isn't a Chromecast very different than controlling locally stored media files, i.e. you can stream YouTube, Netflix, Spotify, mirror your devices (laptop), etc on Chromecast but not your solution?
mpv plays youtube links and many other websites (although not netflix or spotify to my knowledge) using the excellent youtube-dl. For my purposes it is more than sufficient, but as I said it won't be for everybody.
As to why I don't want google devices on my LAN, I'm sure you could already guess that the answer is the usual privacy/political concerns, which I'll not bore you with since you obviously don't care. There are however some practical benefits to my arrangement, particularly being able to play media served up by NFS (DLNA never gave me anything but grief and unreliability.) Furthermore youtube-dl supports a very long tail of sites that Chromecast doesn't (at least not without the jank of screen mirroring, which AFAIK only works for as long as the laptop being mirrored is turned on.)
OT, but i had an idea yesterday... will explain in UX language: would it be possible to send video to chromecast-like device and 'leave sound on mobile device' to be able to listen on bluetooth connected headphones while watching on big screen?
I've thought about the same thing, but I don't think it's feasible because you essentially need to play the video in both places and ensure it stays in sync. The easy solution is to hook up a Bluetooth transmitted to your TV.
I can't tell from this project's readme how to actually play things. It has an instruction for connecting to your chromecast...ok, and then what?
In the past I've used https://github.com/keredson/gnomecast which is a standalone simple media player that transcodes if needed and streams to my Chromecast. Thoughts on what this provides that's better?
While you have chromecast_mpris running, you can use an MPRIS client to issue the OpenUri method[1]. Here's an example:
$ export URL="http://ccmixter.org/content/gmz/gmz_-_Parametaphoriquement.mp3"
$ playerctl -p My_Chromecast open "$URL"
This will cast a song to the Chromecast named "My_Chromecast". I forgot that OpenUri was implemented in the project because I typically cast from other devices and programs, but I'll include it in the README.
> Thoughts on what this provides that's better?
People tend to use catt or castnow to cast from the command-line. I wrote about using VLC to cast to the Chromecast[2], but I wouldn't recommend it unless you're watching something that you need VLC for.
Are there other ways to control chromecasts from Linux? I used to be able to cast straight from Chromium, but that hasn't worked for me in at least a couple years.
The VLC client is "barebones" - even simple functionality like adjusting the volume is missing. If the network connection drops, the chromecast stops playing (regular chromecast would continue). There is no support for subtitles, alternate audio/video tracks, audio effects, video playback speed, or pretty much anything else.
Seeking is supported tho, as are audio-only files.
> If the network connection drops, the chromecast stops playing (regular chromecast would continue)
How would you expect the video bits to get from the machine running VLC to the chromecast if the network drops? Not sure what you mean by "regular chromecast", but if the network connection between the chromecast and the video source is lost, you lose playback. That's true if you're watching YouTube videos or Netflix, or if you're using any other app to cast something from your local network.
Only if it's lost for longer than was buffered. Most decent streaming clients -- even YouTube -- will buffer ahead and keep playing while attempting to restore connectivity.
Speaking of which, the casting with VLC also has major buffering problems. Even casting a low-def video directly from an SSD to a Chromecast Ultra (over ethernet!) it will buffer for about 1-2 minutes for every 5 seconds of playback.
Most services (like YouTube, Netflix, etc.) transfer data direct from their servers to your Chromecast, without your phone or laptop in the loop for anything more than a remote control. It means you can start Netflix running for the kids from your phone and then go out to run an errand and it will keep playing.
VLC could do that for network sources. Even for a local file source, it could copy the whole file over - the Chromecast has a decent amount of RAM.
VLC re encodes content on the fly and sends it to the chromecast, even the android app supports it (albeit making your phone hot). Not sure about your two requirements though, maybe so. else has a tip here.
Casting a browser or whole screen can be done with Chrome/Chromium on Linux. Whole screen doesn't work with wayland. Redirecting system audio doesn't work either.
If you redirect a tab which is mostly a single video file, it is smart enough to do the video decoding directly on the chromecast, so you get much better quality/framerate.
I was interested to find out that the youtube app on an amazon fire stick is supported as a chromecast target now.
It doesn't support casting a browser tab or a desktop though (the latter isn't surprising as I'm under wayland which the parent says doesn't work, but I'd guess a browser tab should work? would be interested in other peoples experiences of this).
I do something similar with chromecast_mpris. I have my media keys mapped to Plasma's Media Controller, which uses MPRIS in the background. Works well for me, and you don't have to wait for catt to launch and find your Chromecast each time.
Shameless threadjack: does anyone know a way to cast _to_ a linux or windows desktop? We use chromecast on all our entertainment video monitors, but sometimes I would like to hang on the couch in my office and cast a video to my desktop monitor.
If opening a browser tab is all you need any tab syncing app / service will do. I use kdeconnect / gsconnect so I don't have to rely on a 3rd party service, Google and Mozilla included.
Ah this is a good idea, I hadn't thought of approaching it that way. Having basic pause/back/forward media controls would also be nice, but they should work if the browser location gets updated right?
What I would like to do is flip youtube videos or whatever on my phone and cast to the monitor, which is 6 feet from the couch... an impassable barrier as I'm sure you'll agree.
While the chromecast's inability to work with captive portals is it's own problem, they make tiny wifi routers, half as tall and twice as thick as a smartphone, and they're cheap. If you find yourself facing captive portals more than once, I'd recommend buying one so you can use your Chromecast in hotel rooms, among other use cases.
It shouldn't. Obviously if you're casting from a WAN source (like YouTube or Netflix), it needs WAN access, but if you're casting from a source on your local network, it should work without the WAN.
https://airflow.app/ is worth mentioning - paid software (sadly Windows/macOS only) but works with everything you throw at it, transcodes unsupported codecs seamlessly and has great UI with remote control via an app.
Theoretically it should work if you're able to get D-Bus working on macOS. D-Bus is usually a Linux thing, but it's been ported to other platforms. macOS isn't included in the title because most macOS users don't have D-Bus installed.
I included instructions here[1] with URLs to the macOS versions of D-Bus and PyGObject. I'd be interested in whether you're able get it working.
I wrote this lib initially for use in Home Assistant, https://www.home-assistant.io
For Home Assistant I made a rule that all device drivers are stand-alone Home Assistant agnostic Python packages. That way more projects can use it.
Glad to see that strategy is working out and it powering projects like this
I know there's no real requirement but I wish projects like this would give attribution where it's due. This project benefits hugely from pychromecast but there's nothing in the readme mentioning that. Just seems a bit off.
Does the pychromecast project use semantic versioning? I've had to pin the library to a specific version after running into an API breaking change on what would be a minor or patch update to 7.X if the project used SemVer.
Here's some example code I wrote, in the form of a few ZSH shell scripts:
https://github.com/chbarts/kodi-command-line
The logic should port nicely to other languages. In particular, it shows how to do things like playing a YouTube video using either the URL or just the hash, plus, of course, a way to play videos on the computer you're running the commands from.
(Note that it only listens on a Unix socket. With socat you can redirect that to a TCP socket though, preferably listening on a wireguard interface to keep the rest of your LAN from accessing it, since there's otherwise no security.)
Definitely not for everybody, but perhaps suitable for some.
https://mpv.io/manual/master/#json-ipc
https://github.com/mcastorina/mpv-remote-app
Isn't a Chromecast very different than controlling locally stored media files, i.e. you can stream YouTube, Netflix, Spotify, mirror your devices (laptop), etc on Chromecast but not your solution?
As to why I don't want google devices on my LAN, I'm sure you could already guess that the answer is the usual privacy/political concerns, which I'll not bore you with since you obviously don't care. There are however some practical benefits to my arrangement, particularly being able to play media served up by NFS (DLNA never gave me anything but grief and unreliability.) Furthermore youtube-dl supports a very long tail of sites that Chromecast doesn't (at least not without the jank of screen mirroring, which AFAIK only works for as long as the laptop being mirrored is turned on.)
In the past I've used https://github.com/keredson/gnomecast which is a standalone simple media player that transcodes if needed and streams to my Chromecast. Thoughts on what this provides that's better?
> Thoughts on what this provides that's better?
People tend to use catt or castnow to cast from the command-line. I wrote about using VLC to cast to the Chromecast[2], but I wouldn't recommend it unless you're watching something that you need VLC for.
[1] https://specifications.freedesktop.org/mpris-spec/2.2/Player...
[2] https://alexdelorenzo.dev/linux/2020/03/14/pipes
Are there other ways to control chromecasts from Linux? I used to be able to cast straight from Chromium, but that hasn't worked for me in at least a couple years.
Edit: included since v3.0
https://www.videolan.org/developers/vlc-branch/NEWS
Seeking is supported tho, as are audio-only files.
How would you expect the video bits to get from the machine running VLC to the chromecast if the network drops? Not sure what you mean by "regular chromecast", but if the network connection between the chromecast and the video source is lost, you lose playback. That's true if you're watching YouTube videos or Netflix, or if you're using any other app to cast something from your local network.
Speaking of which, the casting with VLC also has major buffering problems. Even casting a low-def video directly from an SSD to a Chromecast Ultra (over ethernet!) it will buffer for about 1-2 minutes for every 5 seconds of playback.
VLC could do that for network sources. Even for a local file source, it could copy the whole file over - the Chromecast has a decent amount of RAM.
[1] https://trac.videolan.org/vlc/ticket/25116
Usually I'm interested in either casting a browser window, or even the whole screen usually, which I've been coming up short on.
If you redirect a tab which is mostly a single video file, it is smart enough to do the video decoding directly on the chromecast, so you get much better quality/framerate.
It doesn't support casting a browser tab or a desktop though (the latter isn't surprising as I'm under wayland which the parent says doesn't work, but I'd guess a browser tab should work? would be interested in other peoples experiences of this).
https://github.com/Genymobile/scrcpy
If opening a browser tab is all you need any tab syncing app / service will do. I use kdeconnect / gsconnect so I don't have to rely on a 3rd party service, Google and Mozilla included.
I have a fire stick that I believe supports miracast, and periodically check if there is linux software that will allow me to stream as a source.
Last time I checked miraclecast[0] seemed to be somewhat broken. Has anyone had any luck?
[0] https://github.com/albfan/miraclecast
At least the upcoming Chromecast with Google TV comes with a remote, so you should be able to interact with the captive portal and use it that way.
You can install the Steam Link on a smart TV and your computer (including Linux), switch the Steam window and stream whatever you want to stream.
You'll probably want to avoid outputting the sound on the TV or you'll get a feedback loop.
And there's going to be a slight delay, which might be annoying with a realtime conversation.
So it might not be a great idea from the start.
How would this work on macOS?
Theoretically it should work if you're able to get D-Bus working on macOS. D-Bus is usually a Linux thing, but it's been ported to other platforms. macOS isn't included in the title because most macOS users don't have D-Bus installed.
I included instructions here[1] with URLs to the macOS versions of D-Bus and PyGObject. I'd be interested in whether you're able get it working.
[1] https://github.com/alexdelorenzo/chromecast_mpris#requiremen...