Comments

DavidMcKnight wrote on 4/12/2009, 6:31 PM
What plugins, filters, or effects are applied? Some of those will only work with one core. Some render / filetypes will only work with one core too, not sure if wmv is one of them.
Also, if any of the drives you are rendering to or from are external, it's possible that cpu is not your bottleneck but that the cpu is waiting on data transfer across usb or whatever you're using. Of course if all drives are internal I would not think that would be a problem.
tonyatl wrote on 4/12/2009, 6:44 PM
Nothing is on the footage,captured it dropped it on the time line and started rendering to a internal sata drive which is not the system drive. I upgraded to quad and its just annoying. Maybe the 7 core is the way to go but to me.If this one isnt using even 50 percent whats the point?
tonyatl wrote on 4/12/2009, 6:53 PM
I think I figured it out. the content was on e and I was rendering back to e .I changed it to G and the render time dropped dramatically.
TheHappyFriar wrote on 4/12/2009, 8:11 PM
could be it couldn't transfer data fast enough to even give the CPU something to do.
blink3times wrote on 4/13/2009, 2:57 AM
How much cpu gets used depends entirely on what your doing at the time.

I've watched my cpu whiz along happily at 95% and the frame counter ticking away with the greatest of ease..... and then I hit something like a cartooner effect and cpu drops off to 30% and the frame counter slows to a crawl. It stays that way until the entire effect has gone through then it goes up again.

It's clear it's a bottleneck some where and I may be wrong but I've always assumed it to be memory..... and there is not a whole lot you can do about it.
rs170a wrote on 4/13/2009, 4:32 AM
I think I figured it out.

Part of the solution was rendering to a different drive.
The other part of it is that you're rendering to a different format than your source footage.
This means that Vegas has to process every single frame to convert it to the new format and this will definitely slow down your rendering time.

Mike
baysidebas wrote on 4/13/2009, 10:34 AM
Also, every once in a while check the disc properties, particularly if things are going much slower than expected. Windows has a nasty habit of reverting down to PIO mode after encountering 6 trouble spots in accessing discs. Make sure that the properties box specifies DMA access and not PIO. There's a way to reset this,

http://support.microsoft.com/kb/817472


"According to Microsoft
After the Windows IDE/ATAPI Port driver (Atapi.sys) receives a cumulative total of six time-out or cyclical redundancy check (CRC) errors, the driver reduces the communications speed (the transfer mode) from the highest Direct Memory Access (DMA) mode to lower DMA modes in steps. If the driver continues to receive time-out or CRC errors, the driver eventually reduces the transfer mode to the slowest mode (PIO mode)."