(Vegas 10) Preview and Performance Degraded!!!

kraz wrote on 6/25/2012, 11:10 AM
I know there are various threads and tutorials about how to set up your PC and Vegas correct for best performance.

I originally - over a year ago set up my computer properly and it worked well

win7 64
16GB RAM
100GB SSD for C drive
1TB d: Drive
(sorry for not being clear with my specs before)

In the last few weeks "something" has happened . and it is now really slow
even down to draft mode my preview stinks - and my renders are taking longer ...
before I investigate "everything" are there a few "obvious" things that would have caused a performance change like that?

No - new major SW install

Comments

john_dennis wrote on 6/25/2012, 2:22 PM
I save the image of the boot system and various installation points, like when I loaded Vegas Pro 11-683 or after Microsoft updates. If something goes awry or if I come in and find my seat warm where someone else has been on the machine, I restore it to a known point.

I've been shooting bugs for a living for 36 years and I take pains not to have to deal with bugs more than I absolutely have to.
Fervid wrote on 6/25/2012, 4:35 PM
As I can't find any useful threads on this that worked...I noticed you mentioned Vegas Pro 10 on XP 64bit. What trick did you use to install to this? I've used things in the past like Orca to edit MSI files and remove OS checks and such, but can't seem to get anything to work. Vegas Pro 10 just does not do well on XP 32bit and I have no plans of upgrading to Win 7 when XP 64bit works fine with competitor products. For the price of this thing they could include Win7 if they want us using it so bad.

As far as your performance issues- Have you had many times where Windows wasn't shutdown properly due to crashes, power failures, etc? I find after extended use especially if there were crashes that the corrupt NTFS indexes and errors make everything slow down. I'll run chkdsk with the /f switch on the main drive and follow the prompts telling you it is in use and will be scanned on reboot. Let it scan next reboot then you may notice a big improvement.

You always have the common defrag and swap file suggestions too. I often put mine on another drive/partition with enough room for a file 2-2.5 times my ram. Starting size 2-4GB so not always resizing and let it fill drive/partition. Otherwise you may need to set it to 0/no swap, reboot, defrag, then set it back if on same drive to make room for a solid block of sectors for it.

16GB is not much room for OS and everything else too unless you have another drive that may be full. You get less than 10% free on most drives and they crawl...even if SSD which could also be getting write errors from wore out spots if you have been putting video to it (even pre-renders or temp files from renders).
kraz wrote on 6/25/2012, 11:35 PM
my bad .. I meant Win7 64
16GB RAM
100GB ssd -

fixed above ..
TheHappyFriar wrote on 6/26/2012, 5:14 AM
Odds are you installed a driver/update that did this. That's what always happens to me, some required update botches something. :/