Also, it's recommended for 4k, especially 4k HDR, that you have 32GB of RAM. For slideshows, however, you should be ok. As for the driver, you can run the driver update utility in the help menu to see if you have the one VEGAS wants you to have.

Here's where it got funny. I could never get a finished render using MAGIX HEVC/AAC MP4, HDR10 VBR 80,000,000 max / 40,000,000 min 

Is that one of the standard templates for your GPU encoder, or did you change something?

Which driverversion for the Nvidia 2070 do you use?

471.68 Studio

Also, it's recommended for 4k, especially 4k HDR, that you have 32GB of RAM. For slideshows, however, you should be ok. As for the driver, you can run the driver update utility in the help menu to see if you have the one VEGAS wants you to have.

The MB is an ASUS PRIME X370-PRO with 16Gb RAM. I can go up to 32Gb but was considering a new MB & CPU for Windows 11. Seems my AMD Ryzen 7-1700 isn't on the Win 11 compatibility list.

Seems my AMD Ryzen 7-1700 isn't on the Win 11 compatibility list.

Thus far from what I've read, MS has been intransient on relaxing their minimum specs for W11, but their W11 compatibility app has been MIA for a long time now. Hopefully, the min specs are still under discussion at MS.

Here's where it got funny. I could never get a finished render using MAGIX HEVC/AAC MP4, HDR10 VBR 80,000,000 max / 40,000,000 min 

Is that one of the standard templates for your GPU encoder, or did you change something?

"Is that one of the standard templates for your GPU encoder, or did you change something?"

Sorry, I'm not sure how to answer. I set File / Project Properties to HDR10. Everything else was preset automatically to HDR10 defaults.

Very hard to say what's wrong with your machine, maybe too old CPU/mobo or too less the RAM.

If you go continuously editing HDR10, I'd recommend you, take that RTX2070 out and throw the whole Dschunke away, make a brand new flattop!

From my signature you can see, my AMD RX5500XT is about 60% effective as an RTX2060, a secondhand one from eBay. Initially, I planned an RX5700XT or a new generation nVidia card. This planned waiting declined into the famous price chaos so that I went to eBay and paid 350€ for the RX5500XT.

Now I begin to love it.

For my 4k60pHDR10 project, I need some what more than 3:1 time to render in HEVC-mp4, or as intermediate in ProRes-mov, both can take the GPU acceleration up to 80%. Very stable.

Sure, I have a powerful CPU.

I think I may have found the issue.

The last version of Vegas Pro I purchased prior to 19 was v14. I had just built a new PC with a AMD GPU & the next few versions of Vegas offered GPU acceleration but only with nVidia GPUs support so I never upgraded. I have upgraded my GPU since then to a nVidia card, RXT 2070, 8Gb RAM. With the intro to v19 I upgraded.

As I have mentioned at the top, I thought all my preference setups were good but now realized I omitted one thing. I didn't notice I needed to use a NVENC template when rendering.

After customizing a NVENC to my project I ran a test render. A 34 second video of my slideshow took 7:15. The CPU was at a steady 40-46%. But the final video was terrible. It jittered & skipped while viewing on both the VLC player & the DIVX player, too.

I reset Vegas to no GPU & used the same settings but with the MC HEVC encoder. This time the 34 second video of the same section took 5:05 & the CPU was 85-95%. The video quality was flawless.

Not sure what's going on. (?) I did notice the absence of 2160p NVENC templates so maybe UHD is too much for NVENC rendering. (?)

My GPU is a RTX 2070 with 8Gb of RAM. I use 16Gb of DDR4 RAM & my CPU is an 8-core AMD Ryzen 1700 @ 3.00 Ghz.

RogerS wrote on 9/8/2021, 7:00 PM

Can you share a screenshot of your render template settings and project properties? I feel like we're missing info from your descriptions. See below

I didn't think Vegas had a Mainconcept HEVC encoder in 19. That's through Voukoder?

Yes there is & is called Encode Mode: Mainconcept HEVC

reset Vegas to no GPU Yes

You turned off the GPU in preferences/video? Yes
Have you tried actually resetting Vegas? https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/ Not yet

It can help with hard to diagnose issues.

________________________________________________________________________________________

Thanks RogerS.

The last version of Vegas Pro I purchased was v14 until now, v19. This is my first HDR project in Vegas Pro 19. The results without GPU acceleration look great on our OLED TV. Just now curious why GPU acceleration isn't working.

My project is UHD so the NVENC template had to be edited.

The entire project was a slideshow (montage) of 16-bit .psd photos. I used these to get the most out of HDR color.

Properties of each photo Color Space was set to Rec:2020. I had weird unusable results if set to Rec:2020, 1000nits. Color Range was set to Full. I got the best results using these settings no matter how it was rendered; with or without GPU

Project Properties were set to default for HDR10 videos. I have not tried resetting Vegas yet.

Can you share a screenshot of your render template settings and project properties? I feel like we're missing info from your descriptions.

I didn't think Vegas had a Mainconcept HEVC encoder in 19. That's through Voukoder?

reset Vegas to no GPU

You turned off the GPU in preferences/video?
Have you tried actually resetting Vegas? https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

It can help with hard to diagnose issues.

See post above

Have you tried actually resetting Vegas? https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

It can help with hard to diagnose issues.

I reset Vegas as instructed & the GPU render time was about the same as NO GPU. That's an improvement as with GPU render was 42% slower before Vegas reset. This time there were no rendering errors as before. Odd thing was the colors were off compared to the same render without GPU. Deep reds looked a little pale.

The good news is CPU usage was 12-16% compared to 86-95% without GPU.

