On Thu, 20 May 2004, Michel wrote:
> I'm trying to encode a divx of 3 hours to mpeg2. Yuvscaler stop
> everytime at frame 182053 (totally there are around 250000 frames) with
> a bad frame header-message. Everytime I try a attempt to do the encoding
> I have to wait 20 hours till the encoding process arives at frame
> 182053.... I tried 2 times and it crashed every time... Very frustrating!!!
That sounds suspiciously like a 2GB limit being reached somewhere and
when the filesize limit is exceeded the program exits breaking the
pipeline.
How large is the input.avi file? What resolution, etc is the input
file? If it's 320x240 or so then zooming/scaling that up to full
frame DVD is not going to look very good.
> I'm using mandrake community, kernel 2.6. Filesystems are reiserfs and xfs.
There shouldn't be a filesize limit problem with those filesystem types
but perhaps an application was compiled without largefile support?
> The command:
>
> transcode -i <input>.avi -y yuv4mpeg,null --hard_fps -J modfps
> --export_fps 0,3 -q 0 -Q 5 -z -o /dev/stdout | yuvcorrect | yuvscaler
> -M BICUBIC -O DVD -n p -O SIZE_720x576 | mpeg2enc -f 8 -F 3 -a 3 -4 2 -2
> 1 -q 8 --keep-hf -o <ouput>t.m2v
There aren't any keywords/options given to 'yuvcorrect' so I think
that program is a no-op and could be removed from the pipeline (might
speed things up a little).
The "-O DVD" and "-O SIZE_720x576" are redundant. Once you use
"-n p" to specify the video norm then just "-O DVD" is sufficient.
> Errors:
>
> Couldn't read FRAME HEADER: bad header magic!
> Couldn't read frame number 182053
> End of stream!
> Normal exit: end of stream with framenumber 182053.
Ah, but which program is producing that? The program name should
be part of the message - like this:
**ERROR: [yuvscaler] Could'nt read YUV4MPEG header!
If yuvscaler is producing the error message that means the pipeline
into yuvscaler was broken by 'transcode' or 'yuvcorrect'.
What version of mjpegtools are you using? If it's earlier than 1.6.2
(the last release) I would recommend upgrading.
I do see in yuvcorrect a message that looks like this:
Couldn't read frame number %ld!
so it's possible that yuvcorrect is getting an 'end of file' or broken
pipe from transcode.
>
> Anyone has an idea/knows how to solve this??
If it's transcode having a problem with the input AVI file then I'm
not sure what can be done.
It is beginning to feel like transcode is having trouble reading
past the 1 or 2GB limit of an AVI file. Normally AVI files have a
1 or 2GB limit but the ODML extensions were supposed to fix that
issue.
> I prefer to not reencode the first 182053 frames AGAIN. So if anyone
> knows/has an indea how to concatenate 2 m2v-files, I would also
> appreciate that.
There have been a couple references to such a program/utility posted
to this list recently about that - perhaps a quick search of the last
week or two in the archives will pop up the answer.
I know 'mplayer' can, with the '-vo yuv4mpegp' option produce YUV4MPEG2
output - perhaps that might be an alternative method.
'ffmpeg' can also produce 4:2:0 raw and yuv4mpeg output - I think
something like this:
ffmpeg -i input.avi -f yuv4mpegpipe -pix_fmt yuv420p /dev/stdout
would do the trick.
Good Luck!
Cheers,
Steven Schultz
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
