OK, I'm a total cretin. Checking what version og the x264 lib I had, I realized I actually had 2 installed : the most recent 60 and one year-old 47. After uninstalling both and reinstalling the 60, transcode new module works perfectly and the image quality is perfect! I don't have your "rate abort" message, which is weird, though. I also had the x264_2pass.log issue using export_ffmpeg but thought it was not a big deal, so I did not talk about it... At least the two-pass libavc issue is real, otherwise I would have bothered you for nothing.
2008/8/11, Francesco Romani <[EMAIL PROTECTED]>: > On Sat, 2008-08-09 at 23:16 +0200, [EMAIL PROTECTED] wrote: > > [...] >> I didn't know I was that much on the edge, though I should have >> guessed since man pages were not even talking about it. :-) >> OK, I'll wait a while before trying to use that one. > > OK, my findings follows. > > #1 encode_lavc: I confirm that it doesn't produce first pass log data in > transcode standard file divx4.log; to be exact, it doesn't produce any > log data at all. Probably HEAD is also affected. > > #2 export_ffmpeg: produces the pass log data in a separate file > (x264_2pass.log). > IIRC this issue was already addressed in the past, it would be nice to > try again (or definitively solve this issue). > > #3 encode_x264: on my box it segfaults with -q 2. Too bad. > HEAD is also affected (same codebase). > > #4 encode_x264: on my box, it aborts with "no ratecontrol method > specified" (libx264 build 60), while it works fine through lavc. > VERY strange indeed. It needs more careful investigation. > > For #3 and #4, paired with your reports, I smell some bad memory > corruption. > > Expect fixes in CVS and in 1.1.0beta2 ASAP, this x264 issue has climbed > my TODO list for TC :) > > Bests, > > -- > Francesco Romani // Ikitt > >
