Hi, 0n 06/11/[EMAIL PROTECTED]:55 Eric Lavarde - Asb told me:
> in my program asb, I'm transforming MJpeg files from my Canon camera into
> MPEG1 files (because it's the only format I made work on all PCs of my
> family out-of-the-box on Mac, Windows and Linux). This worked quite well,
> but with my new camera, I have bigger films (640x480 instead of 320x240
> and 30fps instead of 15) and I get 'Frame data under-runs detected!' from
> mplex.
>
> Here the debug output:
>
>
> [...]
> DEBUG: Created directory '/tmp/AsbTest/.tmpmjpg'.
> DEBUG: /usr/bin/transcode -i /tmp/AsbTest/0065_MVI.AVI -y ffmpeg,mp2 -F
> mpeg1video --export_fps 24 -J modfps -E 22050,16 --encode_fields p
When using modfps IMHO it's a good idea to specify input frame rate
(-f 30,5) too.
--encode_fields p should be default.
Dunno if it matters but -E 22050.. is IMHO somewhat strange, too.
Your ears should IMHO notice signals above 11025 Hz and if nothing
stands against it I would use a more common one like 44100 or 48000.
> --video_max_bitrate 14969520 -o /tmp/AsbTest/.tmpmjpg/film --ext
*Ups*. If I got it right that means you ask transcode that it can
spend 14969520 bits/sec (> 14 Mbit/sec) for a bloody mpeg1 file
(assuming transcode will not interpret this value as kbit/sec
already).
Further the manpage says MPEG-2 vbr here and you use it to create an
mpeg1 file.
If in luck transcode will just ignore this statement. However, I
would drop it, as your result should not reach such bitrates at all.
> .m1v,.mpa --print_status 10,0
>
> PROCESSING:
> ..............................................................................................................................................
> DEBUG: /usr/bin/mplex -r 29258 -f 0 -V -o
Probably it is better not to use -r here, as man mplex suggested:
---cut---
-f
0 - Generic MPEG1. A simple general-purpose MPEG1 format
primarily suitable for software decoders. Buffer
sizes and VBR must be specified. Bit-rate can be
auto-detected.
---cut---
so I would drop -r and probably add -b (I would start @ -b 230 see
man mplex).
I think your problem is based on mplex and a bitrate issue.
googleing for:
> ++ WARN: [mplex] Stream e0: data will arrive too late sent(SCR)=957
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Leads you to this thread:
http://www.mail-archive.com/mjpeg-users@lists.sourceforge.net/msg06909.html
Further IIRC ffmpeg was known to have problems with to high peak
bitrates when introducing dvd (mpeg2) support. As I suppose nearly
no one will use mpeg1 (especially if out of dvd/vcd specs) nowadays,
there is probably some similar issue left in ffmpeg. So, it is
IMHO worth a trial to use -y mpeg2enc,mp2enc -F 0 for encoding, if
all other efforts fail.
--
bye maik
signature.asc
Description: Digital signature
