First Impressions and troubles.

Comments

Tony-G1 wrote on 1/5/2017, 6:23 AM

Found this:To use CUDA with the MainConcept AVC encoder you can only use a GT/GTX200, GT/GTX400 and GT/GTX500 series of video cards. 

To use OpenCL with the MainConcept AVC encoder you can only use the AMD/ATI HD 4000, HD 5000 and HD 6000 series of video cards.

Otherwise, when using the MainConcept AVC encoder, it will run using the CPU only.  Which actually isn't a bad thing as the video quality is much better when you set the MainConcept AVC encoder to CPU.

If you want one of these older video cards, you can still find them on ebay.

For some reason, MainConcept hard coded the list of video cards into the MainConcept code.  Why they would hardcode the list of video cards into the MainConcept AVC encoder is beyond me.  Since they have done that, it effectively blocks all newer video cards such as the NVIDIA GT/GTX600, GT/GTX700, GT/GTX900 and AMD HD 7000, R7 and R9 series of video cards from having GPU acceleration when using the MainConcept AVC encoder.

Even if you select the MainConcept AVC encoder to use OpenCL or CUDA with a modern video card, it will fall back to using the CPU.  I do want to point out that trying to use the OpenCL or CUDA on a modern video, you may cause your system to crash or for you to experience other strange problems.  Again, this is due to MainConcept hard coding the list of video cards it will work with under CUDA and OpenCL.

johnebaker wrote on 1/5/2017, 7:07 AM

Hi