Glad to hear you got it working. It's unexpected render times between GPU and not were the same, though perhaps for this particular task your CPU is fast enough and you end up hitting a GPU bottleneck somewhere passing 32-bit video through the GPU.

As far as color not being the same that's a problem and not one I have experience with. Consider using an extended gamut test image and looking at the vectorscope for CPU vs GPU render.

Other thoughts- turn smart resample to disable resample in project properties and set as default for future projects. Did you actually output (covert to) Rec2020 from your photo software? If not, I recommend downloading such an ICC profile and converting to it in your photo editing software before output. Then assign it in Vegas as you have been doing and it should better match your image editor. I don't think photo software will produce images with extended dynamic range at this point (extended gamut, yes) so don't assign as Rec 2020 1000 nits but bring up brightness/expand dynamic range in Vegas while looking at it on your HDR display. How does it work?

For dynamic ram preview, it's just a preview buffer. I keep it at 10% in VP 19 and it works fine. No need to allocate all your system ram to that as it's better used by Vegas, DXO, or whatever else you have open. There are diminishing returns.

Still photos are always full range, so that's a given. For output I see you are outputting 10-bit HEVC. I'd stick to the default for that color range (full?). Not sure what players expect- I see cameras putting out both full and limited 10-bit HEVC. Perhaps use a test target (black to white gradient) and look at it on your HDR display and check it as both full and limited and see if the blacks and whites display properly. If they look the same it likely doesn't matter.

Glad to hear you got it working. It's unexpected render times between GPU and not were the same, though perhaps for this particular task your CPU is fast enough and you end up hitting a GPU bottleneck somewhere passing 32-bit video through the GPU.

As far as color not being the same that's a problem and not one I have experience with. Consider using an extended gamut test image and looking at the vectorscope for CPU vs GPU render.

Other thoughts- turn smart resample to disable resample in project properties and set as default for future projects. Did you actually output (covert to) Rec2020 from your photo software? If not, I recommend downloading such an ICC profile and converting to it in your photo editing software before output. Then assign it in Vegas as you have been doing and it should better match your image editor. I don't think photo software will produce images with extended dynamic range at this point (extended gamut, yes) so don't assign as Rec 2020 1000 nits but bring up brightness/expand dynamic range in Vegas while looking at it on your HDR display. How does it work?

For dynamic ram preview, it's just a preview buffer. I keep it at 10% in VP 19 and it works fine. No need to allocate all your system ram to that as it's better used by Vegas, DXO, or whatever else you have open. There are diminishing returns.

Still photos are always full range, so that's a given. For output I see you are outputting 10-bit HEVC. I'd stick to the default for that color range (full?). Not sure what players expect- I see cameras putting out both full and limited 10-bit HEVC. Perhaps use a test target (black to white gradient) and look at it on your HDR display and check it as both full and limited and see if the blacks and whites display properly. If they look the same it likely doesn't matter.

I ran a 2nd render with the same settings & color was fine. Not sure what happened.

I guess I have been confused about rendering HDR video with photos. My only goal was to preserve 0-255 color (Full) of each photo so I set each to Rec:2020/Full. I did try Rec:2020-1000nits but the rendered results looked harsh/contrasty. I do see there's a difference when converting the profile to ITU-R_BT2020(beta) in Photoshop. I'll convert some of the photos & save using that profile. I assume I'd still need to designate these as Rec:2020/Full (?). And I do believe using HDR10 that all media are assumed to be Full not limited. I set to Full anyway.

Thanks. Will report back with new results.

Photos are always full range, so SRGB would be full, too.

For gamut though, if they are starting in raw they have a wider gamut than SRGB so converting from the original to Rec2020 should in theory preserve a larger color space. If they were jpegs choose AdobeRGB if you have a choice. If they are SRGB you already lost the extended colors.

Photos are always full range, so SRGB would be full, too.

For gamut though, if they are starting in raw they have a wider gamut than SRGB so converting from the original to Rec2020 should in theory preserve a larger color space. If they were jpegs choose AdobeRGB if you have a choice. If they are SRGB you already lost the extended colors.

Yes, all photos were RAW Adobe RGB. Most were reedited in DxO, saved as .psd. In Photoshop they were keep 16-bit. Some were shot in RAW with a 61mpx Sony but when Vegas crashed trying to render them I down rezed.

I will convert these to ITU-R_BT2020 space & re-render. Within Photoshop, ITU-R_BT2020 colorspace looks more contrasty.

Raw has no color space so they were not AdobeRGB. You did the raw processing in which program? DXO? What did you export them as from DXO? If you can't go directly to Bt2020 from the raw converter, export as ProPhoto 16 bit and convert to bt2020 in Photoshop. AdobeRGB is a narrower color space so no need for it here.

I'd resize all to 4K resolutions unless you plan to crop in a lot in Vegas.

Raw has no color space so they were not AdobeRGB. You did the raw processing in which program? DXO? What did you export them as from DXO? If you can't go directly to Bt2020 from the raw converter, export as ProPhoto 16 bit and convert to bt2020 in Photoshop. AdobeRGB is a narrower color space so no need for it here.

I'd resize all to 4K resolutions unless you plan to crop in a lot in Vegas.

It gets complicated, doesn't it? 😀 

I refused to pay per month for Photoshop CS but still have PS CS6. For RAWs I use DxO PhotoLab 4.3.1 which I like very much. Now that you mentioned it, you can export images as 16-bit tiff uncompressed files converted to pretty much any .icc colorspace you have on your computer. Ya learn something new everyday. Thanks!

I like to keep the photo size much larger than UHD. I do like to pan to add motion to the storytelling of a montage so with a larger than UHD image there's always a sharp image.