I don't have the NV encoder rendering option

Comments

RogerS wrote on 11/14/2021, 8:15 PM

I would uncheck it.

What MagicAVC template did you use? Were you able to use MagicAVC with NVENC, VCE or QSV with this enabled?

Former user wrote on 11/14/2021, 10:20 PM

I turned off Allow legacy GPU rendering & rebooted Vegas

I tried all combinations i could with MAGIX HEVC & AVC

All rendered normally, for this 1920x1080 clip @ 27-33secs, except MAGIX HEVC/AAC (INTEL QSV) Mainconcept HEVC), that turned on an encoder

and gave me this 🤣🤷‍♂️

Turning Allow legacy GPU rendering back on i get the same result double screen with that one above, doesn't matter tho, i never use HEVC, the others rendered at similar times to when it was unticked, I didn't notice any difference.

The fastest & from my experience of a rendered clip playing well when imported back in Vegas is -

MAGIX AVC/AAC MP4 - Internet HD 2160p (NVENC) (or 1080p) default settings in the Customize tab, with Allow legacy GPU rendering ticked (on), that's my setting i use all the time.

If there's pics or text in the timeline i still use MAGIX AVC/AAC MP4 - Internet but not the one with (NVENC) at the end, the pics & text can get messed up. it's a little slower but more reliable, the render is as it is on the timeline,

this vid 2.08min 1920x1080 29.97 vid with Allow legacy GPU rendering ticked rendered at 23secs

& with Allow legacy GPU rendering unticked it rendered at 29secs.

 

Former user wrote on 11/14/2021, 10:24 PM

@Adam-Wicher did you get it sorted out?

RogerS wrote on 11/15/2021, 1:11 AM

I think you are saying that QSV (Intel iGPU hardware encoding) worked once legacy encoding was off but gave visual glitches. Maybe try a different iGPU driver. Can't really tell if QSV rendering actually worked as there was no screenshot of the iGPU, just the NVIDIA one in task manager/ performance.

You were able to render to NVENC (NVIDIA hardware encoding) even with legacy encoding on, though there is no screenshot to show that from task manager/performance. Still issues with text corruption, I see. I thought the fix to dynamic ram preview in VP 19 should have addressed that. Before I had to set that to 0MB and turn off GPU acceleration in preferences/video to get NVENC renders to work properly (or just not bother and wait for MagicAVC with Mainconcept).

Legacy rendering should appear under SonyAVC and is CUDA or OpenCL, I believe. Never worked with it myself as my old cards weren't supported. If it doesn't bother NVENC encoding then no harm in leaving it on, thanks for testing.

Some info about it old rendering modes here: https://www.vegascreativesoftware.info/us/forum/faq-graphics-cards-gpu-acceleration-for-vegas-pro--104614/

Adam-Wicher wrote on 11/15/2021, 4:49 AM

Well, I have a GeForce RTX 3060 card with the latest drivers installed.

Which number exactly?
The latest are not always the best to use in an edit program.

Hi, my version of NVidia drivers:

472.47 date: 2021.11.10

Now i use studio edition but i tried with Game Ready drivers too. Unsuccessfully

Adam-Wicher wrote on 11/15/2021, 4:56 AM

The newest drivers should work- I haven't seen any issues reported with the latest Studio drivers- can you share a screenshot of help/driver update to confirm your version number?

If you uncheck legacy AVC in file io is it still missing? While these should not be linked, perhaps they are. Please hit "default" on file i/o, restart Vegas and see if that changes anything.

I assume in preferences/deprecated features "allow legacy GPU rendering" is unchecked.

@RogerS. I hit "default" on file i/o, restart Vegas and no results

In preferences/deprecated features "allow legacy GPU rendering" is unchecked and I restore default.

and nothing happened

Adam-Wicher wrote on 11/15/2021, 5:03 AM

So I'm still at the starting point. And do you think it might depend on the BIOS settings?

Former user wrote on 11/15/2021, 12:35 PM

If you untick legacy AVC in file io is it still missing?

 

What happens if you untick both of these, do you get different options in Hardware Decoder to use?

RogerS wrote on 11/15/2021, 10:59 PM

472.47 Studio and game ready are the same driver- just stick to Studio as they come out less frequently with better testing.

