vegas 9 and amount of cores

wilvan wrote on 9/13/2009, 1:19 PM
Did a quick test , need to complete further ( first finish project ).
workstation :
dell T7500 2 x W5580 Nehalem Xeons 24Gigs RAM (1333MHz )2xquadroFX4800 , 10K drives etc... vista64 minimum processes running - fully editing only optimised .

Did enable hyperthreading in BIOS ( 16 cores total ) , quickly loaded a running veg with 8 cores ( hyperthreading disabled as the system came ) -> vegas32 bit crashes when just previewing timeline.

Didn´t have time to futher test ( need finish project first ) , is there any limits on amount of cores for vegas9 32 bit ?
What about vegas 9 64 bits ?

( since not enough plug-ins yet 64 bit compatible , am unfortunately using vegas 9 32 bit more than the vegas9 64 bit )


Sony  PXW-FX9 and 2 x Sony PXW-Z280  ( optimised as per Doug Jensen Master Classes and Alister Chapman advices ) Sony A7 IV
2 x HP Z840 workstations , each as follows : WIN10 pro x 64 , 2 x 10 core Xeon E5-2687W V3 at 3.5 GHz , 256 GB reg ECC RAM , HP nvidia quadro RTX A5000 ( 24GB ), 3 x samsung 970 EVO Plus 1TB M.2 2280 PCIe 3.0 x4  , 3 x SSD 1TB samsung 860 pro , 3 x 3TB WD3003FZEX.
SONY Vegas Pro 13 build 453  ( user since version 4 ) , SONY DVDarch , SONY SoundForge(s) , SONY Acid Pro(s) , SONY Cinescore ( each year buying upgrades for all of them since vegas pro 4 )
(MAGIX) Vegas pro 14 ( bought it as a kind of support but never installed it )
SONY CATALYST browse 
Adobe Photoshop  CC 2025
Adobe After Effects CC 2025 & Adobe Media Encoder CC 2025
Avid Media Composer 2024.xx ( started with the FREE Avid Media Composer First in 2019 )
Dedicated solely editing systems , fully optimized , windows 10 pro x 64 
( win10 pro operating systems , all most silly garbage and kid's stuff of microsoft entirely removed , never update win 10 unless required for editing purposes or ( maybe ) after a while when updates have proven to be reliable and no needless microsoft kid's stuff is added in the updates )

Comments

Mikey QACTV7 wrote on 9/13/2009, 5:57 PM
I have a dell T7400 with 2 quad cores and 64 gigs of ram at the station. It runs very well rendering on all 8 cores 100%.

I did find out sometimes if I pull media and render to the same drive it will not use all cores to render mostly with HD files.

If I rendered to a different drive than the one with the media (same project) I got all 8 cores to 100%.

There was a back up at the read and write on the drive not at the cores.
wilvan wrote on 9/14/2009, 5:10 AM
Hi mickey , thanks for your feedback .
Maybe my explanation was not well done.

W5580 is a nehalem quad core of which there is 2 -> 8 cores when hyperthreading is disabled and runs fine on both vegas9 32 as 64.

enabling hyperthreading ( in BIOS ) , there is 16 cores
vegas32bit -> crashes when just previewing
vegas64bit -> still to be checked

Sony  PXW-FX9 and 2 x Sony PXW-Z280  ( optimised as per Doug Jensen Master Classes and Alister Chapman advices ) Sony A7 IV
2 x HP Z840 workstations , each as follows : WIN10 pro x 64 , 2 x 10 core Xeon E5-2687W V3 at 3.5 GHz , 256 GB reg ECC RAM , HP nvidia quadro RTX A5000 ( 24GB ), 3 x samsung 970 EVO Plus 1TB M.2 2280 PCIe 3.0 x4  , 3 x SSD 1TB samsung 860 pro , 3 x 3TB WD3003FZEX.
SONY Vegas Pro 13 build 453  ( user since version 4 ) , SONY DVDarch , SONY SoundForge(s) , SONY Acid Pro(s) , SONY Cinescore ( each year buying upgrades for all of them since vegas pro 4 )
(MAGIX) Vegas pro 14 ( bought it as a kind of support but never installed it )
SONY CATALYST browse 
Adobe Photoshop  CC 2025
Adobe After Effects CC 2025 & Adobe Media Encoder CC 2025
Avid Media Composer 2024.xx ( started with the FREE Avid Media Composer First in 2019 )
Dedicated solely editing systems , fully optimized , windows 10 pro x 64 
( win10 pro operating systems , all most silly garbage and kid's stuff of microsoft entirely removed , never update win 10 unless required for editing purposes or ( maybe ) after a while when updates have proven to be reliable and no needless microsoft kid's stuff is added in the updates )

hazydave wrote on 9/14/2009, 9:27 AM
I think what you see there, pulling and rendering to same drive, is just a case of HDD thrashing.

I ran into this several years ago on a project with only my old AMD64x2 processor. This was an HD project, with HDV and Cineform video, along with quite a few 6Mpixel-8Mpixel stills pulled from DSLRs. I had only 2GB of DRAM.

I naievely figured, for long renders to HD output, I would be best off using my fastest drive, which was a 7200rpm SATA. What I got was a fairly unstable system, and the renders were taking forever.

On further investigation, I noticed that neither core was running at 100%... that meant than something else, not CPU, was the bottleneck... hard to believe when rendering AVC out, but true. It turned out that I had reduced my drive throughput to be dominated by seek times, not those nice linear 100MB/s runs.

Moving the output to a separate drive was a big fix. Once I got those stills onto a second drive, I was back at 100% per core. It's not that Vegas isn't trying to use all cores, but if it can't keep them fed, some will be sitting around waiting for input.

Looking at it another way, if you're rendering on an SMP machine and don't have all CPUs at 100%, you have some other bottleneck. Look for it in your I/O.