Fiola asked on 09/23/2016, 06:12 PM

Hi. My only reason switching from Vegas 13 Pro to Vegas 14 Pro would be functional CUDA rendering option. But it seems like my GTX 1070 is not supported. I don't see it in options at all.

This is a breand new GPU - what seems to be not supported up to now in VP14.

Still though, are there any way how to render any codec over CUDA?

In Vegas 13 Pro I have option to select Encode mode - for instance Sony AVC/MVC codec.

In Vegas 14 Pro - there is no Encode mode option.

Go to the internal preferences, and search for GPU. Here you can enable the render cuda support.

Fiola asked on 09/23/2016, 06:12 PM

Hi. My only reason switching from Vegas 13 Pro to Vegas 14 Pro would be functional CUDA rendering option. But it seems like my GTX 1070 is not supported. I don't see it in options at all.

This is a breand new GPU - what seems to be not supported up to now in VP14.

Still though, are there any way how to render any codec over CUDA?

In Vegas 13 Pro I have option to select Encode mode - for instance Sony AVC/MVC codec.

In Vegas 14 Pro - there is no Encode mode option.

Go to the internal preferences, and search for GPU. Here you can enable the render cuda support.

 

Actually. Yeah. But it's not working :D. Why do you think, I am writing here? Please, check whole topic first.

I have the same concerns as you Fiola. I made a youtube video on the render speed comparisons between vegas pro 13 and Vegas pro 14. Is there something that we are missing? Is GPU rendering not supposed to be working on vegas pro 14? The video on youtube is titled ( Magix Vegas pro 14 GPU Render Speed October 2016) (My channel is "Quba Grumpy"  

I have the same concerns as you Fiola. I made a youtube video on the render speed comparisons between vegas pro 13 and Vegas pro 14. Is there something that we are missing? Is GPU rendering not supposed to be working on vegas pro 14? The video on youtube is titled ( Magix Vegas pro 14 GPU Render Speed October 2016) (My channel is "Quba Grumpy"  

Yes. They put GPU render on the bottom in their to-do list. We actually DONT know if they are more people waiting for this feature. Probably it's something, what most people don't think it is important :).

As a 1070 owner the support is crucial and it was one of the things that let me hesitate jumping on V14. Even if the card is quite new, the support of GPU usage of this card is nothing that needs to be invented from scratch. It is usable in Adobe Lightroom or Davinci Resolve without any problem and it did not require a new release of this software.

GPU support is one of the most important things today, how can they miss it?

Enabling CUDA will not help a lot for nvidia cards starting from 6** series, cause newer cards from Kepler core mainly using NVENC for encoding, and MainConcept/SonyAVC still don't. We could before render using debugmode frameserver -> avisynth -> staxrip/Hybrid (containing cool rigaya nvenc encoder)/MediaCoder (own nvenc encoder), but it not easy to setup all this and you loosing some speed on convertations and all this software now quickly switching to avisynth 64 bit, and debugmode frameserver has not FOURCC codec for it: https://github.com/satishsampath/frame-server/issues/28 and author just put all stuff on github hoping somebody will maintain it.

Meanwhile, in better world (adobe premiere/AE) there is Advanced Frame Server - fork from debug mode frameserver: https://sourceforge.net/projects/advancedfs/ which you can use in chain with StaxRip/Hybrid/whatever (contain inside rigaya's best nvenc encoder) and also Nvenc_export plugin https://forums.adobe.com/thread/1243687 which has some troubles at use, but you have more options than with Vegas "Pro"... I have not look furher, but will not be surprised if I found out in CC2015 in AME (adobe media encoder) just easy selection for NVENC encoding. 

Long story short - I think it's time to switch back to Adobe Premiere/AE

Maybe there is CUDA and there is CUDA :)

I have a GTX750 Kalm 2GB which supports CUDA but it just crashes Pro 13 during rendering. I have to disable GPU everywhere I can.

...We could before render using debugmode frameserver -> avisynth -> staxrip/Hybrid (containing cool rigaya nvenc encoder)/MediaCoder (own nvenc encoder), but it not easy to setup all this and you loosing some speed on convertations and all this software now quickly switching to avisynth 64 bit, and debugmode frameserver has not FOURCC codec for it: https://github.com/satishsampath/frame-server/issues/28 and author just put all stuff on github hoping somebody will maintain it.

