I've asked you previously is your 1050 the 2GB or 4GB version, but you didn't bother replying. RogerS has the 4GB and has no problems, so if you have the 2GB there may be no reason to expect anything is wrong, you just don't have enough Vram.

For me 1920x1080 = 3.3GB Vram on load displaying 1 frame, but 1080x1920 = 3.5GB

@Former user got much of a chip, there? I didn't respond to that question because I didn't see it. Because of that, your later LLVM comment just confused me.

It's the 2G version.

How are you tracking gpu mem usage?

Using task manager my gpu memory use never goes above 900M loading my test project that always fails.

What I mean is because you never disclosed you have the 2Gb model, there was an assumption made you had the 4GB card, and people were curious as to why your had ram errors, and there was a potential fix, but as you have 2GB model there may be no fix nor any bug to fix.

Task manager shows me that Vram usage, although I do not play the file, and only a single frame is ever viewed maybe there is background Vram caching of the video. Still not sure exactly how VP21 works

@Former user "people were curious as to why your had ram errors,"

Where did you see that I was having ram errors? I never said that and haven't had any errors that indicated a memory issue.

The problem is your 2GB of video ram. What you could do is work in 1920x1080, encode in 1080P, and alter the meta data so that players and Youtube etc will see it as portrait

@michael-harrison if you could share with me the exact project and media I'm happy to test on the 4GB.

I've seen red screen errors on 2GB cards before and VEGAS doesn't recommend below 4.

@RogerS https://drive.google.com/file/d/1T5zQ8c47M-sGBxuGW5YjE_nSlsfKG1wv/view?usp=sharing

Just for the record I have used both Studio and Game drivers with no issues with many versions of Vegas. But it makes sense to use the Studio version if you do not play games or games are not your priority. The Studio version also works with games (unless the game needs a specific updated driver). Also we have seen many issues with cards with less than 4GB of RAM on this forum.

Thanks Michael. I had an uneventful test here- played back at preview full and then best/full with no issue and then completed a 9:16 1080p NVENC render with no red screen.

@andyrpsmith yeah, though I've yet to run into anything with stock VP that really taxes my 1050. I'm not using a ton of fx or the newer AI plugins with any regularity. My working test project only uses 500M vram in horizontal aspect with pip working and the vertical project is using 600M before pip is added.

It may well be that VP is attempting to allocate > 1.5G just for pip but I don't see signs of that in a horizontal project.

Even a test with a 3840x2160 project with the preview at Best (Full) VP is only using 700M of vram before pip.

As a long-time developer, including low-level coding for Nvidia gpus, I'd suspect a bug in the way pip is allocating vram. Probably for a temp buffer. Unfortunately I don't have the dev tools (or room for them) on this laptop and can't dig deeper on my own.

Probably best to wait until the VP devs have a chance to take a look.

RE. gaming, yeah, I don't do much gaming these days so I've stuck with studio drivers for the last couple of years.

@RogerS thanks. I assume you were on the XPS 15? All things being equal that would tend to point to a potential vram issue. Given what I'm seeing with my latest testing I would suspect a temp buffer(s) > 1.5G being allocated and that failure puts VP into a permanent failure mode. It's interesting that once the failure happens, VP just keeps popping up the gpu failure box even after starting a new project. I initially thought I needed to reboot but a simple restart of VP gets things working reliably again.

@VEGASDerek As I was writing this reply I just ran into an important variable. The preview resolution.

If I run in Draft (Auto) I get the GPU error the first time, every single time with 21-187. If I change to Best (Full) I can add pip all day long (probably) without an error.

While writing *that* I created a project with 11 pip tracks and no error. Doubled it to 22 and still no error in Best (Full).

Ran through all the preview modes and I can run pip on everything except Draft (Auto) and Draft (Quarter). Those it consistently dies in.

To clarify all my testing here is with my XPS 15 with 4GB GTX 1050.

At the draft quality setting it doesn't playback and then locks up VEGAS. No red screen but still a failure of some sort. GPU doesn't seem to be doing much with nearly no ram usage. No error report box. I triggered it 3 times in a row.

@michael-harrison @RogerS I've been playing with a 1000x1900 clip quite a lot of tonight (I know it's not 1080x1920) PinP added, Good (Full), I even added several effects, borders, black bar fill etc, just to see my RAM/VRAM's reaction, no problems. just seen your msg reg Draft (Auto - Full)

Loaded the clip again, just with PinP & switched to Draft (Auto) instant red screen, I can't use any preview option now

Closed project - new project - I can't add media without that pop-up showing.

Had to restart Vegas.

------------------

PS. I added a UHD .mov ProRes, changed the project to 2160x3840 Portrait, changed the clip to Match Output with Pan/Crop, added another clip, added PinP to that clip, Good (Full) everything was fine, switched to Draft (Auto) instant msg & red screen.

Looks to be related to resolution and PIP, rather then quality of preview and selecting quarter/half/full. If I used a lower resolution video it would perhaps error on BEST/FULL

@Former user "perhaps" or "does?"

I don't see any difference in behavior with either lower-res video or a lower-res project. Changed both to 1080x1920 from 4k and every playback resolution that worked before still works and those that failed, still fail.

@Former user  Hmmm, maybe but I just tried a 576x324 clip with all Preview options, no problem. it was 16:9 tho

Second go, I changed that clip to portrait 324x576, PinP added, as soon as Good (full) was changed to (Half) I got the red screen. so maybe a combination of Resolution & aspect.

Changed the project to 1080 x 1080, Good (Full=Auto) no prob, Draft (Auto) crash.

Ok, 2160x2160, Good (Full) no prob, switch to Draft = crash, so Aspect + Preview option the problem?

@Former user you may have found a possibly related but new bug.

I've never had any problem with any combination of aspect and preview. It was only after I added PIP that the error started on my machine

@michael-harrison @Former user @Former user @RogerS @andyrpsmith

Try a project with 3840 x 3840 resolution. It seems any resolution less than 3840 will cause a red screen and crash. I tried 3839 x 3839 and it crashed, but not 3840 x 3840.

@Robert Johnston Yep, 3840x3840 worked with all preview options 👍

Because that was sq 1:1 I thought I'd try an odd shape, this clip of the back of my van is an 8K 7680x4320 clip, I rendered it out at an 'odd' 5000x4320, Good (Full) was fine but Good (Quarter) crashed it. 🤷‍♂️

Thanks, I tried the same charlie2 project with a 3840x3840 and it didn't crash. At 3838 and draft (auto) I got an immediate crash.

I crash if width = 4098 or more (especially on preview full). I can do 4097 x 7000 okay. 4098 x 4097 crash. 4097 x 4098 okay.