[FFmpeg-devel] [PATCH 2/2] MxPEG decoder

[Anatoly Nenashev]

On 03.11.2010 21:04, Reimar D?ffinger wrote:
> On Wed, Nov 03, 2010 at 08:54:44PM +0300, Anatoly Nenashev wrote:
>    
>> On 03.11.2010 18:11, Anatoly Nenashev wrote:
>>      
>>> I have additional question. This patch works fine with ffplay, so
>>> this command
>>>         ./ffplay stream.mxg
>>> works fine and I see well syncronized video.
>>>
>>> But if I run
>>>         ./ffmpeg -i stream.mxg -f rawvideo /dev/null
>>> there are a lot of messages:
>>>         [rawvideo @ 0x30f4d10] st:0 error, non monotone timestamps 1>= 1
>>>
>>> After some researches I found that right command line must be
>>> ./ffmpeg -i stream.mxg -r 25 -f rawvideo /dev/null
>>>
>>> So it meens that user must manually define output FPS, otherwise
>>> it will be 1/time_base. In case of mxg demuxer it is 1000000.
>>> I think that it isn't so user friendly way. What can I do with
>>> this issue?
>>>
>>>        
>> I have found only one decision for this issue. I have changed
>> time_base in demuxer  for video stream from 1/1000000 to 1/100 and
>> rescale output pts from it.
>>      
> You can't just mangle the time stamps just because the one
> source you have at hand sets them to values you don't like.
> Your source isn't 30 fps, and it needs a 1/1000000 time base
> to be represented accurately.
>    

Ok. I've removed dts transformation.
Also parsing dts for audio packets are added. See attachment.

> If you want FFmpeg to try harder to chose some "close enough
> but not correct" time-base for non-VFR formats then that belongs
> into the main FFmpeg code (e.g. the tb_unreliable handling),
> but certainly not in a demuxer.
>
>    

May be done later in another patchset.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: mxg_v9.patch
Type: text/x-patch
Size: 7867 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20101103/4b6880f6/attachment.bin>