command line to chromecast --> remux is faster than live, vlc closes http stream, chromecast quits. But if you separately declare demux as demux_chromecast, it works
Issue:
If you use --sout "#chromecast{ip=192.168.XX.XX,mux=mp4}"
, the file is hosted as an http stream correctly and the chromecast device successfully connects to the remuxed stream hosted by vlc and begins playing.
However, the remuxing process performed by vlc is not performed not in realtime, but rather piped to the receiving device at as high a bitrate as possible (filling buffer of chromecast default media receiver in the chromecast's RAM). As soon as the file is finished being sent to the chromecast (or when the chromecast's RAM is full), the http session is closed by vlc. This causes the chromecast to quit playback immediately (i.e., songs and videos only play for a few seconds and then quit)
For example, this issue occurs if you apply vlc -vvv ./file.mp4 --sout "#chromecast{ip=192.168.1.XX,mux=mp4}"
However, if you specifically declare demux filter as "demux_chromecast", playback is done correctly at realtime speed, and scrubbing forwards and backwards through the file works correctly at chromecast playback:
(i.e., this command here works perfectly)
vlc "C:\Users\admin\Desktop\carbot.mp4" --sout "#chromecast" --sout-chromecast-ip=192.168.2.173 --demux-filter=demux_chromecast vlc://quit
Given that chromecast only supports the containers MP4, OGG, WAV, WebM, MP2T, MP3 (https://developers.google.com/cast/docs/media), would it not make sense that when --sout "#chromecastXXX
is called, that --demux-filter=demux_chromecast
is set automatically?
NOTE:
demux_chromecast is NOT documented in vlc -H