Just a Quick Tip, for those using Sony's Vegas line of products for editing. I was working in a recently-upgraded-to Movie Studio 13 Platinum, enjoying the new version and trying the FXHOME HitFilm Effects plug-ins that come with it. Then, the plug-in effects seemed to stop working today - they didn't show the effects in the Preview at all when I re-opened the Project. I could open the Settings Panel for the plug-ins and change them, but could not 'see' the HitFilm effects. I made a few recent changes to my System, one of them being upgrading my NVIDIA GPU drivers. So, I rolled them back, installing an older version (going back to 332.21 - a version I chose so that I could also use CUDA for Rendering, among other things) and boom - the Hitfilm effects were back ...to the future ...with a vengeance ok I'll stop. So, if anyone else runs into this problem with these HitFilm Effects and Vegas [it may help no matter what Edition you have installed], try rolling back the GPU drivers.
[N.B.: This issue was encountered and solved on my NVIDIA GPU, it is unknown by myself, at this time, whether this issue exists with AMD/ATi GPUs]
Have fun editing your gameplay adventures - and See You In The Games!
Since the most popular answer on the ongoing poll I have running here at the blog ("what type of posts would you like to see more of in 2014" [top right, it will run until the middle of the year]) is "Tips And Tricks Of Video Capturing And Editing", I thought I would start more of these types of requested posts by sharing this fix for a problem that seems to pop up intermittently with Sony's Vegas line of products.
Whether you have just re-installed it or whether it has been on your system for a while, 'something' is causing the EULA (End User License Agreement) to pop up and require you to agree to it, even if you have already done so and/or Registered the program. This question comes up once in a while on the Sony Creative Software Official Forums and I have seen it elsewhere. I was recently reminded of it again because it is also something that just happened to me on my system! I didn't re-install Vegas or make any large changes related to Vegas, yet this little guy started popping-up every time I started up Vegas Movie Studio HD**:
The popup that comes up for some people, every time they start Vegas
The fix is a simple one, originally suggested by a Sony Forum Moderator and quoted/forwarded frequently on the official forums, to those who come and ask the question there. Although it seems more like a 'workaround' than a 'fix [in my opinion], it works just fine and since it is officially supported by Sony and I just tested it for verification myself [that it does indeed solve the problem], so now I share it here with you:
To stop the EULA popping up every time you start Sony Vegas, simply open Windows Explorer and navigate to the folder where you installed it on your system.
Then, find the file that is titled, simply, "eula". There will be no Extension showing, even if you have the Windows option to 'Hide Extensions For Known File Types' turned off.
Rename (or delete) the file. That's it!
Now the EULA cannot pop up anymore and won't, every time you start up Vegas to edit your game captures.
**Although this example shows steps for the Movie Studio version of Sony's Vegas Video editing line, the EULA 'fix' is the same steps for Vegas Pro, Vegas Edit or other versions of Vegas
Enjoy popup-free video editing once again - and See You In The Games!
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"
[The title sounds like a spell of some sort.. BEWARE THE TRAILS OF CORRUPTION]
As part of the 'And More' of this blog, I would like to present a Tip that will help anyone that may be experiencing the 'trails' or 'corruption' effect that appears when importing an Xvid-recorded video into the Sony Vegas line of products.
This effect can occur no matter what game recording software you are using (Dxtory, Bandicam [as an External Codec], MSI Afterburner, etc.**), if it is configured to record with the Xvid codec downloaded from the Xvid.org website. An example of the corruption (and the associated setting that can fix it) can be seen in this short video:
The first portion is an Xvid Codec recording with the Motion Search Precision setting ON (which is the default setting if you are using the "Real-time" Quality Preset to record with, for instance).
The second portion is the same Xvid Codec recording, but with the Motion Search Precision setting OFF (Set to "None" (0)).
That is all that need be changed to fix this problem with importing Xvid recordings into Vegas, all other settings can remain how you prefer. One more example of what can be fixed/corrected (a still frame from a 'corrupted' video) is shown here:
To change the required setting in the Xvid Codec interface:
After selecting Xvid MPEG-4 Codec as your recording codec [in whatever game recording software you prefer], click on the Configure button to open the Xvid Configuration window. Then, under the More section, Quality Preset, click the "more..." button past the pull-down menubar and it will Question you with the choice to Copy the values that cannot be changed to a "User Defined" setting. Clicking "Yes" will copy the Real-time Preset settings to the pull-down selection called "User Defined" and then you can change the preset settings within.
Click to see Full Size
In the Motion Precision category on the first tab (Motion), next to Motion Search Precision, click on the pull-down menubar and click on "0 - None", to turn off Motion Searching when recording using the Xvid Codec.
Click to see Full Size
That's it. Sony Vegas Movie Studio and Sony Vegas Pro should both now be able to import your Xvid format recordings, no matter what game recording program you are using (Dxtory, Bandicam [as an External Codec], MSI Afterburner, etc**).
** Users of Bandicam will find that a built-in/optimized version of Xvid is already included within the program codec menu and provides good capture ability/quality, it just does not have the codec-native configuration interface (to change settings) and this version will not natively import into Vegas, as of this version. If you are using Bandicam as your game recording application and you wish to record with the built-in/optimized version of Xvid and import your recordings into Vegas, simply download the Xvid codec from the Xvid.org website. Then, Bandicam's version of the codec can be opened within the Sony Vegas line of products. The problem presented above in the article does not occur when using Bandicam's built-in/optimized version of Xvid†† †† It should be noted, that this issue of "corruption" or "trails" or "glitchy-ness" does not occur in all Video Editing Applications. While most NLE editors (Vegas, Premiere, Lightworks, etc) will experience this, many 'Pro-sumer' grade video editing programs, do not. I have personally tested editors such as Corel's VideoStudio Pro, CyberLink's PowerDirector and even Microsoft's Movie Maker - and none of these editors display the issue mentioned herein. If a user desires to stick with Xvid as their recording codec (indeed a speedy and potentially semi-high quality codec), then perhaps utilizing one of these other editors, should be considered.
[Update 1: Added still frame examples of the difference, to help those who perhaps could not easily see the difference in the video or in their own renders, from the recorded video/output, found at **] [Update 2 (2016-12): Updated some Screenshots and added additional example Screenshots of what the various Menus and Properties windows look like (to Vegas Movie Studio 13, the version I currently own at the time of this Update)]
As part of the 'And More' of this blog, I would like to present a Tip that will help everyone asking about and experiencing the 'blurry/ghost-y' effect that appears when rendering a video that they have created in the Sony Vegas line of products. An example of this blurring or ghosting is shown in this short video:
Recorded with: Bandicam @ 1080p, Quality 70% Recorded Game: Left 4 Dead 2 @ 1080p, Dark Carnival Level Recording Output: Rendered with Sony Vegas Movie Studio HD Platinum Edition, Sony AVC codec @ 1080p, 15Mbps data rate for smaller upload size
The first 10 seconds is the 'Smart Resample' setting that is on By Default in Sony's Vegas product line (Movie Studio, Movie Studio Platinum, Vegas Pro). The second portion is the same recording but with the 'Disable Resample' setting. Even with some quality loss from YouTube, the difference between the first "blurry" output that many have experienced - and the second crisper, clearer version without it can hopefully be seen... So then, how to fix it?
The simplest way is to right click on the video event (video clip) and open the Properties of the event/video. The pop-up menu that should show up when right-clicking on an event/video is seen here (shown from Vegas Movie Studio 13):
Then in the 'Properties' window, simply click on the radio button choice that indicates "Disable resample", as seen here (example Event Properties window shown from Vegas Movie Studio 13):
That's it!
Now, with any further work you do with the video, you won't have to worry about the 'ghosting' effect happening to you in the end render output. I suggest doing this at the beginning of your project and as you add new video clips, that way it is done for the entire clip, even if you split it up into parts.
**Below are two examples, one showing the "ghosting" or "blurring" effect in more detail (for those that could not quite tell the difference in the video example), shown as frames extracted from the video itself:
Example frame from video showing the "ghosty" or "blurry" effect that can occur with Resampling Enabled in the Sony Vegas Video Rendering Options (Smart Resample ENABLED).
Example frame from video showing the absence of the effect/problem that can occur with Resampling here being Disabled in the Sony Vegas Video Rendering Options (Smart Resample DISABLED).
Behind-The-Scenes: Additional Info About The Above Thingamajig And Related Doohickeys
While the above steps solve the problem, I would like to go into more detail as to why this is occurring. I see this question a lot in forums, particularly ones about gaming and video editing, and would like to clear up more of what is going on.
Many people blame Vegas and say that the resampling (which is essentially a re-structuring/blending device to correct for framerate, interlacing, etc.) is not working properly. Although Sony's method could use a little work, the program portion of it 'detecting' and 'kicking in' is actually working as intended...
One of the reasons why this ghosting or blurring occurs, is that the project framerate (what Vegas 'assumes' you are going to be rendering to) differs from the recorded source (that source being your gaming video, recorded with Fraps, Dxtory, Bandicam, etc - whatever you prefer to record with).
One way to check what the output goal that Vegas has set in mind is: open up the Project Properties by going to the Project pull-down menu and select Properties. That pull-down menu looks like this (shown in Vegas Movie Studio 13):
You can also open up the Project Properties by clicking on the button/icon that looks like 'a grey box with an arrow in it', found in the top toolbar and also is found just above the main video preview window area. The button to click on looks like this (shown in Vegas Movie Studio 13):
In the Pro versions of Vegas, the pull-down menu will not be called PROJECT, it will be called FILE (but it will still be the first menu in the Toolbar). The small button that can also be clicked on, will still be located in the same place, just above the Preview Window area, as shown above.
Here is an example of what the Project Properties window will look like (shown from Vegas Movie Studio 13):
The main thing to check in the Project Properties, is the Frame rate (shown pulled-down and highlighted in the screenshot above).
Vegas' resampling capability will kick-in even if the frame rate is off by a small amount, such as if you are using a recording that is 30 frames-per-second, but being edited with a Vegas project setting/output format that is 29.97 fps (which is most standard DVD/BluRay/Render Presets that Vegas may pre-load).
Whatever frame rate you are recording at (30fps, 60fps, etc.), double-check the Project settings to see if it is the same as your recording. If it isn't, Vegas will try to restructure the video and blend the differences, resulting in that 'blurry', 'ghosty' output that many are familiar with.
[To be fair, Vegas is attempting to help/compensate for the framerate differences of possible recording devices (cameras,etc), and in live-action[real-life] recordings, it does help in a way; but in videogame recordings that are already crisp and clear, this process is not needed and results in this ghosty/blurry 'problem' for gameplay recorders/editors]
There are actually three places in Sony Vegas that keep track of the frame rate:
1) In the Project Properties (eg. pulldown the PROJECT menu in the toolbar and choose PROPERTIES (FILE menu in Pro versions of Vegas))
2) Shown In Each Event/VideoClip (eg. Right-Click each of your clips on the Timeline and click PROPERTIES)
3) In The Render Options (eg. RenderAs and see it in the CUSTOMIZE TEMPLATE settings (CUSTOM button in Pro versions of Vegas))
If just Disabling Resampling [via the event on the timeline] is not working, try to see if all of these three locations match the framerate of your recorded video clips.
Alternatively, you could try to change only the framerate in the final Output Format rendering settings to match your source recording(s) framerate (location is shown highlighted below in an example Settings window from Vegas Movie Studio 13):
Looking at the Frame Rate (shown highlighted, near center of window) in a Template of High Quality Render Settings (shown from Vegas Movie Studio 13). Feel free to use these Settings in your Projects!
By doing this one adjustment at the very end of your editing process (just as you finish up and start the Render) - as long as you are sure that all of your source clips involved have the same framerate and you are going to do your final render out to that very same framerate - then you can try to change this one setting at the end and see if it works as well (you may still have go back and change all three locations if it does not).
Note that although the Setting for "Frame Rate" may only allow you to go up to "59.94fps" (even if you type it in); don't worry, that framerate is still seen by YouTube [if you are using YouTube to share your videos] as "60fps". I did a short Vegas render and Upload to YouTube to test it out [kept Private, done just for this test] and below is what it looks like at YouTube after Uploading:
As you can see, even though Vegas had "59.94 fps" in the Frame Rate box/area, it is a Standard Framerate and accepted as "1080p60HD" at YouTube.
Whichever way you go about it, hopefully checking these few things will help you create clearer, crisper game recording videos.
+EXAMPLE+of+changing+motion+search+precision+1+.png)
+EXAMPLE+of+changing+motion+search+precision+2+.png)
%2BThe%2BGame%2BTips%2BAnd%2BMore%2BBlog%2B.png)
