On Sat, 2009-03-07 at 10:28 +0100, Richard wrote: > Hi, > sorry to boher again with my stuff. :-| > Sometimes, when transcoding vobs to h264 m4v files with the new > "encode" way, the first pass seems to work well :
Don't worry, we're here to fix the bugs (well, not only for that but...) :) > [transcode] encoded 81523 frames (2 dropped, 0 cloned), clip length > 3260.92 s [*] So I'm expecting a 81253 line long logfile. Please post the output fo the following: $ wc -l /path/to/offending/logfile $ tail -n 20 /path/to/offending/logfile > but the second pass fails almost immediately with the following > error : Yes, it fails when loading the stats file, at x264 initialization time. > [encode_x264.so] using cpu capabilities: MMX2 SSE2 > [encode_x264.so] critical: bad frame number (81519) at stats line > 81516 > [encode_x264.so] critical: x264_encoder_open() returned NULL - sorry. > [encoder.c] critical: video export module error: init failed > [transcode] critical: failed to init encoder [...] > Is that something that depends on transcode or something that should > be reported to the x264 team? The error happens into x264, however it is still possibile that transcode given wrong (or missing) parameters to the library. It happens randomly? If I understood correctly, sometime it should work fine. Have you noticed any dropped frame for the failing sources? See [*] above. Bests, -- Francesco Romani // Ikitt http://fromani.exit1.org ::: transcode homepage http://tcforge.berlios.de ::: transcode experimental forge
