I'm not sure if it's just Vegas. NBFX Tilter Pro 7 won't work with AMD's latest and greatest driver. BorisFX Title Studio too as was posted here in the forum. It wouldn't work with Resolve Studio either. But using 22.5.1 fixed all of those problems. Ignite Pro also now works.

My Dell laptop (12th Gen Core i7-12700H) has been crashing regularly with latest Vegas build too.. very frustrating. The only way to get it stable seems to be to enable legacy AVC.

Setting decode to use Intel Iris Xe Graphic (or not), or NVIDIA GeForce RTX 3070 Ti isn't affecting stability on this one. Only enabling Legacy AVC Decoding seems to keep it running without the crashes while editing.

Also noticed when I launch Vegas it's taking a very long time before any splash screen comes up on this machine.

I have made a bug report thread for VEGAS 20 build 326, if you could please report these bugs in there following the instructions in the thread, I will make sure the developers see this. iEmby, your opening post to this thread contains most of what I asked for already, so you can copy/paste it into this thread and then add the few things it is missing for this bug report. Thank you!

https://www.vegascreativesoftware.info/us/forum/having-problems-with-vegas-20-only-users-of-v20-build-326-please--139920/

iemby, RedRob can you please share some of the media giving you trouble? dropbox or google drive... thanks! If we can get this reproduced on another system, that's one big step towards isolating the cause.

iEmby, based on what you've said, it appears it's an issue with GPU decoding. If we can reproduce that on a similar GPU in another system using some sample media, that will help us figure out why the GPU decoder is choking on that file.

 

iemby, RedRob can you please share some of the media giving you trouble? dropbox or google drive... thanks! If we can get this reproduced on another system, that's one big step towards isolating the cause.

easier said than done.. 4-camera project each w/4K 1-hour video clips. I'll try reducing/isolating the problem when I have spare time (HA?! is that a thing?!) and then get those clips uploaded.. can't upload the full files.

I have made a bug report thread for VEGAS 20 build 326, if you could please report these bugs in there following the instructions in the thread, I will make sure the developers see this. iEmby, your opening post to this thread contains most of what I asked for already, so you can copy/paste it into this thread and then add the few things it is missing for this bug report. Thank you!

https://www.vegascreativesoftware.info/us/forum/having-problems-with-vegas-20-only-users-of-v20-build-326-please--139920/

iemby, RedRob can you please share some of the media giving you trouble? dropbox or google drive... thanks! If we can get this reproduced on another system, that's one big step towards isolating the cause.

iEmby, based on what you've said, it appears it's an issue with GPU decoding. If we can reproduce that on a similar GPU in another system using some sample media, that will help us figure out why the GPU decoder is choking on that file.

I hv already raise a complaint with customer support. So just waiting there solution.

Different project same thing. On my main editing machine she leaves "use legacy AVC Decoder" checked and it's been very stable. On my finishing machine I had it unchecked, but after dealing with crashes every 5 minutes finally checked it and it's been stable and solid all day.

I don't know for sure -- our crashes frequently have been around stopping and starting playback, but that's not always the only times. Sometimes it's after saving. Sometimes after adding something to the plug-in chain. I've had a gut wondering if it has to do with File I/O actually -- like sometimes maybe background auto-save causes the crash when it seems random to us end-users. But that doesn't make sense to me how a video decode would come into play there then.

@RedRob-CandlelightProdctns

Sir you hv to keep checked on avc legacy option in File I/O menu for stability. Bcoz intel iGPU is giving problem. May be they will fix it in next update but still its a bug now.

Even customer support couldn't help me yet.