GPU Render Templates are suddenly missing from MAGIX AVC/AAC MP4

Greg-Smith9805 wrote on 3/7/2023, 10:20 AM

This is my first forum post. Have been using Vegas pro on and off for many years but only recently have been working with 4k+ cameras.

I just built a custom machine for video editing mainly to speed up rendering with Neat noise reduction V5. When I first installed Vegas pro 20 in render as for MAGIX AVC/AAC MP4 options were displayed for processor only, Intel QSV, and NVENC. Now after updating the video drivers and a few re-installs of Vegas, and resets (shift ctl, double click) the Intel QSV and NVENC profiles are no longer displayed.

In video preferences GPU acceleration of video processing is set to Optimal - GeForce GTX 1070 and I have tried a number of different settings for Dynamic RAM preview that does not seem to have an effect on the rendering options displayed. Right this minute RAM preview is set to 0 MB.

Interestingly MAGIX HEVC/AAC MP4 does show some templates for Intel QSV but none for NVENC.

Yesterday morning both the NVENC and Intel QSV options were displayed for MAGIX AVC/AAC MP4. At some point, the Intel QSV options disappeared and then after I went into the BIOS and sped up the memory bus to 5200 MHz and updated the NVENC driver and maybe some other things the NVENC render option disappeared.

In the File I/O preferences for HW decoder to use I only have the options of Off and Auto (off). On my previous slower but stable machine I also have the options of QSV and NVDEC. I'm not sure that my new machine had those options under File I/O but it probably did.

As far as I know I have tried all of the suggested fixes in the post below which pretty much is the same issue I am having except for VP 19. There was no resolution in this thread.

http://vegascreativesoftware.info/us/forum/render-as-does-not-show-any-gpu-profiles-in-vp-19-build-550--135284/

Before the NVENC render template disappeared for a test project with just one 3840x2160 video track with just a track color grading input LUT for V-log to REC.709 and the Neat noise reduction applied to the event I was averaging somewhere around 5 fps. Now without the NVENC the render speed is about the same. Is Vegas smart enough to determine that my CPU is just as fast as my NVENC GPU?

The Neat software under tools -> preferences -> performance shows a speed of 15.1 fps with Use CPU and GPU checked, 14.9 fps for CPU only and 5.33 fps for GPU only so that might be the case but I was not aware that the plugins could be so tightly coupled with Vegas. When deinstalling Vegas and cleaning out the local files (AppData -> Local -> Vegas Pro -> 20.0) I did not remove the NewBlue and Neat plugins - maybe I should have also uninstalled and re-installed the plugins. I don't think that I ever successfully performed a clean install because the program remembered the product key.

I have searched on everything I can find and have not found an explanation as to how Vegas might modify the rendering template choices based on system performance.

Is there any explanation of how Vegas makes choices on what rendering templates to display? This new machine is ready for a 4090 graphics card but I wanted to make sure that I have a stable configuration with the old 1070 card that I had before making that investment.

As a side note, Vegas was crashing after every render completed (short test renders). I think that backing out the latest windows .Net framework patch fixed that but I am not sure.

Comments

Wolfgang S. wrote on 3/7/2023, 10:29 AM

Now after updating the video drivers and a few re-installs of Vegas, and resets (shift ctl, double click) the Intel QSV and NVENC profiles are no longer displayed.

I would try to go back to older driver for the GPUs.

Greg-Smith9805 wrote on 3/7/2023, 11:10 AM

Wolfgang, thanks for responding.

I'm not sure what previous drivers I should try. Microcenter built this machine and I am finding out that a number of drivers are not up to date so I have been updating them...

It might be interesting that Vegas is offering to download the driver that I already have installed as far as I can tell. Too bad the Intel UHD graphics check is broken. For what it's worth the Intel QSV template in render as disappeared before I updated that driver. Is it possible that VP 20 is not compatible with the latest drivers? I figured that the Studio Driver (not the game driver) was a safe bet.

Wolfgang S. wrote on 3/7/2023, 11:25 AM

That is hard to say, since I do not know what version your original drivers were. Can Microcenter give you the information, what driver they had installed originally? Is there a backup that would allow you to go back to the old status of the system?

Sure, it can be that newer driver are not compatible with the render function. From time to time you hear such reports. But I do not know, what happened here really. But the assumption, that something happened when you installed the newer driver, is maybe a good idea to follow.

Wolfgang S. wrote on 3/7/2023, 12:03 PM

Maybe you can check in the windows update, which updates took place?

Greg-Smith9805 wrote on 3/7/2023, 1:05 PM

Wolfgang,

Thanks for staying with me here. Because Microcenter did not update the driver - they just mounted the card in the chassis there is nothing to roll back to. My options for experimentation are listed in the snip below. Assuming that Vegas tested with the latest drivers when they released the Vegas 20 update Build 326 on January 23 I guess I should go back two versions to 528.02 that was released on Jan 5. Do you think I should go back further?

Greg-Smith9805 wrote on 3/7/2023, 1:24 PM

I installed the Jan 5 older driver and re booted. Now Vegas won't start. That is another issue I have been having... Might have to remove it an install again

