[londons_explore]

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.

[kelnos]

> 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.

[mholt]

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.

[londons_explore]

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.

[this_machine]

I opened a bug report[1] regarding this issue a few days ago if you'd like to leave a comment.

[1] https://trac.videolan.org/vlc/ticket/25116