-
Vegas Pro 10 Cuda perf. improvements/comparison
Hi,
I have just installed Vegas Pro 10 64 bits on my machine, and run the test I ran with Vegas Movie Studio 10 Platinum HD, Vegas Pro 9 64 bits, Premiere Pro CS5 (see below for the details and the results of these tests).
Here is what I get:
1) Sony AVC MP4 rendering: 2’20 (was 6′ with VMSP 10). The GPU is now used at 11% (was 0%). Only 4 of the 8 CPU cores are used, and the total average CPU workload is about 25% (and the file I/O are at about 3 MB/sec, far below my disk throughputs).
2) MainConcept MP4 rendering : 3’20 (exactly like before with VMSP 10 and VP9).
So, there have been great improvements with the Sony AVC plug-in, however, it is still far beyond Premiere Pro CS5, which does the job in 1’40.
Interestingly enough, I get the same results starting from my EOS 7D MOV clips, than if I render from the Cineform-converted AVIs. And with no crashes!
Hope it helps,
Frédéric— below the details of my previous benchmark —-
Hi,
Still investigating the GPU issue on my Vegas Movie Studio Platinum HD 10 / i7 950 / nVidia GTX460 / 4GB RAM (GPU load stays at 0% with it, while it does not on many other Cuda-enabled apps), I have made a test with an eval version of Premiere Pro CS5 (which also claims to support nVidia Cuda to enhance both preview and rendering) to compare the rendering times of PPro CS5 / Studio 10HD / Vegas Pro 9.
In the 3 cases, I am rendering a simple project of 1’40 made of 6 MOV clips taken out of my Canon EOS 7D, the format being 1920×1080 25fps. There is no effects and no transitions, just 1 video track and 1 audio track.
In all cases, the rendering is made to H.264 1280×720 25fps progressive / 1 pass / 8Mbps average / 10 Mbps max / AAC 128kbps / 48kHz stereo, with a MainConcept encoder
1) processing on Premiere Pro => 1’45. It uses the 8 cores at 98-100% and the GPU at 4-8%
2) processing on Studio => 3’26 (+ 1’10 of processing in Cineform to convert the MOV to AVI to avoid crashes). So rendering on Studio is twice longer than on Premiere. I don’t even talk of the Sony AVC renderer, which takes about 6′, only uses 4 cores, and not the GPU at all even when the option is activated…
3) processing on Vegas Pro 9 (64 bits) => 3’17 (+ 1’10 of Cineform processing here as well) – which is also basically twice as long as Premiere Pro CS5.In addition, several things go in favor of Premiere Pro:
1) when there are effects (such as alpha processing, blurring, color correction), they are processed by the GPU (raising at 20-30%), which means no extra rendering cost.2) the preview is also partly managed by the GPU. When there are effects, they are processed in real time by the GPU (I can see the GPU load increase, and decrease after the effect), which makes preview fluid.
So I am bit disappointed by our Vegas favorite software, I hope that there will be soon a Studio 10 HD upgrade to really manage Cuda as it promises to do. I also hope the upcoming Pro 10 version will demonstrate efficient Cuda processing as well. For me rendering times and preview fluidity are way more important than 3D.
Comments welcome, questions about my test too.Frédéric
—
Want to learn on Sony Vegas Event Pan/Crop tool? Watch my video tutorial:
https://library.creativecow.net/baumann_frederic/Sony-Vegas_event-pan-crop-tool/1Or about Keyframes? https://library.creativecow.net/articles/baumann_frederic/Animating-with-Keyframes-in-Sony-Vegas.php
French version: https://geo.creativecow.net/fr/a/12999
-
2 Replies
-
Frederic, thanks for doing this research. I was wondering about those things, and it is interesting.
I get ALf’s and others’ comments that real-time preview would really be welcome, but since most of us walk away when rendering, aren’t ease of use and reliability the real primary factors in the selection of an NLE platform?
I’m just pondering out loud….
Norman Willis
http://www.nazareneisrael.org -
Hi Norman,
I see what you mean, however in my case, I am doing very few video effects except simple transitions, color adjustments, or panning/zooming, which make the preview usually real time.
However, I have just made another test, with 4 video tracks on top of each other, with transparency, slow-motion, and color correction for one of them. VMSP plays the sequence at 3 fps, while VP10 does it at 25fps (the original speed), except at one point (during about 1 second) where it falls to 22fps. Impressive, but this is of no use in my specific case.
In my case, I am concerned by rendering times because:
– I like to do 5-10′ videos of my family.
– Rendering is then about 15min-1 hour (to render to MP4, and depending on complexity)
– Then I have to manually run another tool to convert to DivX or Xvid
– And then I have to manually transfer the movie through FTP to my TV box so that my family can watch it.So this kind of short movies does not let me much time to switch to something else, and I have to be next to my PC to run the divx encoding as soon as rendering is finished, then the FTP transfer as soon as divx conversion is done. But the CPU being used intensively, I cannot do many other stuff (well, browsing the web is ok). This is the reason why I would like the rendering to be as fast as possible.
Hope you understand my point. And maybe I am doing it the wrong way. Maybe there are ways to automate the whole process from Vegas (conversion to divx, transfer to FTP). I am ready to learn more!!
Frédéric 🙂
—
Want to learn on Sony Vegas Event Pan/Crop tool? Watch my video tutorial:
https://library.creativecow.net/baumann_frederic/Sony-Vegas_event-pan-crop-tool/1Or about Keyframes? https://library.creativecow.net/articles/baumann_frederic/Animating-with-Keyframes-in-Sony-Vegas.php
French version: https://geo.creativecow.net/fr/a/12999
Reply to this Discussion! Login or Sign Up