[MPlayer-users] zapping speed

[Zoilo Gomez]

Rich Felker wrote:
> On Wed, Oct 24, 2007 at 07:07:16PM +0200, Zoilo Gomez wrote:
>   
>> Thank you Nico, with "-tsprobe 256000" zapping speed is now down to 2 
>> seconds (instead of 5).
>>
>> I am trying to understand how tsprobe works.
>>
>>  From the man-page I do understand that tsprobe determines the amount of 
>> bytes that will be searched for the necessary video and audio PIDs. So 
>> why does it spend so much time when I specify a high (safe) value?
>>
>> I would expect it to terminate the search as soon as the PIDs have been 
>> found, however it seems like it keeps searching the entire specified 
>> data size.
>>
>> Why does it seemingly keep looking for something that it must have 
>> already found?
>>     
>
> It's trying to find a list of all present PIDs, not just one. The only
> way you can know there aren't more is to search the whole thing...
>   

Thanks Rick, that makes sense.

In order to further improve zapping speed, I am now experimenting with 
the cache settings.

Ideally, I would like a picture to show up asap, but at the same time I 
would like to use a cache buffer to absorb jitter.

While testing with -cache 8192 -cache-min 2, I notice that the 'current 
cache size used' seems to remain at 1-2% roughly, ie. the -cache-min value.

Is there a way to slow the display rate down a little bit, until the 
cache has filled up to say 50%, and then maintain it at 50% ? Such that 
displaying can already start immediately at 2% cache fill, after which 
we slowly fill the buffer up to 50% and stabilize it there.




> Rich
> _______________________________________________
> MPlayer-users mailing list
> MPlayer-users at mplayerhq.hu
> http://lists.mplayerhq.hu/mailman/listinfo/mplayer-users
>
>
>