Greg-Smith9805 wrote on 3/7/2023, 1:43 PM

Finally managed to uninstall and re-install Vegas Pro 20. Rolling the NVIDIA driver back to v 528.02, 2023 Jan 5. Did not bring back the GPU render options.

j-v wrote on 3/7/2023, 1:50 PM

@Greg-Smith9805
Did you ever a total reset of Vegas ?
Also give a screenshot right after clicking "render as"

VEGASDerek wrote on 3/7/2023, 1:58 PM

Probably an issue with the hardware detection. Could you please provide us with this file: C:\Users\(your username)\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml

@Greg-Smith9805

Greg-Smith9805 wrote on 3/7/2023, 2:38 PM

@Greg-Smith9805
Did you ever a total reset of Vegas ?
Also give a screenshot right after clicking "render as"

Probably an issue with the hardware detection. Could you please provide us with this file: C:\Users\(your username)\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml

@Greg-Smith9805

I don't have a So4HardwareDetectionOutput.xml file?

VEGASDerek wrote on 3/7/2023, 2:41 PM

I don't have a So4HardwareDetectionOutput.xml file?

That would explain the problem. Please create a support ticket and they should be able to help you through this.

@Greg-Smith9805

Greg-Smith9805 wrote on 3/7/2023, 2:51 PM

My bad on the hardware detection file...

How do I attach a .xml file? The upload file seems to just allow media files.

I don't seem to be able to attach any more pictures. Will try next to send a snip of part of the xml file.

Greg-Smith9805 wrote on 3/7/2023, 2:54 PM

The detection error file just lists all the detection errors. Notice that the .xml file was created early yesterday morning before I started loosing rendering and file I/O options. I think you are on to something here - of course I have no idea how to fix it...

VEGASDerek wrote on 3/7/2023, 3:14 PM

More than likely, the Intel driver is causing the problem.

Greg-Smith9805 wrote on 3/7/2023, 3:20 PM

More than likely, the Intel driver is causing the problem.

It just occurred to me that I can paste in the whole .xml file text which is below. By Intel driver do you mean the Intel UHD graphics driver or the OpenCL HD graphics or maybe something else that I am not seeing?

<?xml version="1.0" encoding="utf-8"?>
<hardware_detection>
   <version>2</version>
   <operating_system>
       <version>2009</version>
       <build_number>22621</build_number>
       <updated_build_revision>1344</updated_build_revision>
   </operating_system>
   <OpenCL>
       <num_platforms>2</num_platforms>
       <platform_0>
           <name>NVIDIA CUDA</name>
           <vendor>NVIDIA Corporation</vendor>
           <version>OpenCL 1.2 CUDA 11.1.96</version>
           <num_devices>1</num_devices>
           <device_0>
               <name>GeForce GTX 1070</name>
               <version>OpenCL 1.2 CUDA</version>
               <driver_version>456.71</driver_version>
               <boardName/>
               <pciId>0</pciId>
               <pciSlot>0000:01:00.0</pciSlot>
               <platformIndex>0</platformIndex>
               <deviceIndex>0</deviceIndex>
           </device_0>
       </platform_0>
       <platform_1>
           <name>Intel(R) OpenCL HD Graphics</name>
           <vendor>Intel(R) Corporation</vendor>
           <version>OpenCL 3.0 </version>
           <num_devices>1</num_devices>
           <device_0>
               <name>Intel(R) RaptorLake-S Mobile Graphics Controller</name>
               <version>OpenCL 3.0 NEO </version>
               <driver_version>31.0.101.1989</driver_version>
               <boardName/>
               <pciId>0</pciId>
               <pciSlot>0000:00:02.0</pciSlot>
               <platformIndex>1</platformIndex>
               <deviceIndex>0</deviceIndex>
           </device_0>
       </platform_1>
   </OpenCL>
   <DXGI>
       <num_adapters>3</num_adapters>
       <adapter_0>
           <adapter_number>0</adapter_number>
           <vendor_id>4318</vendor_id>
           <device_id>7041</device_id>
           <device_name>NVIDIA GeForce GTX 1070</device_name>
       </adapter_0>
       <adapter_1>
           <adapter_number>1</adapter_number>
           <vendor_id>32902</vendor_id>
           <device_id>42880</device_id>
           <device_name>Intel(R) UHD Graphics</device_name>
       </adapter_1>
       <adapter_2>
           <adapter_number>2</adapter_number>
           <vendor_id>5140</vendor_id>
           <device_id>140</device_id>
           <device_name>Microsoft Basic Render Driver</device_name>
       </adapter_2>
   </DXGI>
   <hardware_decoders>
       <num_decoders>2</num_decoders>
       <preferred_decoder_0>
           <vendor_id>2</vendor_id>
           <vendor_name>QSV</vendor_name>
           <device_name>Intel(R) UHD Graphics</device_name>
           <vendor_unique_id>5</vendor_unique_id>
       </preferred_decoder_0>
       <preferred_decoder_1>
           <vendor_id>4</vendor_id>
           <vendor_name>NVDEC</vendor_name>
           <device_name>NVIDIA GeForce GTX 1070</device_name>
           <vendor_unique_id>0</vendor_unique_id>
       </preferred_decoder_1>
   </hardware_decoders>
