Hi! I just bought a 24" LCD screen and suddenly realized that most of the rips I've done of my DVDs, done with xvid and vorbis codecs muxed in a matroska container, look rather blocky on this new hardware. So I'm about to start a new ripping campaign of all my DVDs, but first I wanted to find the nice codec for it. Initial tests showed that H264 is much better than xvid for large screens, being a lot less blocky and keeping still images really still. So I started doing some tests with transcode HEAD (downloaded yesterday), using basically three different processes :
- directly the x264 lib with new generation encode modules - usig lavc new generation module - using the old ffmpeg export module First of all, I find the new module architecture, with vcodec,acodec,mcodec really nice and hope you'll be able to get there as quickly as possible, it's very good from the user point of view. However, I ran into some issues : - Using the x264 module directly, everything works fine, but there are green artifacts appearing here and there, even when no x264.cfg is present. It's weird because these artifacts do not appear in the exact same situation with the lavc and export_ffmpeg modules, using the very same x264 lib, so I think it should be an issue with the current x264 transcode encode module. - Using lavc module, it seems to run OK, except that 2-passes rendering does not work, as the first pass does not seem to record anything in the log file. Using one pass, I see no green artifacts (but that does not mean there won't be with two passes). - With export_ffmpeg, things run fine, but I don't seem to have access to all h264 options using the ffmpeg.cfg file. - the lafc muxer did not accept to mux an AAC stream created by the faac module in a m4a file, for some reason. I finally ended creating wave file and convert them with faac. It works but is less elegant. Please let me know if you want me to run some tests to fix these problems or, if they're caused by my ignorance, please explain where I've made a mistake. Thanks anyway for transcode, that's a mighty piece of software I've been using ofr years and I really like where it's heading. Best regards, Richard Van Den Boom
