[vlc-devel] [RFC] Unified caching values
david.glaude at gmail.com
Fri May 20 13:11:13 CEST 2011
2011/5/20 Laurent Aimar <fenrir at elivagar.org>:
> On Fri, May 20, 2011 at 02:41:13AM +0200, Pierre Ynard wrote:
>> Sounds like a good idea, but how does caching work? Because when setting
>> too low values, Bad Things™ happen at some point in the pipeline.
>> Users got broken setups in the past because of that.
> With 1.2, when the caching is too low, the input will automatically increase
> it. When it does, you have a pause (can't be avoided), and you have a glitch in
> audio/video (broken frames sometimes). So it's not as bad as before where VLC
> would never recover.
Could you show us where/when is that new change in 1.2?
I would like to compare two nighlty build (before and after) in our
"low lattency lab".
How is it different from "--clock-jitter 0"?
Do you still have options to disable that increase?
In our case, VLC was always capable to recover, only the new delay was
not always acceptable.
But I don't remember seeing a VLC crash because of empty input buffer.
More information about the vlc-devel