. . . . . Has anyone got this Graphics card.XFX HD-545X-ZCH2 Graphics Card (ATI Radeon HD 5450 1 GB PCI-E GDDR3 Memory DVI HDMI 1 GPU . . . .

I had one in my old computer, a quad core pre Intel ix series being released, transferred to my current PC and dumped it within a week - was not as fast as using the integrated chipset of the i5 4570K.

It worked OK with MEP 2013 on Windows 7 and 8, so I would expect it to work with MEP Premium however you will need to check you can get ATI/AMD Windows 10 drivers for it - there may be issues if you use the Microsoft drivers.

HTH

John EB

 

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

johnebaker wrote on 1/5/2017, 7:15 AM

Hi

Good to know the info re MainConcept and AMD cards compatability.

Thanks

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Scenestealer wrote on 1/5/2017, 6:14 PM

Hi Tony

Thanks for posting that list, but know surprises there as it is what I have posted and discussed many times over the years. I was looking for that information to copy from the Mainconcept site where they used to list it in relation to the SDK for H264 HW encoding, on Nvidia and AMD GPU's, but I see they have retired those kits since a few months ago and removed the info. It seems that there is a new Encoder Wrapper that is taking over the task to enable any usable hardware on you system for acceleration of encoding, whether it be the legacy cards you have listed, or optimisations in Intei I series CPU's even if they do not have integrated GPU's.

From MC:-

The AVC/H.264 Video Encoder Wrapper is a module which grants access to all MainConcept AVC/H.264 Video Encoders through a single, common API. Regardless of whether a customer application is using MainConcept Software Encoding, Intel Quick Sync hardware encoding on a 3rd Generation (or later) Intel® Core™ processor, or the legacy OpenCL or CUDA encoding modules the wrapper is able to reliably detect available encoders and configure them. Based on the configuration requirements automatic selection of encoders is being performed. The AVC/H.264 Video Encoder wrapper is available as add-on to any of MainConcept’s AVC/H.264 Video Encoders.

Interesting and I am sure Magix takes advantage of this which could explain why I am seeing almost as fast render times with the MC Codec without HWA as I do with the Intel with HWA enabled, on my 6th Gen i7 system.

Your statement "Why they would hardcode the list of video cards into the MainConcept AVC encoder is beyond me." It is beyond me too but they would know better than us.They built it to make use of the chip architecture available at the time and what is more important is why they decided not to keep developing it for later hardware. "the video quality is much better when you set the MainConcept AVC encoder to CPU." is part of it probably.

You need to be careful when reading sales blurb from the Editing SW manufacturers when they make Hardware accelerated claims as it is often either:-

1. with Legacy cards no longer available.

2. Acceleration of the timeline decoding and encoding during preview, and preview of effects (selectable in the program settings in MEP) .

3. Encoding of effects on the GPU during export (selectable in the Export dialog in MEP).

I can not see anything in the link you sent or on the Cyberlink site that would confirm any other NLE program would do anything other than those 3.

Peter

Last changed by Scenestealer on 1/5/2017, 6:16 PM, changed a total of 2 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 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

johnebaker wrote on 1/6/2017, 2:19 AM

Hi

. . . . Why they would hardcode the list of video cards into the MainConcept AVC encoder . . . .

I suspect this is because one graphics card maker was mixing chip types for the same model graphics card and there was some incompatibility between them.

. . . . legacy OpenCL . . . .

Interesting statement from MC - unless they mean it is 'over a few years old'.

Unlike CUDA, OpenCL is alive and kicking, the newest version was finalized April 2016 and supported by a multitude of modern graphics cards.

@ Peter

. . . .Magix takes advantage of this which could explain why I am seeing almost as fast render times with the MC Codec without HWA as I do with the Intel with HWA enabled, on my 6th Gen i7 system. . . .

I think that if you turn on HWA in MEP, the MC render times will be the same as without it, and MC is ignoring the program setting altogether.

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Scenestealer wrote on 1/6/2017, 4:03 AM

Hi John

Interesting statement from MC - unless they mean it is 'over a few years old'.

I think they are referring to "the Modules" that they used to enable HW Export with the up to:- GTX5xx series and Radeon HD6000 cards.

Unlike CUDA, OpenCL is alive and kicking

Well I think Cuda still is as well, for purposes other than what we are interested in, or can utilise in NLE's. The latest cards still contain CUDA cores.

I think that if you turn on HWA in MEP, the MC render times will be the same as without it, and MC is ignoring the program setting altogether.

Yes, that is what I suspect based on the MC info about the "automatic selection of encoders" with their new encoder wrapper.

Peter

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 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

Tony-G1 wrote on 1/6/2017, 8:04 AM

Hi Guys. What do you make of the info in this link? Admit I am a bit baffled by all this so not going to spend any more time on it and just accept that my graphics card is of no use in terms of HWA. https://www.studio1productions.com/Articles/SonyVideoCards.htm All the Sony software I gather now is Magix.

Tony-G1 wrote on 1/6/2017, 11:33 AM

Finally got a reply from Magix which confirms.

"Please note that hardware acceleration in MAGIX software is applicable only under Intel graphics. You should enable your Intel component in your computer's BIOS if it is not showing in Windows device manager. "

--
Thank you for contacting Magix Support.

yamane wrote on 1/6/2017, 12:26 PM

Finally got a reply from Magix which confirms.

"Please note that hardware acceleration in MAGIX software is applicable only under Intel graphics. You should enable your Intel component in your computer's BIOS if it is not showing in Windows device manager. "

But, it means you can keep using your discrete video card (e.g. NVidia GTX970), and with the monitor connected on the discretre video card?

Scenestealer wrote on 1/7/2017, 4:24 PM

Hi Tony

Thanks for the link. I think I have seen it before but no surprises there. One thing with articles like that is that they are often a year or two old, and cards and editing software processing engines are constantly being updated to take into account updated SDK's like the Mainconcept ones I mentioned before.

The fact that AMD cards handle Open CL acceleration better than Nvidia in Vegas may have no relevance in MEP as I am not really sure what MEP is leveraging for timeline preview rendering, it may be using Direct Compute which is Direct X accn. I am not able to access a modern AMD card to compare playback performance.

Yamane

I would enable both the integrated Intel GPU and the Nvidia discrete card as my experience has shown that during exports with Quicksync HWA enabled, both cards are doing work with "Calculate FX on GPU" ticked in the export template window. GPU-Z showed about 15% load on the Nvidia card and 65% on the Intel HD530 integrated Graphics and 1 minute of 1080 50P went through in 38 seconds. This could relate to what that article is saying about the timeline rendering of FX etc. being a process that must occur before the encoding on the GPU can take place, suggesting that in my case this was the 15% activity on my GTX1060. Other members have reported faster exports with both GPU's enabled also.

BTW - once setup- you can choose which GPU can be used for timeline preview, in MEP Program settings > Display options > Preview in the arranger, to see which works better for you. I have not seen much difference with either although I think the GTX1060 is slightly smoother at full res. Also make sure 'HW acceleration for playback' is enabled in the previous Tab.
 

Peter

 

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 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.

pmikep wrote on 1/13/2017, 9:24 AM

I have PD 15. (Bought it for $35 USD during Black Friday to try it out.) It does offer HW encoding using my GTX 960. At times, can be very, very fast.

I prefer MEP over PD for editing. But I encode into high BW in MEP and then run it thru PD to shrink it for upload.

Started with MEP 11, then 17, then MX, then MEP 2013, 2015, then 2016. Changed to the fast competitor after that, which worked fine with my non-Intel hardware. Then bought a used Dell with an Intel GPU, just to play with MEP again. Installed MEP 2020 Plus in March 2020, even tho I don't like losing patches if I have to reinstall after a year.

Testing on a Dell Vostro, <s>i3-8100</s> updated to i5-9400 w/ UHD 630, 16 GB 2400 DDR4 (CL15), Win10 Home, heavily NTLite'd. Now with GTX-1650 Super OC'd. Added a WD Blue M.2 for OS (PCIe 3), Apps, Temps and Video-In. 2 Monitors. A WD Blue SSD for outputs. (SATA III.)

Scenestealer wrote on 1/15/2017, 4:36 PM

Hi pmikep

It does offer HW encoding using my GTX 960. At times, can be very, very fast.

Does it say it is using Cuda specifically?

Ss

 

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 2004, MEP2016, 2022 (V21.0.1.92) Premium and prior, VPX7, VPX12 (V18.0.1.85). Microsoft Surface Pro3 i5 4300U 1.9GHz Max 2.6Ghz, HDGraphics 4400, 4GB Ram 128GB SSD + 64GB Strontium Micro SD card, Win 10Pro 2004, MEP2015 Premium.