This is a little like a post I made seven years ago:
Results of render times for ALL Vegas fX
You can download the VEG file for this project, substitute your own 6 second (or longer) single video file, and adjust your project properties to match your own video.
Project VEG file
I did this mostly to be able to see if all the fX were working (there have been reports of problems with one or two of the fX plugins). However, when I rendered each one, using the Cineform codec set to match the source footage, I was somewhat surprised to see that Vegas 11, even with my GPU turned on, was actually slower than Vegas 10. I tried a few of them in Vegas 11 with the GPU turned off, and the rendering time, in most cases was slower than Vegas 11 with the GPU turned on, so the GPU (mine is an "old" nVidia GeForce 9800 GT with 10/15/2011 drivers) does provide some improvement, but in many cases not enough to make it as fast as Vegas 11.
I found this surprising.
Also, as in my ancient post, you will see that a few of these effects continue to be real dogs, with both the min/max and median taking 35 minutes for five seconds of video.
I don't propose that anyone try to compare times or that this be used as any kind of benchmark because YMMV (a LOT!!) depending on about a hundred different variables, including the fact that some of these effects may take more or less time to render depending on what settings you use. I just chose what I thought were "medium" settings for each effect, spending about 1/2 of a split second to make each decision on what preset to use.
Here are the results (times in seconds). I created these times by creating a script that assigned regions with names that were automatically copied from the effect name. I then used a batch render script to render each event as a separate file. Finally, I used a utility that copied the date/times of each of these files to a spreadsheet and then calculated the difference in date/time between each successive file. This saved me from having to render each effect manually and write down each time from the end of render alert.
Given how I created these times (as described above), I don't consider time differences of one or two seconds to be significant.
Results of render times for ALL Vegas fX
You can download the VEG file for this project, substitute your own 6 second (or longer) single video file, and adjust your project properties to match your own video.
Project VEG file
I did this mostly to be able to see if all the fX were working (there have been reports of problems with one or two of the fX plugins). However, when I rendered each one, using the Cineform codec set to match the source footage, I was somewhat surprised to see that Vegas 11, even with my GPU turned on, was actually slower than Vegas 10. I tried a few of them in Vegas 11 with the GPU turned off, and the rendering time, in most cases was slower than Vegas 11 with the GPU turned on, so the GPU (mine is an "old" nVidia GeForce 9800 GT with 10/15/2011 drivers) does provide some improvement, but in many cases not enough to make it as fast as Vegas 11.
I found this surprising.
Also, as in my ancient post, you will see that a few of these effects continue to be real dogs, with both the min/max and median taking 35 minutes for five seconds of video.
I don't propose that anyone try to compare times or that this be used as any kind of benchmark because YMMV (a LOT!!) depending on about a hundred different variables, including the fact that some of these effects may take more or less time to render depending on what settings you use. I just chose what I thought were "medium" settings for each effect, spending about 1/2 of a split second to make each decision on what preset to use.
Here are the results (times in seconds). I created these times by creating a script that assigned regions with names that were automatically copied from the effect name. I then used a batch render script to render each event as a separate file. Finally, I used a utility that copied the date/times of each of these files to a spreadsheet and then calculated the difference in date/time between each successive file. This saved me from having to render each effect manually and write down each time from the end of render alert.
Given how I created these times (as described above), I don't consider time differences of one or two seconds to be significant.
Effect Vegas 10 Vegas 11
Add Noise 0:00:18 0:00:19
Black and White 0:00:10 0:00:11
Black Restore 0:00:10 0:00:11
Border 0:00:11 0:00:11
Brightness and Contrast 0:00:11 0:00:11
Broadcast Colors 0:00:11 0:00:11
Bump Map 0:00:18 0:00:10
Channel Blend 0:00:10 0:00:11
Chroma Blur 0:00:21 0:00:18
Chroma Keyer 0:00:13 0:00:11
Color Balance 0:00:10 0:00:11
Color Corrector 0:00:12 0:00:11
Color Corrector (Secdry) 0:00:12 0:00:11
Color Curves 0:00:10 0:00:10
Convolution Kernel 0:00:24 0:00:25
Cookie Cutter 0:00:09 0:00:08
Defocus 0:01:04 0:01:17
Deform 0:00:44 0:01:07
Fill Light 0:00:13 0:00:11
Film Effects 0:00:25 0:00:30
Film Grain 0:00:11 0:00:14
Gaussian Blur 0:00:25 0:00:13
Glint 0:00:45 0:01:05
Glow 0:00:26 0:00:14
Gradient Map 0:00:11 0:00:12
HSL Adjust 0:00:14 0:00:12
Invert 0:00:10 0:00:11
Lens Flare 0:00:16 0:00:11
Levels 0:00:11 0:00:11
Light Rays 0:00:17 0:00:37
Linear Blur 0:00:24 0:00:13
Mask Generator 0:00:59 0:00:26
Median 0:35:12 0:38:47
Min and Max 0:34:23 0:38:24
Mirror 0:00:10 0:00:11
News Print 0:00:18 0:00:19
Pinch-Punch 0:00:13 0:00:14
Pixelate 0:00:11 0:00:11
Quick Blur 0:00:10 0:00:10
Radial Blur 0:00:10 0:00:22
Rays 0:00:25 0:00:41
Saturation Adjust 0:00:13 0:00:11
Sepia 0:00:09 0:00:10
Sharpen 0:00:14 0:00:13
Soft Contrast 0:00:14 0:00:15
Spherize 0:00:12 0:00:10
Starburst 0:08:04 0:09:02
Stereoscopic 3D Adjust 0:00:10 0:00:10
Swirl 0:00:15 0:00:18
Threshold 0:00:12 0:00:13
Timecode 0:00:10 0:00:11
TV Simulator 0:00:17 0:00:17
Unsharp Mask 0:00:28 0:00:13
Wave 0:00:14 0:00:16
White Balance 0:00:10 0:00:17