[George Dean]

Hi Carlos,

Go ‘View’ > ‘Window’ > ‘Video Scopes’. From this window you can resize it, move it, and select which scope(s) to view, or all of them, plus some other adjustments.

Best Regards……George

[George Dean]

Hi Robert,

I posted in the other thread you posted your issue to. Perhaps those methods will get you out of a jam.

I suppose you have already tried a Full Reset, although if you have tried a new project and it works fine, I would agree the problem is embedded into your problem project.

Best Regards……George

[George Dean]

Hi Robert,

Here are two methods that may or may not help, that you may or may not have already tried, but they are simple and quick to test.

Method 1 – I’m sure you have saved your project many times. If you are using ‘Save’ any garbage build up is staying with the project. If you use ‘Save As’, to a different name, this will dump some of the built up garbage and may straighten things out.

Method-2 – Open 2 entances of Vegas Pro. In the first, open your problem project. Select everything in the timeline. Then copy and paste into the second project. This method may leave behind the garbage. However, using this methods has some restrictions. Copy and Paste from one timeline project to the other will only copy the cuts, edits and effects applied to the events in the timeline, it will not copy anything applied at the track level, Project Media bin level or Project level. If you have just a few effects on the track, media, or project level that you can easily duplicate in the new project, this may work, if you have extensive track, media, and project level FX’s, it may make this method unreasonable.

Best Regards……George

[George Dean]

Hi Sholeh,

If I’m not mistaken that camera has S-Video, Composite, and Firewire connection. I would pick up an inexpensive Firewire card and connect using Firewire which should give you the best quality. If the card doesn’t come with software, you may already have software on your computer or download a free app. Ah, that’s for Windows, not sure about the Mac.

Best Regards……George

[George Dean]

Hi Michael,

I cannot tell from your video, but I have a suspicion that there maybe some Track Motion going on with your template. If that is correct, Track Motion and Track FX’s will not copy and paste.

How large is the template you are using for this example, that is file size? Maybe you can upload it here or a file sharing website that I can then download and get my hands on it. I’m on a limited data download service, but if the whole template (I assume it is probably a zip file) is less than 100 mb, I could handle that.

Best Regards……George

[George Dean]

Lee @ “but if I use the original clips before they were converted to constant frame rate they run smoothly on the preview window. ”

Hi Lee, the first question I would ask is, if the original clips run fine, why are you converting them? That’s not a wise crack question, I’m serious.

Although, generally, I agree, variable frame rate is often not good for NLE’s. And, whenever I hear from a smartphone or screen capture, I ask is it variable frame rate. But, there are many users of variable frame rate that have no issues with it. So, if I didn’t have any issue, I would not bother converting/transcoding to constant frame rate.

Beyond that, in addition to Handbrake, I would also suggest something like the free app MediaER Tool Kit. It is easy and fast and if the results were acceptable to me, I would go for it before Handbrake. Handbrake is a great tool with a lot of power and flexibility. With that power and flexibility comes complexity. If you are a Handbrake power user, no problem filtering through all the settings and getting the results you want. If not, maybe a simpler tool like MediaER Tool Kit will suffice.

And, beyond that, proxies (as Francois points out) may be your friend.

Best Regards……George

[George Dean]

Hi John,

We need some additional information, but before that…..

Although this is too late, never, never, ever install K-Lite codec pac, it has the capability to screw your system up and only makes Vegas Pro worse. I assume when you say ‘Magix’ you are referring to Magix Vegas Pro 14.

If you used the Windows Control Panel to uninstall K-Lite, you may also want to take a look at your C: drive and delete anything name K-Lite, as well as, look at the Windows Registry and delete any references to K-Lite. If you are not comfortable with editing the registry, you may want to use something like CCleaner to clean the registry.

