I think you need to work with VEGAS Pro 21.208 or older for this footage and Fx until 22 is fixed.

I don't have Vegas 21 anymore. Vegas 21 did not work with other older projects, hdv. Red preview and crashing rendering after several minutes.

I am sticking with only option now. Editing with gpu enable on file IO tab and disable it for render.

VP 20 and 21.208 and older had issues with a red preview?

VP 20 and 21.208 and older had issues with a red preview?

Vp 21 had red preview after one time editing for hdv files, always, gpu on or off, nothing worked and was not able to render them, stopt with red preview and out of memory. 40 gb available, strange. I was busy with older material at that moment. Helpdesk was not a help at all. Only solution was, reinstall and then there came no solution anymore.

Gone back to vp20. Which worked correctly. Vp 22 workes correctly too. But not tested rendering hdv yet.

Never tested vp21 for this footage, uhd files. So no idea if vp21 worked or not.

vp20 had black frames (the same as vp22 with legacy drivers), but there I disabled the gpu on file IO tab and this was no problem for preview. Same fps there on or off. Vp22 is can not preview without gpu turned on. Stuttering, even on lowest setting. Also vp 20 had problem with odd frames which where not black, but had strange effects in preview. The same frame in rendered file had this also. Moving clips and moving fx or copying to new project could solve it.

To be honest, It has never, same with computer before with other geforce card, been possible to work with gpu accelerated. (Vp13 (only tested hdv) and 19 same problems (hdv and uhd)).

Testing vp22, before buying, it looked like the first version where gpu worked, sadly no.

But turning the gpu off had never so much inpact on fps preview.

Are you sure 21 with HDV issues was 21.208 or the final releases of it? 21 was mostly a refinement of 20 until build 300 (which is like an early release of 22).

It sounds like no version actually worked properly with all of your footage so hopefully the files you provided will help make 22 the first version to work without compromise.

To be honest, It has never, same with computer before with other geforce card, been possible to work with gpu accelerated. (Vp13 (only tested hdv) and 19 same problems (hdv and uhd)).

Testing vp22, before buying, it looked like the first version where gpu worked, sadly no

I work only with GPU acceleration enabled - and it works fine for my footage. I think one cannot state that so general as you did here.

To be honest, It has never, same with computer before with other geforce card, been possible to work with gpu accelerated. (Vp13 (only tested hdv) and 19 same problems (hdv and uhd)).

Testing vp22, before buying, it looked like the first version where gpu worked, sadly no

I work only with GPU acceleration enabled - and it works fine for my footage. I think one cannot state that so general as you did here.

I think I had no luck in combination with the type of footage i have (Sony fx 7 hdv and jvc hme170 uhd). For me it never worked, I have always had problems with preview or render or both. Vp 20 I set dynamic ram to zero, was only solution in combination with turning of gpu that worked. Then I got no black frames in preview.

And I start always with default settings. Only if problems arrive, I start to change settings. Which for me have been always the case.

Also I had to render with mainconcept for vp20 (magix HEVC/AAC, tv does not recognize AVC/AAC for testing). With nvenc much faster, but got parts of clips before in next and lots off other errors with higher bitrate. I have not tried the nvenc yet in vp22.

Try setting the number of threads to 1 in the Preferences/Video tab and reopen Vegas. This helped me in the past when I was getting errors and black frames in my video while rendering.

Try setting the number of threads to 1 in the Preferences/Video tab and reopen Vegas. This helped me in the past when I was getting errors and black frames in my video while rendering.

I will try that. No, still green frames in render and preview.

Open C:\Programmi\VEGAS\VEGAS Pro 22.0\FileIO Plug-Ins

and rename mxcompoundplug folder:

Well, it would be nice if this bug (which has been going on for over 10 years) was fixed once and for all by the developers.

No need to hide MxCompound plug (which is new, as of this spring, by the way). Just check enable legacy AVC or experimental HEVC in preferences, file io to avoid it for AVC and HEVC media.

No need to hide MxCompound plug (which is new, as of this spring, by the way). Just check enable legacy AVC or experimental HEVC in preferences, file io to avoid it for AVC and HEVC media.

Agree. This disables mcompoundplug and enables so4compoundplug. But that is no solution for this media. As stated before. We will see what testing with the media results in.

Well, I have used my laptop with your project (specs in my signiture), but have NOT enablede the legacy AVC decoder. I see no reason for that, frankly spoken.

But I have used your project, and have applied the CGP to the timeline (without any correction). So I added more stress to the project. And with that change I see a green decoding error - reproduceable at frame 525.

Here the project file with the CGP applied, and a marker where I see the green error:

https://drive.google.com/file/d/13TN--Vp0fgXdBEAhZQxJxa6enGqWSKZr/view?usp=sharing

@Wolfgang S. I tried your version, but did not see any green or black frames. In fact on my own videos with VP22, I do not recall getting black and green frames. Do not get me wrong, I do believe the issue is real though, but hard to reproduce. And I get a subjective vibe that @Former user is on the right track:

Most likely a problem with transparent caching. If you look at my screen recording showing difference between DRP on and off, when it's turned on the VRAM fills with video data and is used instead of reading original files. That cache data is lost or not able to be read sometimes with transitions as you've said the problem goes away with turning DRP off.

https://www.vegascreativesoftware.info/us/forum/vegas-pro-22-build-194-general-discussion--147635/?page=2#ca928174

Maybe because I have 24 GB of VRAM available with my RTX 3090, the issue has lesser chance to happen on my system.

I must also add I have resizable bar and Above 4G Decoding enabled in BIOS, which is a somewhat "dark horse" feature which is found in modern motherboards that allows the system to access more than 4GB of memory space per PCI Express device. Setting this may also help if it is a caching issue...

Hi, I sometimes get green frames in transitions but they always go away with the first play or even just scrubbing through looking for them I find they're gone nowhere to be found & impossible to reproduce 🤷‍♂️,

When this topic is mentioned I try the suggested actions or media shared to see if I can get green frames & it's always no, I can't get green frames. Same goes for this project, I can't get green frames with either project shared.

So this comment by @bitman is always my thought & it's a bit fruitless to continue trying -

Maybe because I have 24 GB of VRAM available with my RTX 3090, the issue has lesser chance to happen on my system.

I set above 4g decoding to enabled and resizable bar to auto. No difference. Opening project with problem and seeing several green frames in problem part.