VP 21 - BUG with GTX970 - 32-bit Floating point and SHIFT+B

3POINT wrote on 4/23/2023, 2:55 PM

32-bit needs a lot of Dynamic RAM memory (which you can allocate in video preferences), avoid also setting preview on best full, try best auto.

RogerS wrote on 4/23/2023, 8:49 PM

How much memory is allocated to dynamic ram preview? More than 0Mb?

Former user wrote on 4/23/2023, 9:49 PM

At 1080P60 with DRP set to 3269MB in 8bit I get 10.5 seconds of cache, in 32bit mode I get about 2.8 seconds. So you can see that 32bit float uses more than 3x the data, and that requires 3x the bandwidth, internal bandwidth Vegas doesn't have which is why it has to default to 8bit for a more useable playback experience and render speed

pierre-k wrote on 4/24/2023, 4:51 AM

I have 64GB of Ram and I have it set to the maximum in Vegas. Yet not a second is used.

Yelandkeil wrote on 4/24/2023, 5:04 AM

I too have 64GB RAM, and set 20% for RAMpreview.
Suspect: timeline area not clarified?

wilvan wrote on 4/24/2023, 6:23 AM

My colleague , working with vegas pro (20-370 ) , told me a few weeks ago he always had to mute the video track(s) below in order to get RAM preview working properly , rather very uncomfortable and also strange since I never had to do that with all the sony versions of vegas pro and did use RAM preview non-stop in complex edits . ( one of the functions I did like the most ) Just saying , for what it may be worth .

Grazie wrote on 4/27/2023, 2:40 AM

Alternatives:

Ctrl + M - Render to a new track

Shift+M - Prerender, but do disappear when editing

or . . .

KwikPreview - From HappyOtterScripts, it's also volatile, like Shift+B, but you aren't restricted by RAM, and, if you use a suitable Encode, which I do, my GPU is utilised - mighty fast!

RogerS wrote on 4/27/2023, 5:19 AM

I tested it here on my desktop and it seems to be working (VP 20, added picture in picture made ram preview). Any other clues as to when it fails? Particular type of footage? Certain combination of tracks?

pierre-k wrote on 5/19/2023, 10:17 AM

So I figured out the cause of the problem. If you select the GTX970 card in the Video preferences, Shift+B does not work. If you choose Off or Intel UHD, it works.

With GTX970

With Intel UHD

Does anyone have a GTX970 and similar (GTX980 and higher)? Can you please try it?

jetdv wrote on 5/19/2023, 1:23 PM

@pierre-k, what video driver version are you using on the GTX970?

pierre-k wrote on 5/19/2023, 2:06 PM

Latest drivers 531. 79 games.

jetdv wrote on 5/19/2023, 2:11 PM

@pierre-k, laptop or desktop? If laptop, you may need to change:

Also, you probably want the "Studio driver" instead.

VEGASDerek wrote on 5/19/2023, 2:19 PM

I actually do have GTX-970 with the latest driver on my home computer and have just tested it without experiencing any issues. We will need to figure out where your system is different.

VEGASDerek wrote on 5/19/2023, 2:31 PM

Actually I just tried this on my laptop with a mobile 970, and I actually do see this issue.

pierre-k wrote on 5/19/2023, 2:45 PM

There are no studio drivers for Gtx970. Only games.

pierre-k wrote on 5/19/2023, 3:13 PM

Actually I just tried this on my laptop with a mobile 970, and I actually do see this issue.

Thanks for confirming that for me. I look forward to the fix. I have desktop gtx970.

pierre-k wrote on 6/20/2023, 3:07 AM

@VEGASDerek

In version VP20 411, this problem is still not solved.

RogerS wrote on 6/20/2023, 4:01 AM

Hi Pierre, I just checked with VP 20 411 and have the same issue with my GTX 1050 mobile. Studio driver 531.61.

GDI is set to compatible and that helps for the preview Fx bug but not for this.

Switch the same project and media back to 8-bit full and there's no problem- dynamic ram preview creates a selection as expected.

pierre-k wrote on 7/31/2023, 7:49 AM

@VEGASDerek

Will this bug be fixed in Vp20 or will I have to buy Vp21? Thanks for the reply.

fr0sty wrote on 7/31/2023, 2:19 PM

Your best bet is to edit your project in 8 bit mode, then if you must use 32 bit mode (and that assumes you're using 10+ bit media, otherwise it's just a waste of render time), switch it back to 32 bit mode before color grading and rendering.

pierre-k wrote on 7/31/2023, 2:45 PM

Waste of time? Are you serious? There are more of us who notice that 8-bit rendering to avc and hevc degrades the video too much. There are artifacts that are not in the 32-bit mode. And we use 8-bit sources. Read this.....

https://www.vegascreativesoftware.info/us/forum/degraded-video-rendering--141895/

I want to correct the mistake.

I don't understand that you who represent the Vegas team are giving me such advice.

vkmast wrote on 7/31/2023, 3:07 PM

@pierre-k FYI, please note that forum moderators with an "M" in their avatar's hexagon graphic are peer users and not MAGIX/VEGAS employees or members of the VEGAS team.

fr0sty wrote on 7/31/2023, 4:08 PM

Waste of time? Are you serious? There are more of us who notice that 8-bit rendering to avc and hevc degrades the video too much. There are artifacts that are not in the 32-bit mode. And we use 8-bit sources. Read this.....

https://www.vegascreativesoftware.info/us/forum/degraded-video-rendering--141895/

I want to correct the mistake.

I don't understand that you who represent the Vegas team are giving me such advice.

I digress, until I see some actual quality metric comparisons between the two.

Regardless, you claim you do your editing in 8 bit in that thread, so why do you need to drp in 32 bit? Your aging GPU can't handle it, so is there a reason you don't do it in 8 bit mode and spare yourself the headache?

I'm not saying the issue shouldn't be addressed, but if there's ways around it, why not utilize them?

pierre-k wrote on 7/31/2023, 4:21 PM

@fr0sty

Does shift+b work in 32bit mode with your rtx 3090 graphics card?