[Nigel O’neill]

Is there a reason why you are not using the Render As, Sony AVC/MVC template (*.mp4, *.m2ts, *.AVC) > Internet templates?

Optionally, you can use the free Vegasaur Video4YouTube plugin:

https://vegasaur.com/Video4YouTube

I use it exclusively for creating all my Internet YouTube output

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

[Nigel O’neill]

[David Shirey] “I’ve been doing the one week trial for Vegas 14 and it’s nothing but crashes on my system”

Thanks David. Vegas 11-13 were crash happy, but once I disabled GPU acceleration in both preview and renders, it was stable. When it was working, it was great, but it crashed too often and became disruptive.

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

[Nigel O’neill]

Scott, like everyone else here, I use DVDA just to author but not burn. I found that DVA would make coaster after coaster if I used it to burn. I use either Nero or ImgBurn to burn my discs.

My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (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 sounds so familiar. Try: Tools > Preferences, General, remove the tick against Close media files when not the active application

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

[Nigel O’neill]

[Lech Biegalski] “Please tell me why you think that Windows 7 is better for Sony Vegas. How about Windows 8?”

As far as Vegas as concerned, Windows 8 or Windows 10 offer no compelling to upgrade from Windows 7, other than being newer. I had all sorts of driver compatibility and stability issues. Given the age of your system, I would stay on Windows 7.

I had nothing but headaches upgrading to Windows 10 and I had numerous driver compatibility issues with my NVidia 570 as well as RAID controller. My raid had a disc transfer rate of 1 mbps (no kidding!) and when I updated the driver, my entire disk subsystem became invisible to Windows 10. Luckily I was in the 30 day trial period, and successfully rolled back. My other editing system got trashed in the rollback process and had to be rebuilt from the ground up. The lesson I learned is that Windows 10 is not so supportive of older hardware as it claims to be, and that if I do want to get onto Windows 10 in the future, it will be part of a new system build.

In terms of your BSOD, does it occur with GPU acceleration off under video preferences and in the render template? BSOD’s are very serious errors. I used to get them a lot under Windows XP, less under Vista and none under Windows 7.

A quick Google search reveals The “whea uncorrectable error” message that you get on Windows 10, Windows 8.1 on a blue screen can be caused by two things. Either you have a hardware failure or you have problems with your Windows 8.1, Windows 10 drivers that are probably not compatible with your Windows 8.1, Windows 10 operating system.”

Other posts suggest overclocking of the CPU is occurring, in which case, you should check and disable it in BIOS if it is enabled.

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

[Nigel O’neill]

Vegas editing, like all other NLE’S is non destructive. Any trimming you do on the timeline requires you to render out to a new file to make it ‘shorter’.

My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (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 encountered this issue on a laptop years ago. Turns out the CPU cooling policy under the advanced power management settings was set to passive. I set it to active. The fan now stays on, the laptop no longer shuts down unexpectedly, but it does mean that battery life is shortened considerably.

My system specs: Intel i7 970, GTX570, 12GB RAM, ASUS P6T, Vegas Pro 12 (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 based in Australia, Brisbane to be more precise. Sony may possibly know about me (i think), but all my Vegas purchases were made in the US portal going back to 2008. The timing of the email coincides with the Magix acquisition of Vegas, but phishers also use such opportunities to steal identities. I might sit on this email for a while.

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

[Nigel O’neill]

Having your edits on the same drive as Windows is going to always result in a performance hit as Windows uses the same drive for its swap file. Try hooking up a second drive (preferably internal) and run your project off that. 6GB of RAM is pretty low and will result in swapping as video files are pretty big.

Your recent performance hit could be due to a Windows update, but working out which one is going to be next to impossible and uninstalling/reinstalling is a trial and error exercise. I would be looking at antivirus updates, first up, or try disabling antivirus protection during renders (remembering to re-enable when done). I see the laptop comes with Norton AV which can be a bit of a resource hog. I use Microsoft Security essentials and Windows defender now after using Norton, Comodo and Avast which all slowed my system down.

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

[Nigel O’neill]

[Steve Rhoden] “Are those mov video files?”

Pawel, if these files are from an iPhone, they are mov files and I can also attest that the problem is the mov format, having experienced it myself. I think my fix was to copy and paste to a new project and render to another format. If not, use VLC player to convert the source files to MP4 and re-edit.

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