[MPlayer-users] Can somebody explain this? (and some trouble with mpeg muxer as well - i guess)

Nico Sabbi nicola_sabbi at fastwebnet.it
Wed Mar 8 09:11:43 CET 2006


Levente Novák wrote:

>On Wed, 2006-03-08 at 02:59 +0000, Vijay Gill wrote:
>
>  
>
>>   The problem with the muxer (which I assume is a problem because and old
>>version of mencoder (CVS of 2006-01-13 ) does the job without any problem)
>>is that it starts throwing following messages almost 10-20 seconds down the
>>line during encoding and the resulting file does not play(freezes) or has
>>sound problem.
>>
>>ERROR: SCR: 1853355569, APTS: 1812234240, DELTA=-0.446 secs,
>>COMPENSATE=7139, BR: 16000, lens: 2020/2020, frames: 5
>>ERROR: SCR: 1875721296, APTS: 1823293440, DELTA=-0.569 secs,
>>COMPENSATE=9102, BR: 16000, lens: 2020/2020, frames: 5
>>ERROR: SCR: 1881307549, APTS: 1834352640, DELTA=-0.509 secs,
>>COMPENSATE=8151, BR: 16000, lens: 2020/2020, frames: 5
>>ERROR: SCR: 1886893802, APTS: 1845411840, DELTA=-0.450 secs,
>>COMPENSATE=7201, BR: 16000, lens: 2020/2020, frames: 6
>>
>>I have not tried to find which day's CVS version actually started causing
>>this but definitely after the date mentioned above.
>>    
>>
>
>I can confirm this, got the same problems to the extent it is not
>possible to encode a XSVCD of more than 20 seconds long from a HuffYUV
>capture without these problems to happen. It used to work with last
>year's CVS (I didn't encode inbetween).
>
>It works with lavf mpeg muxer though.
>
>Levente
>
>  
>

I didn't apply to the muxer changes that could lead to this effect.
Can you try to backtrack in cvs history until you find the first 
revision that shows these problems?




More information about the MPlayer-users mailing list