Meanwhile, in better world (adobe premiere/AE) there is Advanced Frame Server - fork from debug mode frameserver: https://sourceforge.net/projects/advancedfs/ which you can use in chain with StaxRip/Hybrid/whatever (contain inside rigaya's best nvenc encoder)...

Debugmode Frameserver 2.15 works in Vegas Pro 14. I know it will frameserve to MeGUI, TMPGEnc, AviSynth etc. and I have heard that it will frameserve to StaxRip so I expect it will also frameserve to Hybrid and MediaCoder. Admittedly in Vegas Pro 11, 12, 13, and 14 it will only serve 44.1kHz audio, but apart from that, Adobe does not have an advantage here, unless I've missed something.

I have not look furher, but will not be surprised if I found out in CC2015 in AME (adobe media encoder) just easy selection for NVENC encoding.

Looks like still only 3rd party plugins.

Long story short - I think it's time to switch back to Adobe Premiere/AE

If rendering speed to those formats is all you care about then you may be right, but then you'd be locked into a subscription contract and you'd be missing out on Vegas' advantages in terms of workflow, audio, scripting etc..

For Staxrip it only worked in old version when Staxrip was x86. Nowadays Staxrip is only x64 and Frameserver dont work with it, at least for me. For those with Skylake CPU's Handbrake should be fine using Quicksync. My Haswell Quicksync is not much faster than my 4 cores at x264 Veryfast and H.264 quality from all ASIC's(VCE,NVENC, Quicksync) is very close to x264 Veryfast quality.

H.264 ASIC's from Broadwell, Skylake, Maxwell, Pascal, GCN 1.2/Polaris is much faster than old ones but quality not changed. Mainconcept AVC CPU encoding use some quality close to x264 slow/medium. Of course quality will only be a concern for those with complex videos(high motion/high detail), for those with mostly static footage the quality difference would decrease or even disappear.

I confirm that frameserve to Staxrip doesn't work except  in the old x86 version. 

Hybrid has problem as well because it considers the frameserve avi file always progressive and with Rec. 601 color matrix to convert to YV12 for ex.   whatever the input.

The best way would be a built in frameserve into Vegas. 

Fast rendering is great but mostly affect the quality. I personally prefer render lossless files from Vegas then feed them in a X264/X265 GUI. 

I feel like they are reselling outdated compatibility, we waited so long only to get what we already had for the past 3 years. Encoding 4K with a CPU is a no no. I know alot of folks here are tying to defend the software an such, but it makes no sense to give us native 4k support, but not update the CUDA driver compatibility to render/encode them even 1080p/60fps is terrible slow with CPU. Lowering the settings for faster rendering time would destroy the whole purpose of better quality. Vegas does has it advantages, but as a youtuber it doesn't benefit me at all unless I buy another GPU that happends to be AMD b/c the devs think Nvida users aren't important

Mainconcept encoding CPU only = x264 Slow preset quality. Mainconcept CUDA encoding = x264 superfast quality. I dont see the point to move to CUDA for faster encoding and lowest quality while saying than dont want faster CPU encoding which decrease quality. CPU encoding at level of x264 Veryfast will be better quality than CUDA and faster encoding than using Mainconcept CPU encoding.

The benefits new AMD cards got are same as new NVIDIA cards with GPU acceleration only for features like Video FX, Transition, compositing and this is added to Vegas engine and not to encoding template.

Instead of CUDA there be nice if they can replace encoding with ASIC encoders. NVENC and Quicksync3+ has x264 veryfast quality level, it's better than CUDA superfast quality level. Maxwell, Pascal, Broadwell and Skylake has fast ASIC encoders too so speed should be not a problem.

Kepler NVENC 1.0 is capable only to 1080p@60fps for quality encoding while Pascal NVENC 4.0 can do 1080p@350fps. Quicksync 4.0 and 5.0 should be similar to NVENC4 performance and quality.

Just to compare my i7 4770k 4 cores can encode x264 veryfast at around 1080p@100fps, so newest NVENC/Quicksync encoding are 3x faster to produce similar x264 veryfast quality for those which want CUDA so much.

