[vlc-devel] [PATCH 0/3] Fixing input/decoder/sout deadlock with chromecast

Thomas Guillem thomas at gllm.fr
Mon Feb 12 20:39:13 CET 2018

On Mon, Feb 12, 2018, at 19:13, Rémi Denis-Courmont wrote:
> Le maanantaina 12. helmikuuta 2018, 19.13.23 EET Thomas Guillem a écrit :
> > Hello,
> > 
> > A lot of users report that Chromecast is not working for their
> > configuration. Indeed, some Chromecast devices need to be feed with one
> > minute of data. Since VLC is buffering 300ms of data by default, you'll
> > have to wait 59.7 sec to start playback on some chromecast devices.
> On the one hand, that is a total non-issue if the input is not pacing, as VLC 
> will happily fill the pipeline as fast as the output allows. On the other 
> hand, it is fundamentally unfixable if the input is paced since you can go one 
> minute into the future.
> So I utterly fail the point in hacking the decoder and stream output.
> And hacking the decoder thread in 3.0, not even funny. It is called "stable" 
> branch for a reason.

That is the only proper way I found to fix an issue that will touch every chromecast users. That is not funny but I thought this was more important that this kind of concern. 

> -- 
> 雷米‧德尼-库尔蒙
> https://www.remlab.net/
> _______________________________________________
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
> https://mailman.videolan.org/listinfo/vlc-devel

More information about the vlc-devel mailing list