No Hardware Encoding using LUT

johnebaker wrote on 2/26/2021, 7:33 AM

Hi

Not all effects are rendered on the 2080. If they cannot be rendered on an integrated GPU (Intel processor needed) then they will be software rendered.

What is you computer specification? See this this comment for details of what is required.

John EB
Forum Moderator

CubeAce wrote on 2/26/2021, 7:34 AM

@Zkuggi

Hi.

I notice this appears to be a similar problem to the last post you did not get a reply to.

So far you have not supplied any system specs into your signature as requested in the forums sticky posts which may be a reason for people not being tempted to reply.

Knowing a persons system specs and Windows version and build can help us ask the correct questions to try to et to a solution of a given problem or we are left with guessing at a cause.

Having said that I'm going to guess that you either have.

A Ryzen based system.

An Intel system with no Intel processor with an Intel GPU

A system that does have an Intel GPU but only running one monitor or is a laptop with same.

Either way, you may have noticed if you looked as the minimum system requirements before purchase that it listed the use of an Intel GPU with an HD 520 or higher capability.This is because MAGIX Video Pro X supports the use of "Quick Sync Video" hardware acceleration. This can noticeably speed up the encoding process for hardware acceleration as mentioned on page 390 of the pdf manual.

Now, if you do have an Intel CPU with inboard GPU with a usable graphics processor then it could be that it is not enabled in the bios.

It appears that it is the Intel GPU that is primarily responsible for the faster encoding with HEVC within VPX.

[Edit] Beaten again.😁👍

Ray.

Zkuggi wrote on 2/26/2021, 9:13 AM

Thank you @johnebaker and @CubeAce for quick response.

I totally forgot to mention my CPU. Running this setup on Intel i9-9900. Bought back in 2018.
@CubeAce this is partly similar to my earlier post that I had forgotten about. https://www.magix.info/us/forum/filmconvert-ofx-slow-render-speed-in-video-pro-x10--1223424/

There I was trying to use Filmconvert 3rd party plugin for color grading. In the end I got it confirmed from Magix support that Video Pro X could not utilize the GPU even though it worked with Vegas Pro. Something about how the signaling is between the host program and GPU.

But since Filmconvert does not work in Video Pro X I have been using the native LUT filter of the program. Thought it should use GPU for encoding to HEVC output.

This is my 10th larger than 1hour project that I've created in Video Pro X and I have always been able to export using GPU encoding. The problem is that I cannot remember if I have been using LUTs in those cases. I think so.

I am running latest drivers from NVidia.

johnebaker wrote on 2/26/2021, 9:46 AM

@Zkuggi

Hi

To make use of the Intel UHD 630 iGPU, it may need 'activating'.

Check that the iGPU is enabled in the computer BIOS, how and where you find this depends on the BIOS make.

If you are working with 2 monitors plug one of them into the onboard graphics output - adjust the windows settings as needed - I have my desktop extended across both monitors with my UHD 630 set as Primary display.

If you have only one monitor and it has a spare input connect this to the onboard graphics output - it only has to be detected - you may need to set windows to Duplicate across monitors to avoid issues. An alternative if the onboard graphics output has HDMI 2 compatibility is to use a headless ghost monitor emulator

With the above settings the UHD 630 iGPU and the 2060 will be used as required.

John EB

CubeAce wrote on 2/26/2021, 9:48 AM

@Zkuggi

If it's any consolation, once I start to add any plugins to a 4K (3840 x 2160) project the re-rendering of each frame needed during export with HEVC means a 4 times project length amount of time needed normally as a minimum. I'm running the i9900K. 1920 x 1080 projects are much closer to a 1 to 1 export time but even then the fps of a project can also make a difference if it only rendering half the amount of frames. The Magix video editors have seldom ever been in the top four for fastest render times but are possibly the most stable in use.

Most Video editors do make additional use of an Intel GPU including Adobe Premier, Edius, Pinnacle Studio and Filmora. Notable exceptions are DaVinci Resolve and Vegas.

You can see how the workload is split within VPX on export using HEVC.

As far as I can work out the Intel GPU handles the HEVC coding while any 3D rendering is being done by the graphics card. That is only my observation though. That may well not be what is going on.

Ray.

Zkuggi wrote on 2/26/2021, 10:58 AM

I found another post where you got me on right track @johnebaker.

https://www.magix.info/us/forum/vpx11-color-space-color-space-correction-instruments-meter-setting--1235743/#ca1505273

Turned out my project setting was BT2020 while my source and rendering settings are 8bit BT.709

Changed the project settings to BT.709 but kept everything else the same. Started rendering to HEVC again but still no result. No hardware encoding and slow rendering speed.

Then I tried (for no particular reason) to DESELECT the option to "calculate video effects on GPU" and then the encoding uses the GPU and I see close to real-time rendering speeds. I would say this is around 6-8x faster than what I saw before.

Played around with this and it seems to be that I have to have both the color space identical and also disable the "calculate the video effects on GPU" to obtain optimal rendering speed.

Thanks again for your support. @CubeAce I've updated my signature in my profile for future purposes.

CubeAce wrote on 2/26/2021, 11:49 AM

@Zkuggi @johnebaker

Well I'm glad that is sorted.

We had seen similar effects in the past with not ticking the "calculate video effects on GPU". It never caused that much of a difference in the past though so I discounted it in this instance .Sorry.

The colour space bit is a new one on me so thank you for the additional information and will try it out for myself at some future point to see if I find a similar improvement. That could be the missing link in this one so thank you for the additional information.

Ray.

johnebaker wrote on 2/26/2021, 12:03 PM

@Zkuggi

Hi

@CubeAce commented:

. . . . As far as I can work out the Intel GPU handles the HEVC coding while any 3D rendering is being done by the graphics card. . . . .

There are 2 effects that benefit the most from the Nvidia GPU:

Stabilisation, on some exports my RTX 2060 hits mid 90's % usage
Neat Video Denoiser - has to be purchased from Neat Video, if you have it, the effect renders about 5x faster using the Nvidia - though it is still slow at 2.5 - 8 fps.

Good to hear the rendering is better - that option is a pain you never know if it will improve things or not - personally I never use it.

HTH

John EB

CubeAce wrote on 2/26/2021, 12:14 PM

@johnebaker @Zkuggi

Hi John.

I can definitely add a third effect.

My Boris Titling effects really maxes out my nvidia 1650super.

Ray.

emmrecs wrote on 2/26/2021, 1:33 PM

@CubeAce @Zkuggi @johnebaker

Slightly OT, but for me, exporting Full HD mp4 (need to check the exact settings, before you ask!) and using "Calculate Video Effects on GPU" speeds up the process by at least 25 - 30%.

Jeff

CubeAce wrote on 2/26/2021, 1:43 PM

@emmrecs

Hi Jeff.

I don't think you are off topic as if you remember when I first picked upon this there seemed to be varying differences between different people's systems. In some respects it seems a bit of a lottery when trying to find a one solution fits all setting. A bit like video recording itself 😉.

Ray.

Scenestealer wrote on 2/28/2021, 5:50 PM

@Zkuggi @CubeAce @johnebaker

The key to your strange behaviour when exporting is probably due to the fact that that your Intel Integrated GPU is not showing up in your Task Manager screen shot which indicates you Integrated Intel GPU is either, not activated in the Bios as described by John EB, or is not present in the i9-9900(suffix?) model you specified in your signature.

Peter