[Nigel O’neill]

Randy

Colour correct 1 event the way you want it. Right mouse click that event and select Copy. Ctri-click or shift-click the remaining events you want to apply the correction to, and then right mouse click and select Paste Event Attributes. Viola!

Shift-clicking allows you to select a sequence of events or tracks in order, whilst ctrl-clicking allows you to choose them out of order or at random.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Paul

I have seen third party FX do similar things in Vegas. I had a particular plug-in that worked fine in 10c, but when I upgraded to 10e, the plugin was changing the video gamma/curves randomly on the timeline and in the subsequent encode in my multicam edit, giving crazy results that looked almost cartoonish.

I reported it to the plug-in developer and also emailed Vasst for advice and we concluded that Sony had probably modified the OFX library slightly to cause the plug-in to misbehave. After much to-ing and fro-ing, I reverted to 10c so I could complete my project. I later reproduced the problem on another editor’s PC, reported it to the plug-in developer again and left it that. I don’t use that particular plug-in anymore for multicam edits, but it is OK for single track edits.

In summary, consider rolling back your Vegas version and report it to Vegas

https://download.sonymediasoftware.com/current/

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Dave/Steve

Anyone who posts on this forum using an obviously pirated image for an profile picture surely cannot be taken seriously. Much of the advice provided by John is either so far off topic or irrelevant that I find it becoming quite tiring to read through some of the posts that take off on tangents and lead you on a wild goose chase.

Whilst he is trying to be helpful, some of the advice provided actually is too generalised and as such has little to do with the issue at hand.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Paul

Hope this gets to you in time and that you are feeling better. I would roll back to the earlier version of Vegas 11 that worked for you, get the job done then try to figure out what went wrong. You can download earlier versions from here:

https://download.sonymediasoftware.com/current/

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

What version of Vegas are you on and are you using x64?

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Hank

Video editing is non-destructive and will not modify the source to save disk space. When you are ‘deleting’ portions of video, you are in fact trimming by placing markers in the video stream in a proxy file that the software later uses to encode a new file when you ‘render as’. A similar principle applies when adding FX. Video editing on PC’s has come a long way since the days of linear and destructive editing of film stock.

Video editing is a space hungry application, and you will find that during the encoding process, Vegas creates temporary files before writing out the final file, so you really need disk space.

For video editing, the absolute bare minimum of drives you should have is 2: a C: drive of say, 500 GB, and a 2nd drive of say, 1TB. I run 5 drives, 2 of which are mirrored and another 2 are striped, in addition to my C: drive.

You can in theory get a 2TB drive and run that as your C: drive and edit solely on that, but encoding performance will suffer. The overall video editing experience may be impacted as system processes compete for the hard drive. Partitioning 1 drive into 2 or 3 does not help as the same physical read head mechanism has to traverse the 1 drive. Having a second or third drive means you can spread the load.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

Here’s a tutorial 🙂

https://www.pcfix411.com/consultation/42-tutorial/59-change-volume-and-insert-volume-envelope-in-sony-vegas-9

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

You can add it as an event level FX, or to the project media as Steve suggests. Personally, I add it to the event itself as it suits my particular set of circumstances.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

This is a very old thread, and no one is likely to respond. Start a brand new post and you might get a response from the guru’s. I am stumped.

Provide details of your source format, and where the problem is occuring. e.g. it is playing fine and happens after a certain amount of time has lapsed.

Is it only happening during transitions?

Is it images it is happening to, such as during pan and crop?

Are you mixing formats e.g. AVCHD or HDV or DV?

Have you ticked ‘Adjust source media to match project or render settings’ and it is still happening.

Are you doing a CBR or VBR encode? Are you doing a 2 pass VBR encode?

What ‘render as’ template are you using? Many posters work with NTSC, and some advice is NTSC specific.

All this information is helpful to the guru’s.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Nigel O’neill]

I have an ASUS GTX 970 with the recommended drivers and had an older unsupported GPU card (GT 9000)? The stability issues remain. Perhaps it is my system.

The only common denominator is NVidia cards. I did for a while have to use a USB video card, and it was a nightmare with Vegas.