Norman Black
Forum Replies Created
-
Only bypass blur completely.
I am not sure what bypass gaussian or pyramid could possibly mean. Which of the other 4 options would be used in that circumstance?
-
The Mainconcept CUDA encoder is a completely different encoder than the CPU only encoder. It is not the same encoder with GPU acceleration. Contrast this with Sony AVC, which is mostly the same encoder with some functions done on GPU.
Different encoders are doing things slightly different and unless the two encoders target the same bitrate, EXACTLY, then the file sizes will be different. Even at EXACTLY equal bitrates there can be quality differences. Maybe not visible but PSNR and SSIM will not be the same.
Also Mainconcept is very poor at targeting an average bitrate. No very accurate. One or even two pass. This statement I am comparing to x264 which can really nail a specific bitrate.
-
Playback performance is mostly tied to the CPU, unless you have a bunch of effects that slow things down. In other words, if the media plays fine by itself but cannot play fully with effects and then GPU acceleration can help, otherwise unlikely.
Sadly your CPU is kinda slow at only just over 2Ghz. 3Ghz and up would probably have you a happy camper.
Intel Quicksync would probably be the fastest AVC encoder but sadly your CPU is too old.
-
[Dave Haynie] “It’s interesting that the Sony AVC seems to be less computationally complex vs. Main Concept, but the latter gets more help from the GPU.
Both CODECs use the GPU better than I had seen in Vegas 11, but the Main Concept CODEC is out of control here, really shows that most of the render is happening in OpenCL, not on the CPU. Of course Vegas itself is responsible for some of this, but both CODECs get that same boost.”
Sony AVC only uses GPU for some things like motion search. Otherwise still the same encoder as CPU only. Quality should be pretty similar between CPU and GPU.
Mainconcept OpenCL (or CUDA) are completely different encoders than CPU only. They are mostly written to run on the GPU. Quality is lower than CPU only. Depends on bitrate and at higher bitrates I cannot see any difference.
The Mainconcept AVC OpenCL does not support AMD graphics core next GPUs. This means 7xxx series and later. Includes the current R8/R9. I found this out the hard way. My old 5850 flew on MC OpenCL and my new 7950 gets no use at all. Vegas itself and Sony AVC are fine with current AMD cards.
-
[Stephen Crye] “When you said “…The Vegas video composite and effects engine always uses OpenCL for both AMD and NVidia.” , do you mean during preview or render?”
The composite and effects engine is always used. Playback and render. Vegas creates a single video stream from your various sources with your edits. By definition, this is done during playback and during encode. During playback the video stream is sent to your preview window/device. During encode (render as), it is sent to the file encoder.
-
I have the free GoPro Studio software installed. That does get me decode ability for Cineform.
When I have tried to render to Cineform in Vegas I get an error saying the codec is not installed. I think the free software version only provides decode to third party applications.
I have not bothered with the Cineform workflow. I just put the GoPro MP4 files in Vegas directly. For Protune files, I created my own filter package to handle the adjustments (to my taste). I used color curves (contrast), levels (red tweak), color corrector (saturation) and convolution kernel (for sharpening).
Of course I found a playback performance problem in Vegas 12 with GoPro MP4 files. It would only likely show up with 1080p60 files, unless you have a pretty slow PC. I posted this in the Sony forum and others duplicated my results. I also recently reported this to Sony support.
-
[Graham Bernard] “One of several differences is that OpenCL isn’t available to choose in the SONY template.”
Sony AVC does use OpenCL on AMD cards. It uses CUDA on Nvidia cards. Its option is GPU if available which is the smart way to list the option.
It is confusing of MV AVC to list OpenCL and CUDA separate since for MC AVC OpenCL only supports certain AMD cards and CUDA only supports Nvidia cards.
-
[Stephen Crye] “* SVP12 render CPU only – 7:35 (horrible!)
* SVP12 render with OpenCL selected in the render – 8:40 (more horrible!)
* SVP12 render with CUCA selected in the render 3:22 (pretty bad, but at least the GPU was being used more)”I have some questions about this. The Mainconcept AVC OpenCL encoder does not support Nvidia. It only supports AMD. You use CUDA for Nvidia. This is documented.
The question is that your CPU only and OpenCL encodes should both be same time, and they are not, since CPU would be used when you selected OpenCL. This is assuming you changed nothing else other than the render as selection. e.g. Same GPU option in your video prefs. So the thing here is consistency of results.
The Vegas video composite and effects engine always uses OpenCL for both AMD and NVidia. This is independent of Mainconcept AVC OpenCL/CUDA options. The benchmark project uses lots of effects that are GPU accelerated.
-
Nice catch Steve!
I gotta try an old version with another AVC decoder issue I found. Bad performance with GoPro 1080p60 files. John Rofrano tried my example and it worked fine on VP11, and bad perf on VP12 but I don’t know what build he was using.
I just have to find where I can download these things.
https://download.sonymediasoftware.com/current/Has everything but VegasPro 12. It has all the MovieStudio12 stuff.
Can you Dropbox the 563 Steve?
-
I did drag into an empty project. I have Vegas set to ask to match media properties and I did so.
1440×1080
upper field first
1.33 aspect ratio
frame rate 25 (PAL)