[Nigel O’neill]

Just out of curiousity, is your file system FAT32 or NTFS?

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]

John

I am not disputing your expertise. Out of the box, Vegas does indeed default to NTSC and when I select the PAL template, I have to change the deinterlace method from none to blend. It does this on every single installation I have done.

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]

[John Rofrano] “Change your deinterlace method back to the default which is Blend Fields and your problems will go away.”

John, there must be a difference in the default PAL project properties template. Out of the box, mine defaults to NONE. This has also happened to other editors I work with in PAL-land.

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]

K-lite and other codec packs are strongly recommended NOT to be used with Vegas and can cause massive problems during the edit stage and render phase. Installing the K-Lite codec pack is the WORST thing you could have done.

The first thing I would do is uninstall the K-Lite codec pack, reboot your computer, uninstall and re-install Vegas Pro. With any luck, this will re-establish the codecs that came with Vegas.

Search this forum and you will find this advice everywhere.

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]

Bardon

You can have multiple and different versions of Vegas on 1 PC. For example, I have a 64 bit Windows 7 operating system and I have SVP version 9, 10 and 11 (32 & 64 bit) on the 1 PC. That’s 6 versions! Why? Because you can!

I mainly edit using SVP 10 x64, but I have recently used SVP 11 (x64) to deliver 2 multi-cam projects using an HDV source. I did find it necessary to disable Track Buffering in the Audio Device preferences as Vegas would constantly crash otherwise. I also observed that SVP is quite sensitive to video driver updates. In my case, I had to revert to the original drivers that shipped with Windows 7.

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 usually split the event to what I need stabilised beforehand, but the effect is applied quickly. I do this before adding any other FX, otherwise the stabilisation takes longer.

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]

Editing wise, you have the necessary minimum horse-power to edit. Video card wise, it’s hard to tell. My laptop supposedly has a SVP11 supported card for GPU acceleration, BUT the latest required driver from ATI to enable GPU acceleration crashed my laptop constantly. Not Vegas, Windows 7. It’s my first ever blue screen in Windows 7 I have seen. The project would load and work for a time and then, bang, Windows 7 would have a cow.

I ended up rolling back the driver to the one that ships with Windows 7, which though it does not allow GPU support/acceleration, has restored stability and my sanity.

Your setup is probably OK to single camera edits, but will struggle with multicam.

In terms of your laptop, you might want to consider eSATA via an Xpress port (if the model supports it, I cannot tell) or an external USB 3.0 drive (which its does support).

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 am assumming a VHS-C or Video 8 source, which isn’t all that great as a video source to begin with, but here’s some basic tips.

You could apply a slight colour curve and a touch of contrast (0.010 or 0.020) to reduce the washed out look and possibly add a slight sharpening.

The colour corrector is only necessary (in this case) so that your whites look white. If you just want to ‘boost’ your colours and give them a bit more ‘oomph’, take a look at Saturation adjust and boost your mid tones (it’s one of the presets).

Shooting outdoors in bright sunlight is always a challenge, and I would shoot with a camera using an ND filter to be able stop down the iris.

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 not had such issues. My only observation was that a stabilisation added in SVP10 does strange things when the same project is opened in SVP 11.

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 would report the crashes to Sony.

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