Nvidia GPU accelerated LUT Filter Failure

ken-dehoff wrote on 2/11/2019, 3:49 PM

All:

***Updating the post to better reflect where my nvidia gpu-accelerated problem is - I consider this a bug - maybe VP16, maybe an nvidia driver issue - my question remains - where's a document to work through an issue like this***

I've been a vegas pro user since V12 and every rev I get a new computer with an nvidia card - and can never get it to work reliably ;( I have had much better success with Intel's hw rendering but for other uses the intel video driver isn't the best. So I'm trying once again to render with nvenc and getting failures. I was hoping there is some recent documentation on how to get nvenc to work reliably.

I have an 8700k, GT1060, 16GB RAM - I've updated all system drivers to their latest, set the preview memory max to 0.

My video source is gopro 7 (hevc) 4k/59.94 and am doing very little in terms of filters (for debugging all effects are off). I have an hour of video to render and it typically gets to between 10 and 12 percent and then I see the preview window stop updating while the rendering countdown continues.

I'd love to see anyone's successful (recent) experience fixing this kind of issue. Since this is the 4th generation of vegas I've not been able to make work with nvidia - appreciate any pointers.

Comments

j-v wrote on 2/11/2019, 4:11 PM

I have no problem with rendering of my GOpro files and I also tried the Gopro 7 HEVC files I could find without a problem all in 50p
The GoPro 7 HEVC takes more time but no stops or freezing.
But I never do rendering of an hour, 25 minutes were the longest renderfiles. Who wants to look at a video of more than an hour except it is an exiting story that wait a long time till its solution?

If you send a file on a cloud service I can try it multplied and than try to render it to??????
What is your rendertemplate in Vegas Pro 15 or 16??
And what are your project settings???

j-v wrote on 2/12/2019, 6:53 AM

Did you already tried to let the Nvidia start your Vegas software,

and set it also as the dedicated GPU in Options/Preferences/Video for GPU acceleration of Video processing

and for your rendering this template?

ken-dehoff wrote on 2/12/2019, 1:47 PM

Why I hate 'troubleshooting' nvidia when the Intel encoder 'just works'.....

