Hi, Francesco and thanks for answering! > And that's just the beginning ;) Congratulation, then! :-)
> Yes, I'll do some tests (which version of x264 are you using?). > Most likely the problem is on how the x264 encoder is feeded. I use the latest x264 from git (or svn, don't remember). I got these green artifacts consistently with several DVD rips (meaning I'm trying to transcode PAL VOBs file, read by the vob import module from the hard disk). It's often on the left side of the image but can appear in many other places, especially if options are set up supposed to increase image quality (which they do where there's no artifact). > Ack. I'll check this too. This happen whether I tried to use a specific file or if I let transcode use the default divx4.log file. The first pass, it does seem to want to use it but does not record anything in it and thus the second pass fail. > This is a known "issue" in the sense that ffmpeg(/lavc) module should > _not_ expose all possible setting, but just a subset that is shared > wit all native ffmpeg codecs. It's the job of specific x264 module to > provide full access to underlying library. I understand. Well, the new module way is more elegant anyway so if it works, that will be fine for me. :-) > Are you referring to multiplex_lavf? That module is still HIGHLY > experimental, it's already a success if hasn't caused a segfault! :^) Well, it's a success then. :-) 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. Thanks for your work, it's really much appreciated. Best regards, Richard
