Sony Vegas 10 Slow rendering CPU / GPU rending tested

[Rob Wijnhoven]

Sounds interesting Dave.
Remember from the old days (when disks were still really slow) that I set up a ramdisk.

– Can you give some numbers on performance changes?
– Does the editing feel faster/more responsive?

Thanks for your 50 cents.

[Davd Keator]

Holly smokies! People are still dropping there change here!

After extensive testing with my ram drive vs a Standard 7200rpm drive were nill.

That was till I switched to the Red Camera.

I soon found that 25 Megs a second for a video clip was a bit rough with: transitions, sounds, images, and extra layers!

The main problem was a short 2 minute clip ‘segment for our TV show’ would be about 300 gigs (b-roll – errors – omissions etc.. )

We ended up going with a good areca raid card and 6 2TB drives in a raid 10.

With that setup there was no perceptible difference from a Ram drive and Our raid setup.

I find no reason a all for rendering to a ramdrive, out putting a continuous stream of any sort of compression Youtube-MP4, Blu-ray, DVD, even Cineform – mattered nothing at all. Bandwidth and IO’s are minimal.

Its all about the ability to feed the cpu all the data chunckies on the timeline…

Even with this high speed raif and RED footage, With all the Transitions and effects, I still can’t saturate my Core 7 2600K.

I Render 2 to 3 segments just to get 100% usage.

President: http://www.VertexMedia.com

[Trey Wingbat]

I recently rendered an HD project that had tons of HD clips in the Sony Vegas 10 timeline. My RAM usage in the Windows Task Manager indicator showed I was using 11.9 GB of the 12 GB I had in my system to render, so I bought 12 GB more. This is in a system with an Intel Core i7 980 EE processor, and 2 NVidia 580 GTX graphics cards.

I had now set the dynamic RAM preview to 16 GB, meaning 67 percent of my total RAM was allocated to that. I did also have problems with Vegas crashing a lot when I was working on my massive HD project, so I thought I’d increase the dynamic RAM preview.

Then my next so-called project was to convert over an old football game from VHS to digital format for personal archive. This was in SD, with no special effects or anything – I just chopped out the commercials where I needed to. I went to render, and things were fast at the start too, and then just slowed down to beyond a crawl – Vegas was doing less than a frame a second it seemed like! I let the render go for a few days, wondering if the source file was somehow different or even corrupted, and that things may speed up again. Even after a few days, the file was barely over 50 percent rendered. Normally it should take 45 – 45 minutes to render SD footage of this length. My CPU usage at this time was about 8 percent, and RAM usage was 21 GB in the Windows Task Manager. My CPU didn’t seem to working too hard, and the fans in the computer didn’t speed up like they normally do during a render.

Luckily, I found this post, cancelled the current render as I didn’t want to wait several more days for it to finish, and now have reduced dynamic RAM preview to 2 GB, and my CPU usage is 66 percent, and my RAM usage 4.2 GB in Windows Task Manager. The fans are speedier now, and Vegas just calculated 40 minutes to complete the render for about a 2 hour clip – which is right on par.

Dynamic RAM preview – watch how you use it!!!