caveat emporium. with software especially so ;-(

How do you make 750ti and these Kepler cards to speed up with Mainconcept CUDA in VP12 when it's well known to only work for Fermi/VLIW? Are you 100% sure than Mainconcept CUDA was capable to use your Kepler and Maxwell card when even Mainconcept itselft stated than it only support up to GTX580 and no more?

Just asking because my GTX560 can work in both jobs with Vegas 13, in Vegas engine which speed compositin,efects etc. and in Mainconcept CUDA for final encoding only. My GTX770 and R9 390 in VP13 can only speed Vegas engine(OpenCL) and in Mainconcept both cards dont work for speed up final encoding since Mainconcept dont updated the template to support GCN and Kepler+. You can check in their own website for CUDA encoding about supported cards http://www.mainconcept.com/eu/products/sdks/gpu-acceleration-sdk/cuda-h264avc.html

Dont you confusing CUDA which is only inside Mainconcept with Vegas engine GPU acceleration(OpenCL) for other video editing features?
My GTX560 is accelerating Preview and all OpenCL related features when rendering without a problem since i keep internal GPU rendering=FALSE in VP14. Only downgrade is Mainconcept CUDA encoding is gone even on Fermi, my dear GTX560 cant push to the max anymore.

I dont/dident say V12 worked with my cards. "I was running version 12 for a long time (and have been a customer since V10) but was hoping for Sony to get the GPU acceleration running for CUDA based cards" like they claim in the system features it will.

I used to run FireGL cards, and was a AMD fanboy from the start. I only changed to NVIDIA because Sony's worked well with the older GTX5XX Cards. 

Vegas 14 still works fine with both my Quadro Q4200 but also my AMD R9 390X - and has a clear support from this cards in the preview if one uses effects. That is more important then the render support to my opinion.

I do not think that there will by any refund for such a point. But give it a try and report to us. ;)

Hi

There has been a lot of discussion over in the Movie Edit Pro forums regarding CUDA support.

In a nutshell NVidia have stopped providing CUDA support on the newer graphics cards drivers .

See this post and this post there are many more posts over there on this issue.

John EB

In a nutshell NVidia have stopped providing CUDA support on the newer graphics cards drivers .

John EB

That statement is so false it is criminal.

I dont/dident say V12 worked with my cards. "I was running version 12 for a long time (and have been a customer since V10) but was hoping for Sony to get the GPU acceleration running for CUDA based cards" like they claim in the system features it will.

I used to run FireGL cards, and was a AMD fanboy from the start. I only changed to NVIDIA because Sony's worked well with the older GTX5XX Cards. 

 

CUDA in Sony VEGAS was delivered by third party Mainconcept company, looks like Mainconcept give up on GPU encoding long time ago since GPU encoding produces lower quality encodings than software(CPU only).

There is nothing Sony/MAGIX can do to force Mainconcept to update their template. Forget about it, that something probably would not comeback. What rest now is the other GPU acceleration which are in Premiere too, Premiere never adopted such thing how GPU encoding acceleration, they only have GPU acceleration for common features compositing, effects etc..

Old Fermi and Kepler architetures has slow compute performance which is the power to perform good OpenCL, so they both are slower for Vegas, but Maxwell/Pascal increased a lot in that matter and nowadays both Maxwell/Pascal should stay at same level of GCN cards in most OpenCL applications.

Take a look how Maxwell improved over Kepler in compute: http://images.anandtech.com/graphs/graph9390/75492.png

Pascal should got some gains against Maxwell aswell.

Try this. Go to the Internal preferences tab and search for GPU. "Enable GPU" will probably be set to FALSE. Change it to TRUE and then restart Vegas. This may or may not fix the problem. For me, I could find out if OpenCL was available when I clicked the "Check" button on the System tab of Mainconcept AVC Internet 1080p preset. Before, there wasn't a Check button.

 

 

CUDA in Sony VEGAS was delivered by third party Mainconcept company, looks like Mainconcept give up on GPU encoding long time ago since GPU encoding produces lower quality encodings than software(CPU only).
 

 Is this expected to stay this way? I have a dual 6 core machine and I just use CPU rendering anyway but it would be nice to get a speedboost for the cost of a newer video card.

 Is this expected to stay this way? I have a dual 6 core machine and I just use CPU rendering anyway but it would be nice to get a speedboost for the cost of a newer video card.

That something to ask MAGIX or directly Mainconcept, since last time Mainconcept updated their GPU encoding template was around 2010.

But like i said GPU encoding produces lower quality, for some cases of complex scenes with low bitrate video quality can stay much lower than CPU only. This problem almost disappear when the bitrate amount is high enough for specific source complexity.

 Thanks, I have been thinking about upgrading the video card in my PC, I guess it would not be worth it at this point in time.

I usually am not making fuss of demanding refund based on false advertising, but in the case of MAGIX VP 14 I might make an exception! Utterly disappointed with both the performance of this version (on my new machine, SCS VP 13 was flying), but also with the lack of so many promised features... Thos most important to me which were announced but didn't come are:

- even a basic LUT support for my Slog FS7 footage (ACES is unusable)

- HEVC import 

- full and bug-free Decklink 4K Extreme 12G support 

So - if anyone from MAGIX is reading this - please come up and speak, before I file my refund claim. I can still give MAGIX some credit and wait, provided I'm promised and guaranteed those feaures will be arriving, and bugs ironed out, in frequent interim releases/builds of the same, 14 version of Vegas Pro. If on the other hand MAGIX oannounce them again as coming with the next major Release (15?), and want my money again - not only will I refuse, but will do everyting possible to get my VP 14 price back and forget about MAGIX (and sadly, Vegas) for good. And MAGIX being an EU-registered business, I'm covered with all the rights required for demading refunds as a Polish company.

Piotr

I think about this 3 points, and I wonder what is the issue behind:

- LUT support was never promissed in the features, I would have loved too but it was not on the list. Can be done with third parties plugins only (e.g. hitfilm or looks3)

-HEVC import - the rendering is here. I have not tested the import really, for the FS7 footage that is no issue? But what does not work here?

- Decklink support: preview works great here with my Decklink 4K. So what is the problem with yours?

Hi Wolgang!

OK, so you're right (apologies to MAGIX) - LUT weren't announced; I must have mixed up the announcements with wishes people were making while waiting for the 14. As to the other two points:

- if I am to preserve as much of my footage quality as possible in my out-renders, I need H.265. True - VP 14 can do them - but I was also counting on importing them; as of now I cannot export H.265 from Resolve after grading, but this will most probably come soon. Already present is the Mercall's SAL version H.265 export as the only one, preserving much of my XAVC footage, but those files canot be imported to VP 14 :(

- as to my Decklink: unlike in VP 13, the resolutions drop-down list does indeed contain FUHD and even DCI 4K - but the whole point of using Decklink (with 32bit float project color precision) is 10-bit color, and this only works with up to 1080. Also, 25fps doesn't work, either (even with 10-bit processing unticked) - does it with your Decklink 4K? Asking, as this might be BM's own driver issue - but it should have been tested by Magix, right?

Piotr

HEVC import works fine here for the H.265 available for me.

Hi Piotr,

during betatesting I have checked the functionality of my Decklink 4K Extreme (6G as you know) quite intensive, and for sure it was also tested by the development team too.

I had a look for you again, and can say following. I use a 10bit test ramp.psd that is available in the net.

- from an UHD 25p project (XAVC files UHD 50p but set to 25p to improve preview cabilities) I see an 8bit preview from my Decklink. Preview settings are UHD 2160 25p (the box "use 10bit encoding MUST not be enabled)

- from the same project but changed to from 8bit to 32-bit floating point (video levels) the preview by my Decklink 4K is shown as 10bit. And it is also shown as UHD 2160 25p (and my Dell UHD Monitor confirms that the incoming resolustion is 2160p.

- in the output settings from the Decklink I have also up to UHD 2160-50p/60p available, but also up 4K 22160 25p

- never ever enable the box "use 10-bit encoding"!

- I use the Blackmagic driver 10.6.5, what may not be the latest one.

For the HEVC issue:

- I have here some testfootage from the Samsung NX1. I never had this camera, but I collected some testfootage. This testfootage can be imported in the Vegas Pro14 timeline and the playback is fine. So the HEVC import works generally, and the files are shown in the properties as HEVC too.

We had it also in the past that some rendered footage even from Vegas cannot be re-imported in Vegas itself. But that is something what was never promissed (because they never come up with such details).

I also think that it is NOT a good idea to use HEVC to perserve the best quality possible. I am not sure yet if HEVC will be handled in Vegas as 8bit or 10bit yet, to my opinion that is a format that will be used as final delivery format for UHD TVs mainly (what requires in future 10bit, but that is not what I know yet).

For a roundtrip worklfow  with Resolve I would tend to use codecs like Cineform, uncompressed or maybe XAVC I. But also those requirements are nothing what is a Vegas Pro 14 issue really. That is something what is up to you to find here a solution that works for you.

Kr

Wolfgang

Wolfgang,

Which connection are you using with your Decklink - SDI or HDMI?

Piotr

HDMI

Well - so there must be a difference in how VP14 handles Decklink 6G vs. 12G...

Piotr

Cannot imagine that. What is your driver version?

It's the newest one (10.8), but I tried 10.7 with the same results. The UHD 25 fps sends blank screen no matter what (even though monitoring at 25 fps works fine with Resolve). But one thing I must admit - with the "10bit processing" checkbox NOT ticked, it's sending 10-bit signal properly (only at 50 fps setting, though).

Piotr

So you have your solution - then it was the "10bit processing" checkbox.

The 10bit signal will always be send if you use a 32bit floating point projekt. Regardless if it is HD, UHD, 24p, 25p or 50p.