I've simplified my project down to the smallest elements to cause the failure. I did mis-state on not using an effect - I do in fact have the LUT filter on to color the video. I have gpu processing enabled. I have gotten the fault to happen reliably after processing 17,000 frames. Tested by moving the render window in the file. It's not memory - I added a 2nd 16 GB DIMM to test (so I'm back to 16GB for now). So the problem is not 'just' the nvencoder, but rather how it is interacting with the LUT filter.

Like I said before, I know other's have been through this but I am unable to find any history or links via google on how to approach this which if any of you have is what I'd love to have. FYI I did check my nvidia driver properties and have them set as close to J-V's as possible.

 

Here is a quick video of my screen when the hang occurs.

fr0sty wrote on 2/12/2019, 3:59 PM

Keep in mind, NVENC isn't using your system's memory, but rather the GPU's.

ken-dehoff wrote on 2/12/2019, 9:45 PM

I'm testing further and think this is a bug - either in VP16 or the Nvidia driver. The problem is - I have no idea how to report it - usually vendors like to point the finger across the aisle and not much gets done.

So here are my further results - to summarize I've tried different source formats and they all fail at approximately the same amount of data processed - leads me to think it is a memory exhaustion problem somewhere, but I don't see it in gpu-z, or windows task manager. All results are repeatable to the same exact frame as near as I can see and shifting the start point results in the same shift to the end point.

First test: 3840x2160 59.94 HEVC - 16,900 frames before fail

Second Test: 3840x2160 59.94 Magix intermediate format - 16,700 frames before fail

Third Test: 2704x1520 59.94 h.264 - 29,000 frames before fail

Fourth Test 3840x2160 29.97 h.264 - 33,800 frames before fail

 

fifonik wrote on 2/12/2019, 10:04 PM

You can try if the issue is re-producible with media generated content. This way it would be easier to supply the project file for testing on different systems. Then, if confirmed, you can submit it with bug report to Magix.

Chief24 wrote on 2/12/2019, 10:37 PM

Check this post concerning GoPro Hero 7 HEVC 4K60.

Self Build: MSI X399 Gaming Pro Carbon AC/1950X @ stock; 64GB Corsair 2666 Mhz; OS-Intel 750 800GB, Project Media-Samsung 960 EVO 1TB; (3) Samsung 850 EVO 500GB SSD for various (LightRoom & Photoshop), Render, Other Assets; Gigabyte WindForce GTX 1080 8GB; (2) 28" Samsung 3840x2160; Windows 10 Pro 64-Bit (1809); Magix Vegas Pro 15 Suite (416), Magix Movie Studio Platinum 15 Suite (157); Canon EOS 80D; GoPro Hero 5+ & 6 Black; Sound Forge Studio 12.6; Creative SoundBlaster Zx sound card; Magix Music Maker Premium 2019

ken-dehoff wrote on 2/13/2019, 1:22 PM

And I'm further down the rabbit hole...

The problem seems to occur when both effects and encoding are done by the nvidia gpu. So when I split the load - GPU processing for effects (lut filter) and quicksync for HEVC encoding, I get a 'low on memory' error. I'm running 32GB, a 64GB swap file so I don't think I'm out of memory (task manager shows 8GB in use, 10GB committed). What is this error message referring to - anyone know?

Chief24 wrote on 2/13/2019, 2:02 PM

????? GPU processing for (lut filter) and quicksync for HEVC encoding????? Uh, did you check out the link I provided for you concerning GoPro?

And, if your rendering continues to "Stop" at about the same time frame/frames (depending on your above resolutions), then to me it would be a corrupted file. Take that "One File" out of the project, extend an "In/Out" point to accomodate a minute or two past where the removed clip was, and give that a test render. At least it will help in further "troubleshooting"

Self Build: MSI X399 Gaming Pro Carbon AC/1950X @ stock; 64GB Corsair 2666 Mhz; OS-Intel 750 800GB, Project Media-Samsung 960 EVO 1TB; (3) Samsung 850 EVO 500GB SSD for various (LightRoom & Photoshop), Render, Other Assets; Gigabyte WindForce GTX 1080 8GB; (2) 28" Samsung 3840x2160; Windows 10 Pro 64-Bit (1809); Magix Vegas Pro 15 Suite (416), Magix Movie Studio Platinum 15 Suite (157); Canon EOS 80D; GoPro Hero 5+ & 6 Black; Sound Forge Studio 12.6; Creative SoundBlaster Zx sound card; Magix Music Maker Premium 2019

ken-dehoff wrote on 2/13/2019, 2:18 PM

yes I checked on the gopro - I also tested other manufacturer video sources which eliminates the source and format

OldSmoke wrote on 2/13/2019, 4:21 PM

Would you mind doing a quick test and set render threads to 1 and try to render it again?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15.

System Spec.:
Motherboard: Intel DX79SR
Ram: G.Skill 8x4GB DDR3 2133 (running at 1600 and lower latency)
CPU: 3930K @ 4.3GHz (custom water cooling system)
GPU: 1x ASUS Fury-X
Hard drives: 4x 2GB WD Red in RAID 5 (with Hot Spare), 2x Crucial 256GB SSD in RAID 0 (mulitcam project drive), 1x Samsung 850 Pro 256GB SSD (System), 1x Crucial 64GB SSD (temp files and swap file), 1x 3.5" Hotswap Bay, 1x LG BluRay Burner
PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM, 1x Sony HDTV 32" preview monitor

ken-dehoff wrote on 2/13/2019, 7:16 PM

I did the single-thread test and got the same results - it did run a little longer (maybe 10%). I backed into my problem statement about the Lut filter - at first this was a more generic nvidia complaint. I see now there are several threads already on the gpu-accelerated lut filter and Magix are working on it. Not sure why it worked (slowly) on intel but I've grabbed a 3rd party lut plugin to work around the issue. I note that if the LUT filter were working, the performance boost would be around 33% for my stuff - really hope they get it working soon!

Steve_Rhoden wrote on 2/13/2019, 7:46 PM

Stop getting hung up on relying on nvidia cards to make your editing experience faster, better and more efficient!

bob-h wrote on 2/13/2019, 9:10 PM

Stop getting hung up on relying on nvidia cards to make your editing experience faster, better and more efficient!

His nvidia card is much faster for video processing over the intel, but intel does the timeline decoding & good for hardware rendering. Ideally he'd use the intel & nvidia card at the same time. That could fix his rendering problem, but he might have qucksync problems also.

j-v wrote on 2/14/2019, 3:45 PM

His nvidia card is much faster for video processing over the intel,

With me QSV is a little faster but with lower bitrates it give me tiny faults, so I always use now Nvidia for all my rendering and hardware acceleration.
Only one time I was forced to let the last task and starting the program to the Intel GPU. That was in a project with 4 HEVC GOpro 4K tracks full of those files to render them into a 4K output with Pip's, what is not my normal workflow rendering to FHD AVC or HEVC included a lot of nested vegs. It were black parts in de render result.