Has anyone done a comparison on recent AMD CPU ?  (Is there already a thread I havnt found on that maybe ?)  Im in the market for a new GPU but am undecided between AMD and Nvidia.  My priority for it would be using it for Vegas 14.

Its a shame that modern GPU acceleration doesnt seem to make much difference with rendering the final movie.  At least creating proxy files works well giving you extra flexibility with a speedy workflow allowing you to change preview quality.

Hopefully in the future Vegas will get proper GPU support on both AMD and Nvidia that makes a good difference :-)

Has anyone done a comparison on recent AMD CPU ?  (Is there already a thread I havnt found on that maybe ?)  Im in the market for a new GPU but am undecided between AMD and Nvidia.  My priority for it would be using it for Vegas 14.

You're probably better off with AMD if Vegas is your priority because of the better OpenCL support. Howardv posted some useful test results of the RX480 here: https://www.vegascreativesoftware.info/us/forum/benchmark-tests-for-new-video-card--101793/?page=1#ca644645

RX470 user here. Previously using Radeon HD5750.

So far so good... for rendering, I leave Mainconcept for rendering to Internet MP4 presets as it is no longer supported, and have been using Sony AVC/MVC.

Developers realize about the GPU support, and they are trying to make this back to work. (Reference)

Thanks for the link and info. An AMD gpu will be on the cards unless Magix improve the nvidia support.  And look forward to the developers improving the GPU support.

AMD GPUs tend to be more powerful when it comes to GPGPU functionality anyway, though I moved on to Nvidia anyway due to AMD's terrible drivers. I also do video projection mapping, and having my system crash and burn in the middle of a gig (so bad I almost had to re-install windows to get going again, I couldn't even get it to boot), leaving 3 projectors blank and the client infuriated, was enough for me to make the switch. That wasn't the only incident either. Nvidia has been rock solid on the software front.

AMD Drivers have improved a Hell of a Lot. I think my next GPU might be a AMD Vega one. Currently using a GTX 1050 and no improvment in render times on SVP 14. Might have to move to premiere.

I managed to get CUDA to work from the internal Preferences and CUDA is active but no decrease in render time.

I managed to get CUDA to work from the internal Preferences and CUDA is active but no decrease in render time.

If you will read this post, you will discover, that we already tried that! :D But it's good to be sure, you know ;) ...

GPU accelerated rendering is not currently available both: Vegas 13 and Vegas 14 for many GPU's out now.

Hi. My only reason switching from Vegas 13 Pro to Vegas 14 Pro would be functional CUDA rendering option.

The obvious question is which CUDA? CUDA is a proprietary way to access certain NVIDIA GPUs. NVIDIA was pushing it, when it was new and had no competition. They were pushing it because if programmers fell for it, millions of people would opt for an NVIDIA card over any competition.

It actually worked at first. But then NVIDIA came up with new models of their GPUs, and they ceated a new CUDA just for them. They were hoping programmers would fell for it again, and everyone would be forced to get new GPU cards.

This time it did not work as well as before. You see, programmers tend to be intelligent. They don’t want to spend their time on learning some complicated proprietary system with a steep learning curve, if their experience tells them that the creator of that system will most likely abandon it by the time they have finally learned all of its ropes.

And sure enough, NVIDIA came out with yet another group of GPUs that come with a totally new CUDA again.

I learned the first CUDA myself, but when NVIDIA came up with a completely new CUDA, I quickly decided it wasn’t worth my time.

Meanwhile the industry came up with OpenCL, which is just one new thing to learn, and it is up to each GPU manfaturer to create the code to interface between OpenCL and their GPU and include it in the driver for their GPU. If NVIDIA has failed to do so because like a little kid they have a fit that other companies dare to compete with them, well, to Hades with NVIDIA.

If you want Vegas to work with your NVIDIA GPU, don’t ask Vegas programmers to learn yet another proprietary system and make Vegas bloated with every new version thereof, ask NVIDIA to include a good OpenCL interface in their own drivers, and let them know that if they do not, you will never buy another one of their products and will encourage everyone else to do the same.