Has Magix resolved the NVENC / NVCUVENC-CUDA issue yet?

mojoaudioguru wrote on 09/04/2016, 21:04

When is Magix going to incorporate the NVENC encoding capabilitiy? Or, are they going to do something about the fact that CUDA is no longer supported by NVidia GPUs? My rendering times have skyrocketed for BDR and AVCHD videos. (I am a professional videographer / cinematographer / film maker, that has relied on Magix software for years)  I don't want to leave Magix MEP for another software, but Magix is the only software that doesn't incorporate either the NVENC or NVCUVENC features. I've used Magix exclusively, since 1999. Does anyone know anything about these issues? And if there is a work around, please let me know.  Thanks. 

Comments

GrindheadJim wrote on 01/06/2016, 05:03

I have the exact same concern.  I have 2 980ti's running in SLI, and Magix can't use them, apparently.  What gives?

terrypin wrote on 01/06/2016, 09:44

That's disappointing to learn and a timely revelation for me. I'm about to order my high end PC, including an nVidia GPU. (My current preference is a GTX 960, as I've had over seven years of good service from my GeoForce 8800GT on my current XP).

While hopefully waiting to hear from the user experts (and ideally from Magix too) about this I've been googling to learn a few basics. I understand from this article:
http://create.pro/blog/open-cl-vs-cuda-amd-vs-nvidia-better-application-support-gpgpugpu-acceleration-real-world-face/
that AMD cards offer a roughly alternative facility called OpenCL.

So, could I please tack on the supplementary question: does MEP 2016 suport OpenCL?

johnebaker wrote on 01/06/2016, 10:08

Hi Terry

. . . . does MEP 2016 suport OpenCL? . . . .

MEP 2016 supports:-

OpenCL - it is specific to AMD cards

CUDA - NVidia, until they dropped it from the drivers

Quick Sync - Intel

John EB

terrypin wrote on 01/06/2016, 11:25

MEP 2016 supports:-

OpenCL - it is specific to AMD cards

CUDA - NVidia, until they dropped it from the drivers

Thanks John. Could you (or anyone) amplify a little on that please, in the context of my choosing a suitable GPU?

johnebaker wrote on 01/06/2016, 12:02

Hi Terry

There have been a several threads in the forum regarding the dropping of CUDA support from their drivers, here are a couple.

http://www.magix.info/uk/graphic-card-issues-magix-mep-2015.forum.1137997.html

http://www.magix.info/uk/is-there-a-work-around-in-order-to-get.forum.1150832.html  - top post

John EB

Scenestealer wrote on 04/06/2016, 23:59

Hi

Can anyone confirm that Hardware Accelerated export encoding is still available using Open CL on a recent AMD card and version of MEP or VPX using the Mainconcept encoder.

If so, which model GPU and which Magix version?

Thank you.

Peter.

Last changed by Scenestealer on 04/06/2016, 23:59, changed a total of 1 times.

System Specs: Intel 6th Gen i7 6700K 4Ghz O.C.4.6GHz, Asus Z170 Pro Gaming MoBo, 16GB DDR4 2133Mhz RAM, Samsung 850 EVO 512GB SSD system disc WD Black 4TB HDD Video Storage, Nvidia GTX1060 OC 6GB, Win10 Pro, MEP2016, 2017, 2014 Premium and prior, VPX7, 8. Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro, MEP2015 Premium.

savage10 wrote on 19/06/2016, 16:24

NEW, it seems in Windows 10 you only need the nvcuda.dll  extracted from driver http://www.nvidia.com/object/win7-winvista-64bit-260.99-whql-driver.html

For the mainconcept mpeg-4 codec to work, in windows 7 64 bit i put all 3 of them but it to may work fine with just the nvcuda.dll file, don't forget to use 7zip to extract the nvcuda.dl_  to get the nvcuda.dll file.

 

I got the cuda working in movie edit pro 2016 premium mainconcept mpeg-4

You need to download the driver http://www.nvidia.com/object/win7-winvista-64bit-260.99-whql-driver.html

Extract it do not install, then use 7zip to extract 3 files 2 nvcuvenc.dl_ one is a 64 bit the other is a 32 bit after you use 7zip to extract them they will have the full dll extention nvcuvenc.dll. Put the 64 bit one in the windows\system32 folder and the 32 bit in the windows\syswow64 folder.

Now you also need to use 7zip on the nvcuda.dl_ to extract it with the full .dll > nvcuda.dll, you CANT just rename the dl_ you need to extract all 3 on the file not remame.

THEN put the nvcuda.dll in the windows\system32 folder. Start your movie edit pro and you will now have cuda hardware encoding and no mpeg-4 error on the mainconcept mpeg-4 codec

mainconcept mpeg-4 will only work with the 260.99 cuda versions, it does not matter that the 260.00 is not for your video card as you are not installing it, just the 3 file for cuda that are in them. My card is a gtx 650 ti but it will work with any geforce that has cude.

mojoaudioguru wrote on 21/06/2016, 07:30

Savage 10, I did exactly as you described, and I still get no CUDA encoding with my GTX 750Ti. I am running in Windows 7 Ultimate, with a Q9550 Core 2 Quad CPU, (Overclocked at 3.5 GHz), 10 gig of DDR3 RAM, on a 500 gig SSD drive. Nothing has changed in my AVCHD or Blu-ray rendering times, despite doing exactly what you described. Is there something else I need to try?

savage10 wrote on 21/06/2016, 16:35

Savage 10, I did exactly as you described, and I still get no CUDA encoding with my GTX 750Ti. I am running in Windows 7 Ultimate, with a Q9550 Core 2 Quad CPU, (Overclocked at 3.5 GHz), 10 gig of DDR3 RAM, on a 500 gig SSD drive. Nothing has changed in my AVCHD or Blu-ray rendering times, despite doing exactly what you described. Is there something else I need to try?

mojoaudioguru, Is your windows 7 64 bit if not you need the 32 bit files.

Also make sure you put the 64 bit in the windows\system32 its the larger of the 2 nvcuvenc.dll files and the smaller in the syswow64, sound odd but the syswow64 is the 32 bit folder not the 64 bit one.

Also because the GTX 750Ti did not come with any nvcuvenc.dll files files or nvcuda.dll you will need to register them, go to command promp and run cmd as administrator you will see c:\windows\system32 then type regsvr32 nvcuvenc.dll, should look like c:\windows\system32 regsvr32 nvcuvenc.dll space after c:\windows\system32 and regsvr32 nvcuvenc.dll. The change to the syswow64 and do the same thing also do this for the nvcuda.dll.

I am using movie edit pro 2016 premium and paid the 5.77 for the mainconcept mpeg-4 codec after doing the cuda fix and pick encode with mpeg4 I go to a screen to encode it but their also is an advanced button under that and you can pic the hardware encoder it would have auto cuda, and 2 software to pick BUT after doing the nvcuda.dll fix I NO longer get the cuda pick, BUT it is using it and I guess because it does not show means its working. I DID test it, i took the same small video and not changing the advanced option and then changed it to the software and it was half the speed the cuda was si the fix doed cut the encoding in just about half the time.

Hope this works for you as it did for me, the 750 ti gpu is maxwell and my 650 ti is kepler but from searching it should still work on yout 750 ti, let me know if it does.

 

 

pmikep wrote on 09/07/2016, 04:39

I've been posting about lack of NEVC export (with late version Nvidia cards) and MEP in the Q&A area. Not sure which is the best area to post.

Anyway, since this thread was already started, I retried savage10's trick. (I did this trick last year too.) But it doesn't get MEP working for me. That's with a GTX960, Maxwell gen 2 chipset. I know that CUDA is working because 1) Blender works fast with the GPU selected and 2) Freemake acknowledges that I have CUDA for decoding. I'm pretty much resolved that CUDA and MEP are no more. (When it worked with my old card and my old version of MEP, the quality wasn't very good anyway.)

BUT - if you have a newer Nvidia graphics card, you CAN encode using NEVC in a round about way by using a free program called StaxRip. (You need to have .netframework 4.6.1 installed on your Windows machine first.)

To encode in H.265 using NEVC, you would first export your Magix video to the usual .MP4. I suggest using loose export settings so that the encode goes fast. It will give you a large file, but that's okay for now. It's only a "temporary" file.

After MEP is done with the MP4 encode, then run your large MP4 file thru StaxRip. You can encode to H.265 or H.264 using the hardware on you Nvidia card. It's amazing how fast it is!

In a way, it's kind of a manual "2 pass" encode. But if you have a long video to encode, it might actually be faster to do it this way. It will certainly give you a smaller file in the end if you need to upload your video somewhere.

mojoaudioguru wrote on 27/12/2016, 09:08

pmikep: That StaxRip idea is great. But it does nothing for me in rendering onto Blu-rays, in hi-def. Which is what I need and use the software for. Not for posting or uploading clips. I'm a videographer who relies on rendering edited video onto BDRs and DVDs. But thank you for the suggestion.