</hardware_detection>

Greg-Smith9805 wrote on 3/7/2023, 3:28 PM

More than likely, the Intel driver is causing the problem.

If I understand what you are saying, the Intel graphics driver that is listed in the .xml file 31.0.101.1989 was probably OK. The current driver 31.0.101.3302 is likely the problem?

VEGASHeman wrote on 3/7/2023, 4:36 PM

@Greg-Smith9805: From the hardware detection output XML you posted, it seems like both of your GPUs are detected:

 <hardware_decoders>
        <num_decoders>2</num_decoders>
        <preferred_decoder_0>
            <vendor_id>2</vendor_id>
            <vendor_name>QSV</vendor_name>
            <device_name>Intel(R) UHD Graphics</device_name>
            <vendor_unique_id>5</vendor_unique_id>
        </preferred_decoder_0>
        <preferred_decoder_1>
            <vendor_id>4</vendor_id>
            <vendor_name>NVDEC</vendor_name>
            <device_name>NVIDIA GeForce GTX 1070</device_name>
            <vendor_unique_id>0</vendor_unique_id>
        </preferred_decoder_1>
    </hardware_decoders>

VEGAS currently assumes that hardware encoders are available for all known hardware decoders, and will accordingly show those presets.

Could you launch the Hardware Detection explicitly from within VEGAS, using the following steps:

1. With the SHIFT key pressed, select the "Help" menu entry, and select "Launch Hardware Detection...". Please take a screen shot of the dialog shown (it should list something similar to above - two entries - 1 for Intel GPU, and 2 for NVIDIA GPU if everything is OK).

2. If the entries don't show up as expected, please click on the "Get fresh data and overwrite cache" checkbox, and select the Update button to the very right.

Greg-Smith9805 wrote on 3/7/2023, 4:51 PM

When launching hardware detection I get "Hardware Detection Error" Process crash error

When I click on OK then I have the option to check the Get fresh data and overwrite cache it does nothing for more than 2 seconds. If I click on the "re-do" arrow at the right it just shows that detection failed (crashed) again.

I can't figure out how to open a support ticket - can anyone walk me through that?

Greg-Smith9805 wrote on 3/7/2023, 4:54 PM

If you look at my 3:51 post you will see that at some point hardware detection was working and that XML file was created maybe multiple times but for over a day Hardware detection has been failing

VEGASHeman wrote on 3/7/2023, 5:12 PM

Thank you for the update - and clarifying that the output detection XML was from earlier. Based on the above results, it seems VEGAS cannot work with either of your GPU/drivers, so it would be best to get the machine into a better state first. Is it possible for you to reset your BIOS to default settings (you had mentioned bumping up the memory speed)?

As far as some of the questions you had asked in your original post, the render template entries for HEVC QSV will show up even when the QSV hardware is not detected, as it will fallback to the software QSV renderer (which uses the CPU instead), but that is not the case for AVC. Also, if the hardware detection fails, the corresponding entries will not show up in the File I/O preferences -> Hardware Decoder To use, which is also what you do see.

I will let @VEGASDerek help you through opening up a support ticket.

Greg-Smith9805 wrote on 3/7/2023, 5:22 PM

I successfully submitted a support ticket. I had to use the edge browser. For some reason I couldn't click on the support button with chrome.

I went to the Intel site (as opposed to the MSI site) and updated my integrated graphics driver and the Intel tool installed version 31.0.101.4146. That did not help. I'll go back into the BIOS and reset but this problem started before I updated the RAM speed so I don't think that will help.

Thankyou very much for explaining why I see some GPU support options for HEVC.

Greg-Smith9805 wrote on 3/11/2023, 11:28 PM

Neal from Magix support helped me troubleshoot the issue. He first had me uninstall VP from my normal user account and install it in an admin account. From and admin account HW detection worked. He then had me uninstall VP from the admin account and reinstall on my user account. He reasoned that the issue must be with the registry so he had me edit the registry to give my user account full permissions for the path down to the VP PRO 20 key. That did not work. He then gave me instructions on how to do a clean install which involved deleting a number of directories and registry keys. Following his instructions VP HW detection still crashed. Since this is a new computer and the only MAGIX SW on it I care about is VP20 I just searched for all folders on the C drive with MAGIX and deleted them all and again removed the registry keys. It took three tries and of course I had to delete all those folders and keys each time. In the end, I had gotten rid of enough so that HW detection worked again. I could post all the details but the specific instructions he gave did not work for me. Since doing that I have spent a day doing editing and the program has not crashed once. In the past even before HW detection stopped working on this machine and my previous machine VP would crash every now and then, usually during an undo operation. It seems to be rock solid now. QSV still does not show up in render options but I think that is simply because the latest intel drivers don't support it.

RogerS wrote on 3/12/2023, 1:05 AM

For QSV not appearing do you have more than one display connected? If so try to disconnect one and see if it comes back.