On Wed, 10 Sep 2003, Ralf Haller wrote:
> Hi Berni,
>
> here's what I get when I am multiplexing a custom VDC with higher bitrate:
>
> [EMAIL PROTECTED] tmp]$ mplex -f 2 -r 1500 chunk.m1v chunk.mp2 -o chunk.mpg
...
> ++ WARN: [mplex] Padding : sector=00000000
> ++ WARN: [mplex] Stream e0: data will arrive too late sent(SCR)=572382
> required(
> DTS)=564048
> ++ WARN: [mplex] Video e0: buf= 44799 frame=000141 sector=00000386
> ++ WARN: [mplex] Audio c0: buf= 4096 frame=000218 sector=00000070
> ++ WARN: [mplex] Padding : sector=00000019
> ++ WARN: [mplex] Stream e0: data will arrive too late sent(SCR)=946068
> >>[EMAIL PROTECTED] tmp]$ ffmpeg -i test.mpg -b 1150 -s 352x288 -r 25 -ab 224 -ar
> >>44100 -f vcd -y out.mpg
1500 is too low. ffmpeg's mpeg capability is not as refined as
that of mpeg2enc (at least when it comes to the rate control or so
it would seem).
Perhaps using mpeg2enc as has been suggested would be a better
method of preparing the .m1v file
Use '-r 2500' or higher and see what mplex prints out for the
Average and Peak rates.
Cheers,
Steven Schultz
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
