[MEncoder-users] demuxing question

[Rick C.]

On Nov 22, 2010, at 10:20 PM, James Hastings-Trew wrote:

> On 10-11-22 7:53 AM, Rick C. wrote:
>> Hello,
>> 
>> I've encountered a problem and I hope someone can help me find out what's wrong.  Here's my command:
>> 
>> test.flv -ovc lavc -lavcopts vcodec=mpeg4 -ffourcc XVID -oac faac -o test.avi
>> 
>> The video I'm converting is 10 minutes and with a recent MEncoder build I only get about 4 minutes output.  But with a MEncoder build I have from last year I get the full 10 minutes.  Here is some output that might show the problem:
>> 
>> libavformat file format detected.
>> [lavf] Video stream found, -vid 0
>> [lavf] Audio stream found, -aid 1
>> VIDEO:  [H264]  480x360  0bpp  29.917 fps    0.0 kbps ( 0.0 kbyte/s)
>> [V] filefmt:44  fourcc:0x34363248  size:480x360  fps:29.917  ftime:=0.0334
>> 
>> That is from the good one and this the bad:
>> 
>> libavformat file format detected.
>> [flv @ 0x101857400]Estimating duration from bitrate, this may be inaccurate
>> [lavf] stream 0: video (h264), -vid 0
>> [lavf] stream 1: audio (aac), -aid 0
>> VIDEO:  [H264]  480x360  0bpp  59.750 fps  573.7 kbps (70.0 kbyte/s)
>> [V] filefmt:44  fourcc:0x34363248  size:480x360  fps:59.750  ftime:=0.0167
>> 
>> And the end:
>> 
>> Pos: 233.9s  12706f (66%) 218.85fps Trem:   0min  36mb  A-V:-0.030 [736:128]
>> Too many audio packets in the buffer: (4096 in 1584970 bytes).
>> Maybe you are playing a non-interleaved stream/file or the codec failed?
>> For AVI files, try to force non-interleaved mode with the -ni option.
>> 
>> I only posted a small portion because I noticed in the good one it accurately reads 29.917fps but the bad a very different number.  The rest of the output was about the same but I can post more if needed.  Any idea why this might be happening or an idea of what else I can check?  I honestly can't remember if I did something different compiling the MEncoder from last year.  Thanks for your help!
> 
> Does sticking -fps 30000/1001 in the command line help any?

If I can ask again regarding my original question if the problem is in the demuxing and lavf is doing the demuxing does that mean that it wasn't the way I compiled MEncoder or what I compiled it with but rather maybe there was a bug in the specific MEncoder snapshot?  I'm just asking because I want to be sure it was not somehow the way I built it.  Well usually if I would have left something out when compiling then I would get an error saying something is missing which didn't happen in this case.  I'll be sure to retest this video the next time I compile MEncoder.  I did notice however in the bad one there is the [flv @ 0x101857400] line that is not in the good one.  Why would that be?  Thanks again,

rc