OK, before anything, I recommend doing a full reset of Vegas Pro. Hold down the ‘Ctrl+Shift’ keys while you double left click on the Vegas Pro desktop shortcut. In the small window, check the box ‘Delete all cached application data’, then left click on ‘Yes’. This will reset Vegas Pro to the original installation settings, and more importantly delete all the pesky cached application data that builds up and over time may cause Vegas Pro to do strange things.

Assuming that does not make a difference, can you post screenshot of your Project Properties, Preferences (display and video tabs), and your source media specs. You can use the free app Mediainfo (in Text view mode), which provides the specs that may be important to members here to help.

Also, what device was used to get your source media (mp4) files? A camera, what model, etc? Or screen capture, what program? Or download, from what source?

Are you editing in 32-bit floating point, or 8 bit?

Best Regards……George

[George Dean]

Renato,

I would make some small changes in your Preferences, which you probably have tried, but perhaps humor me….

Preferences > Preview device tab > (Display adapter) uncheck ‘Wait for vertical sync’

Preferences > Video tab > Dynamic RAM preview max, change it from ‘0’ to ‘200’

Preferences > Video tab > Maximum number of rendering threads from ‘2’ to ’12’

Then restart Vegas Pro and start a fresh project. Add some media to start a fresh project, a little bit at a time. Play the preview as you go along, if things work fine at first, keep adding and checking the play back until you either have a good size project compared to the problem project, or you run against problems, then report back here how that test proceeded.

As for the proxy. Vegas Pro can build a 720p proxy of your 1080, or 2K, or UHD, or 4K media. As a default, Vegas pro will build proxies when you add 4K/UHD media to the Project Media bin. Your media is 1080p, so you need to manually build proxies. Right click on a source media video in the Project Media bin, and from the menu select ‘Create video proxy”. Depending on how large the video will depend on how long Vegas takes to build the proxy. There is a progress bar displayed at the bottom left of the timeline. The proxy is written to the same folder as your source media, but you will not see it in the Project Media bin.

Add the source media from your Project Media bin to the timeline. Vegas Pro will automatically use the smaller resolution 720p proxy for viewing if your Preview Quality is set for ‘Draft’ or ‘Preview’. If you set the Preview Quality to ‘Good’ or ‘Best’, Vegas will automatically run the preview from your original 1080p source. When you render your project, Vegas Pro will automatically use the 1080p HD source media.

So using Vegas Pro Proxy feature, once you have selected to build the proxies (either one at a time or select them all and proxies will be built for all the video you selected) is automatic after that and you do not have to switch anything out before rendering.

About Snapshots: If you feel the amount of snapshots you use is causing the problem, then the test project (above) I suggested should reflex that, once you get to a certain point if you see the same issues you are having with your current project. I would not think a bunch of snapshots (providing they are about the sme resolution as your project, would be the cause.

Another thing you can try, is copy everything in your project along with the .veg file to a different folder on your hard drive. Rename the original folder, as an example the folder name is ‘Snapshot Project’ to ‘X-Snapshot project’. Then load the veg fie form the new folder and if Vegas Pro prompts for the project source files, point it to the new folder. Sometimes garbage gets somehow associated with a project causing strange actions and simply changing the location will help. It is a long shot, but others have reported success doing this.

Best Regards……George

[George Dean]

I have read that some have a work around, but as inexpensive as a firewire card is that’s the way I would go and then it is direct into Vegas as you are familiar with. Just my opinion.

Best Regards……George

[George Dean]

Michael @ “Hi George and Graham, thank you for your quick replies. Sure this is the site: https://delimproductions.jimdo.com/templates-free/ the only thing most of it is in Spanish I hope that’s not a problem. The so called templates are vegas files I have worked with some of them in the past but now because I made a new vegas project I am not sure how to connect the 2.”

…well, yea, that poses a problem for me! I can barely handle Redneck let alone Spanish!

However, maybe I can help with this part, “but now because I made a new vegas project I am not sure how to connect the 2.”

Can you explain your workflow, how you are trying to “connect” the two projects.

Best Regards……George