- Posts: 2
- Joined: Wed Aug 07, 2024 8:19 pm
- Real Name: Adin Biederman
Thu Aug 08, 2024 12:30 am
Hey there!
So I've spent the last few hours diving down debugging and troubleshooting rabbit holes, but I'm now pretty confident NVENC is broken in Resolve 19 betas 5 and 6. I first noticed the issue when trying to enable Remote Monitoring and it giving a "Failed to Initialize Video Encoder" error - diving into debug logs at that point, I see from RemoteStreamer: "Failed to initialize, failed to open NVENC session (NV_ENC_ERR_INVALID_VERSION).".
Huh, that's odd - I'm on the latest release Nvidia Driver (3080 Ti, Win 10) - maybe its a studio vs game ready issue? So I try a fresh install of both the latest studio and game ready drivers and nope, still the same error. Out of curiosity/desperation, I then went and tried reverting back to a driver from a few months back that I know NVENC worked with Resolve 18.6 with, and nope - still the same error. Did one more clean install using latest nvidia studio driver, and after it still giving the NV_ENC_ERR_INVALID_VERSION I decided to pivot.
Next up, I thought "If Remote Monitoring is trying to use NVENC and is failing, does normal NVENC deliver work?" Aaaaand of course, the answer is no. The deliver window popup error gives a "Render Job 2 failed as the current clip could not be processed, Cannot find appropriate codec for encoding the video frame." error. Native (software/cpu based) H264 and H265 work fine, but neither work with the Nvidia Encoder selected.
Going into the debug logs, here we get a bit more info, SyManager comes back with the error "There is no current clip, SetCurrentFrame failed.", followed by IO's error reporting logging: "NVENC m_EncodeAPI.nvEncOpenEncodeSessionEx(&encodeSessionExParams, &m_pEncodeSession) return: 15", "Nvidia codec cannot be initialized with property successfully", and "Failed to create encoder."
At this point, I check if NVENC is functioning at all on my system, and try using Handbrake's NVENC x264 encoder, and it works flawlessly. I try OBS NVENC recording, works great. Go back to Resolve, and it errors out. I double check Resolve's Memory and GPU settings and yup - 3080 Ti selected, processing mode CUDA, neural engine support enabled, memory limits near maxed out - everything looks fine.
Looking online for the exact NVENC error log message, it looks like this post is saying the return: 15 is due to some invalid struct version error: forums.developer.nvidia. com/t/openencodesessionex-fail-with-invalid-struct-version-error/125076 but that's starting to get out of my wheelhouse.
Figured I'd let you guys know about this to hopefully figure out whats going on!
Thanks!
Edit: Link to Resolve diagnostic log zip, system info NFO, and dxdiag txt: https:// drive.google. com/drive/folders/1230hTrtHy4MIXLfXP2RYOIGJoyYckUDv?usp=sharing
So I've spent the last few hours diving down debugging and troubleshooting rabbit holes, but I'm now pretty confident NVENC is broken in Resolve 19 betas 5 and 6. I first noticed the issue when trying to enable Remote Monitoring and it giving a "Failed to Initialize Video Encoder" error - diving into debug logs at that point, I see from RemoteStreamer: "Failed to initialize, failed to open NVENC session (NV_ENC_ERR_INVALID_VERSION).".
Huh, that's odd - I'm on the latest release Nvidia Driver (3080 Ti, Win 10) - maybe its a studio vs game ready issue? So I try a fresh install of both the latest studio and game ready drivers and nope, still the same error. Out of curiosity/desperation, I then went and tried reverting back to a driver from a few months back that I know NVENC worked with Resolve 18.6 with, and nope - still the same error. Did one more clean install using latest nvidia studio driver, and after it still giving the NV_ENC_ERR_INVALID_VERSION I decided to pivot.
Next up, I thought "If Remote Monitoring is trying to use NVENC and is failing, does normal NVENC deliver work?" Aaaaand of course, the answer is no. The deliver window popup error gives a "Render Job 2 failed as the current clip could not be processed, Cannot find appropriate codec for encoding the video frame." error. Native (software/cpu based) H264 and H265 work fine, but neither work with the Nvidia Encoder selected.
Going into the debug logs, here we get a bit more info, SyManager comes back with the error "There is no current clip, SetCurrentFrame failed.", followed by IO's error reporting logging: "NVENC m_EncodeAPI.nvEncOpenEncodeSessionEx(&encodeSessionExParams, &m_pEncodeSession) return: 15", "Nvidia codec cannot be initialized with property successfully", and "Failed to create encoder."
At this point, I check if NVENC is functioning at all on my system, and try using Handbrake's NVENC x264 encoder, and it works flawlessly. I try OBS NVENC recording, works great. Go back to Resolve, and it errors out. I double check Resolve's Memory and GPU settings and yup - 3080 Ti selected, processing mode CUDA, neural engine support enabled, memory limits near maxed out - everything looks fine.
Looking online for the exact NVENC error log message, it looks like this post is saying the return: 15 is due to some invalid struct version error: forums.developer.nvidia. com/t/openencodesessionex-fail-with-invalid-struct-version-error/125076 but that's starting to get out of my wheelhouse.
Figured I'd let you guys know about this to hopefully figure out whats going on!
Thanks!
Edit: Link to Resolve diagnostic log zip, system info NFO, and dxdiag txt: https:// drive.google. com/drive/folders/1230hTrtHy4MIXLfXP2RYOIGJoyYckUDv?usp=sharing
Last edited by adinbied on Thu Aug 08, 2024 1:01 pm, edited 1 time in total.