Unchecking legacy AVC should at least bring back hardware decoding- does it also enable different render options (it shouldn't, but...) That should have been restored when you reset the program (you did that, right)?

Last changed by RogerS on 11/15/2021, 11:01 PM, changed a total of 1 times.

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700 with Intel 630 iGPU (driver 27.20.100.9664), dual internal SSD (256GB; 1TB), Windows 10 64 bit

Vegas 19.636

Adam-Wicher wrote on 11/16/2021, 3:57 AM

I unticked both of these: . After I RESET the program with ctrl+shift buttons and in render options I have the same situation:

I don't know what to do. Maybe I should reinstall windows?

RogerS wrote on 11/16/2021, 4:57 AM

Okay, so you reset the program and left enable legacy AVC decoding off yet Vegas can't find the NVIDIA graphics card for decoding or encoding (rendering) though it can find the Intel QSV one for HEVC.

Hmm... under preferences/video does it find the NVIDIA card now, or no?

Does the NVIDIA card function in other programs without issue? (if you go to task manager/performance you can see it doing something with an app that uses 3D or a benchmark)?

Before reinstalling Windows maybe try a support ticket to Magix. Scroll to the top here and click on support but don't go to ask the community. Search for your problem, say that didn't solve it and then create a ticket.

j-v wrote on 11/16/2021, 5:14 AM

After I RESET the program with ctrl+shift buttons ...........

I don't know what to do. Maybe I should reinstall windows?

Is is very important for this function to delete the cached files for that program. Did you actually used that option by checking it?

 

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 21H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti, Intel HD graphics 630
Laptop  :Asus EVO37T, W11 home version 21H2, CPU i7-10875H, 16 GB RAM, Intel UHD Graphics + NVIDIA GeForce RTX 2070. VP 19 and VMS PL 17 are installed, all latest builds, Nvidia GPU driver version 512.96 Studiodriver and Intel GPU
driver 30.0.101.1994
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEML DONOR !!!

Older Dutch tutorials of 3POINT and me: https://vimeo.com/vegasvideoforum

Adam-Wicher wrote on 11/16/2021, 7:11 AM

Does the NVIDIA card function in other programs without issue? (if you go to task manager/performance you can see it doing something with an app that uses 3D or a benchmark)?

I think so, checked by 3D

So, I'll  try a support ticket to Magix

Adam-Wicher wrote on 11/16/2021, 7:12 AM

After I RESET the program with ctrl+shift buttons ...........

I don't know what to do. Maybe I should reinstall windows?

Is is very important for this function to delete the cached files for that program. Did you actually used that option by checking it?

 

Yeah, I deleted cached files

VEGASHeman wrote on 11/16/2021, 12:39 PM

@Adam-Wicher It looks like VEGAS is not able to detect any hardware decoders on your system.

VEGAS will normally launch a separate process, called 'So4HardwareDetection.exe' at startup, to find available hardware decoders/encoders. The results of that detection are stored in a file named 'So4HardwareDetectionOutput.xml', in a folder called c:\Users\<USERNAME>\AppData\Local\MAGIX\FileIO\1.0 (replace <USERNAME> with your actual Windows user id). If an error is encountered while detecting the hardware, a file named 'So4HardwareDetectionError.log' will be created, and record details about such an error. Can you inspect this folder, and upload the contents of either of the above files?

If no such folder is found, please follow the steps below to directly run So4HardwareDetectionOutput in a console window, and share the results of that command:

1. Open the CMD window (right click on Windows logo in bottom left corner, select "Run", and type in "cmd" in the dialog).

2. When the command console comes up, type in the following:

C:\Users\<USERNAME>>cd "\Program Files\VEGAS\VEGAS Pro 19.0"\

C:\Program Files\VEGAS\VEGAS Pro 19.0>So4HardwareDetection.exe

 

Adam-Wicher wrote on 11/16/2021, 4:35 PM

@VEGASHeman 

I did as you asked - in the 2 folders you are talking about - there were no files.

 

then I did the procedure in CMD. Results:

VEGASHeman wrote on 11/16/2021, 4:57 PM

Thank you - the output from the command shows that hardware decoders (and encoders) are available, at least on your system.

So we now need to figure out:

1) Why the So4HardwareDetectiontOutput.xml file is missing from your  c:\Users\<USERNAME>\AppData\Local\MAGIX\FileIO\1.0 folder, and

2) Is there a way to fix this using some alternate ideas.

For Point #2, could you try running the following command from the command console (use same instructions as above to launch the command window):

C:\Users\<USERNAME>>cd "\Program Files\VEGAS\VEGAS Pro 19.0"\

C:\Program Files\VEGAS\VEGAS Pro 19.0>So4HardwareDetection.exe -F C:\users\<USERNAME>\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml

Please replace <USERNAME> with your Windows user, as before. This should create a file in the right location; if you see any error on the command window, please let me know - there may be an issue with permissions or a Virus Checker, perhaps, preventing this from happening. If the file does get created, please launch VEGAS and see if your hardware choices are now available.

Adam-Wicher wrote on 11/16/2021, 5:22 PM

I did your indstructions, but I have command: The specified file could not be found

I hope I wrote all fraze well.

VEGASHeman wrote on 11/16/2021, 5:28 PM

Please remove the "<" and ">" around your user name - all of "<USERNAME>" should be replaced with your Windows user name, so "C:\Users\Tutodz\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml", in your case (I apologize for not getting the accent characters right).

Adam-Wicher wrote on 11/16/2021, 5:36 PM

ok, file created. but without result in rendering options.

VEGASHeman wrote on 11/16/2021, 5:38 PM

Do you see any Hardware Decoders listed in "Options" -> "Preferences" -> "File I/O" -> "Hardware Decoder To Use" drop-down list?

VEGASHeman wrote on 11/16/2021, 5:38 PM

(also, once this file is created, you will need to restart VEGAS)

Adam-Wicher wrote on 11/16/2021, 5:42 PM

I restarted all computer. In File I/O i see:

VEGASHeman wrote on 11/16/2021, 5:44 PM

That means VEGAS is not able to correctly read the contents of that file, for some reason.

Can you also share the contents of your "fileio_x64.log", located in c:\Users\Tutodz\AppData\Local\VEGAS Pro\19.0" folder. There should be a section towards the end of the file, called "== Start Hardware Decoders Auto-detection" - I am mostly interested in that, but the whole log should also do.