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 and Lightworks, for those who were having problems. In this example, I am recording with an x264vfw (Komisar's Unofficial) interface, which sets up h.264/AVC encoding, used as an "External Codec" in Bandicam :
(This example will show how to set the FourCC code using Bandicam, Dxtory and Afterburner)
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 record with (Bandicam, Dxtory, MSI Afterburner, etc.) - but we're all using Bandicam, right?
[Both videos were recorded with Bandicam's "Rectangle On A Screen" capability]
If you are using the Official version of the x264vfw codec interface, the setting to change is indicated in this screenshot below:
Note: When editing the x264vfw codec with NLE (Non-Linear Editors) such as Sony's Vegas line of products, Adobe's Premiere applications and Editshare's Lightworks, you may experience 'trails' or 'corruption' unless you set the GOP setting to "1", which will make Intra-frame only encodes [or it may not Import at all]. This step 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 (InformationFrames/Keyframes Only) which requires more bitrate/filesize, but don't worry MPEG-4 still uses less bitrate overall in this mode). This issue seems to only occur with NLE's such as Vegas, Premiere, Lightworks and similar products; but does not occur with most other video editing applications (tested with Windows Movie Maker, Nero Video, Avidemux, VirtualDub, etc).
[For the Official x264vfw interface, add "--keyint 1" (without quotations) into the Extra Command area at the bottom]
Have fun editing and See You In The Games!