Wednesday, June 12, 2013

And More: How to record with H.264/AVC/x264/x264vfw (MPEG-4 Part 10) so that your video clips will open in Sony Vegas and Adobe Premiere (Short Tutorial/Example Video)

Originally created to show an example of what to change so that your game recordings using the H.264/AVC/x264/x264vfw (MPEG-4 Part 10) codec will open up in Vegas, this also works for Premiere, Lightworks and other NLE's (Non-Linear Editors), for those who were having problems editing.

In this example*, I am recording with an x264vfw (Komisar's Unofficial, Black Logo) interface**, which sets up h.264/AVC encoding, used as an "External Codec" in Bandicam:

*Just a silly version of the video, sorry for taking up your time with this little joke
Summary of Video: Within the x264 Video For Windows interface, change the FourCC code that x264 is recording with [think of it as the 'UPC label' or 'QR tag' for the videos] to a code that these video editing apps can recognize natively. That's all.
Now, you should be able to import all your future game recordings into Vegas and Premiere without problem...

Ok, for a truly easy-to-follow video, that shows examples of how to set the code for Bandicam, Dxtory and Afterburner, look no further than here:

The true version of the video, showing how to adjust the setting required

As you can see, because the main setting to change occurs within the x264vfw interface itself, this change can be utilized no matter what game recording program you prefer to record with (Bandicam, Dxtory, MSI Afterburner, etc.)

**If you are using the 'Official' version of the x264vfw codec interface (Red Logo), the setting to change is indicated in this screenshot below:

»» Note: 
When editing the x264vfw codec with NLEs (Non-Linear Editors) such as Sony's Vegas line of products and Adobe's Premiere applications, you may experience artifacts such as 'trails' or 'corruption' unless you set the GOP setting to "1", which will make "Intra-frame only" encodes. This will encode frames that do not depend on surrounding frames, containing all necessary data within each frame itself (similar to how the MJPEG codec operates, requiring more bitrate/filesize, but MPEG-4 still uses less bitrate overall), which alleviates this problem.

This seems to only occur with Vegas, Premiere, Lightworks and similar products when using MPEG4, but does not occur with most other video editing applications (tested with Windows Movie Maker, CyberLink's PowerDirector, Nero Video, Avidemux, VirtualDub, etc), so you could always extract the portions of the video you want from your recordings with those, then import your portions into Vegas/Premiere/etc and finalize your video projects that way. However, to omit having to do that extra step, you can have your H.264/AVC (x264) recordings editable in Vegas/Premiere/etc by doing the following:

For the Official (Red Logo) x264vfw interface, add "--keyint 1" (without quotations) into the Extra Command area at the bottom
For The Unofficial (Black Logo) x264vfw interface, set the Maximum GO Size to "1"

A lengthy article, talking about recording with x264/H.264/AVC in detail (testing settings, recommendations for speed, etc.) can be found at the blog here:


Have fun editing and See You In The Games!

No comments:

Post a Comment