VMS Platinum - Another Patch?

hal9001 wrote on 5/2/2006, 12:31 PM

I'm having problems rendering mpg files. The computer keeps crashing about 20% into the render. I do not have problems with VMS 4.0. Is there another patch in the works from Sony? I see that quite a few people have the save problem.

Comments

soaringrocks wrote on 5/2/2006, 9:30 PM

Hard to tell from your message. What version are you using now?

hal9001 wrote on 5/2/2006, 11:55 PM

Sony Vegas Movie Studio Platinum 6.0a

ScottW wrote on 5/3/2006, 6:13 AM

My suggestion would be to do a "dust bunny" patrol inside your computer. Get some canned air, power the machine down, open it up and blow the dust off the CPU fan, heatsink, motherboard, everywhere.

Rendering is one of the most processor intensive jobs you can ask your machine to do and the increased heat as a result could be part of your problem.

--Scott

hal9001 wrote on 5/6/2006, 5:44 AM

I tried the dustbuster but it did not work. However, I have found a solution. I have a Pentium 4 Type D with Hyperthreading, one of the first on the market. I have found that changing the affinity to only CPU-0 has stopped the crashing. This is done by selecting the process in Task Manager and clicking right-mouse and selecting 'Set Affinity'

To do this permanently download imagecfg.exe from here and follow the instructions.

address = http://www.robpol86.com/Pages/imagecfg.php

Instructions
----------------
Copy imagecfg.exe to %systemroot%\system32 (or C:\Windows\system32), and %systemroot%\system32\dllcache (or C:\Windows\system32\dllcache).
Doing so will make imagecfg a system command.

This tool only works on NT based operating systems (Windows NT, 2000 Family, XP Family, 2003 Family, Longhorn/Vista).
It will work on Multiprocessor machines and Uniprocessor machines with HyperThreading Technology (and probably multicore processors).

I was unable to find any documentation for this tool on Microsoft's website.
To use this tool to set affinity masks for an executable, type the following command in a command prompt window or run dialog:

imagecfg -a 0x1 c:\path\to\file.exe

If the above didnt work, try typing the following:

imagecfg -u c:\path\to\file.exe
imagecfg -a 0x1 c:\path\to\file.exe

0x1 = CPU0 (first logical/physical CPU)
0x2 = CPU1 (second CPU)
0x3 = CPU2 (third CPU)
etc...

Thanks for all your advice, it has been much appreciated.