Using a full fledged build of ffmpeg should allow you to offer support for AVI input/output which others have asked for repeatedly. I don't do any encoding with VRD (I actually haven't upgraded to v4 from v3 yet).ĭan- My question was really more from a curiousity standpoint. MrVideo- Yes, I am aware of and make use of x264, avisynth, hcenc, xvid_encraw, etc for manipulating/encoding. Although I haven't looked at x264 closely enough to know if it actually exposes those options or not. If x264 allowed us to set these settings then we might be able to eliminate that bug. When you do a quick edit of these streams the recoded frames around the edit points don't match the rest of the stream exactly and this can cause glitches at the edit points. There are some situations where a source stream can contain encoding parameters which we do not have access to in the MC encoder. The only real advantage of using x264 in VRD, besides higher bitrates, would be if it allowed us to set some of the more advanced encoding options which MC currently doesn't. While 3rd party tests have shown x264 to be of higher technical quality, I'd be willing to bet that most average users wouldn't be able to tell the difference. And unfortunately some of the capabilities of FFmpeg are not exposed in the DLLs in such a way that we could use them in VideoReDo.Īs for quality. Doing this would require something else completely independent of the encoder.
We do this because most people don't understand them and it's almost impossible for us to verify them all to make sure they are set correctly.Ģ) This is valid, and one of the main reasons we've discussed using it.ģ) This has nothing to do with the encoder, as you mentioned. There are a lot of options in the MC encoder which we don't expose via VideoReDo. More about that in the next post.1) This is more of a VRD issue than an encoder issue.
Authoring 720p files through multiAVCHD can handle this for you. You can still use a cheap DVD-R or DVD-RW disc to achieve this, but you must play that disc on a Blu-ray player and the file format can no longer be conventional DVD, but must be the special AVCHD DVD format. Since your source footage was 720p, you may prefer to see a result with that original resolution on your (HD) TV. If you have more than one AVS file in the folder, both the above batch files will process them all in sequence. …On the other hand the batch file AVS to PAL DVD MPEG.bat would be what you’d use for an AviSynth script referring to MTS(PAL AVCHD Lite) source files…įor %%a in ("*.avs") do ffmpeg -i "%%a" -target pal-dvd -b 8000k -aspect 16:9 "%%~na.mpg" Put the batch file in the same folder as your Avisynth script and your source video files, ones of type AVI(MJPEG) or MTS(NTSC AVCHD Lite), and then double-click the batch file. If you prefer, you can produce a DVD-compliant MPG file with your own generic installation of ffmpeg and use a batch file as the front end.Ĭopy the following text and paste it into Notepad, then save the file as something like AVS to NTSC DVD MPEG.batįor %%a in ("*.avs") do ffmpeg -i "%%a" -target ntsc-dvd -b 8000k -aspect 16:9 "%%~na.mpg" You can author a DVD disc from the MPG file, perhaps with other MPG files of related topics, by using the program DVD Styler which provides a simple but adequate menu system.Īlways remember that if your AviSynth script reads in MTS files from AVCHD Lite, you must also have the FFMS2 plugin for AviSynth installed. The resulting MPG file will have AC3 audio.
Press the Convert button and watch the ffmpeg console window open and do its thing. In the Device Preset drop-down list select either NTSC DVD HQ Widescreen or PAL DVD HQ Widescreen as discussed above.
Select DVD from the Convert To drop-down list. WinFF doesn’t require a separate installation of ffmpeg it uses its own stable version.ĭrag your AviSynth script AVS file and drop it into the open WinFF window. A good choice is WinFF, which accepts AVS script files directly. You can always check the specification of your source footage, including the frame rate, by using MediaInfo.Ī very straightforward way of converting to MPG is to use one of the GUI front ends already available for ffmpeg. But if the source is PAL AVCHD Lite (at 25fps) then go for PAL MPG.
If your camera was purchased in an NTSC region (and shoots 29.97fps AVCHD Lite) then again opt for NTSC MPG. If your original source was MOV and your AviSynth script is now handling AVI(MJPEG) at 30fps, then you’d convert the output from the script to NTSC MPG. Which to pick? I’d suggest that the frame rate of your source footage is the determining criterion. The resolution won’t remain at 1280×720, of course, but will be reduced. By using ffmpeg you can compress the output from a 720p AviSynth script to give an MPG file which is suitable for DVD authoring.