Has VP21 become less stable s/Radeon 470 & Intel graphics, and in gen?

RedRob-CandlelightProdctns wrote on 5/19/2024, 3:33 PM

I can't figure out why, but I haven't been able to get through any of my recent finishing edits without constant crashes.. it's really killing productivity.

I tried turning off "dynamic RAM preview" (set to 0) -- still crashed when stopping/starting playback
Tried turning on "Use Legacy File I/O"
Tried turning off video card in File I/O and in Video tab (usually use Intel for File I/O decoding, and the RX470 on the Video tab)

I'm working with a single master video track (post-MC), no effects on the video events or media. Media is mostly 1080p30 AVC from Canon G70's (29.97fps). One cam is 4K AVC from the G70. One cam (Osmo Action) is 1080p60 AVC. One cam (OBSBOT Tail Air) is 1080p30 (actually 30fps, not 29.97). The OBSBOT is a newcomer to the mix; although it *is* in my multi-take clips, it's not the active clip anywhere near where I'm editing right now.

A few audio tracks have Vegas Reverb added to them, but no other processing.

I'm using two audio buses to boost volume on one track and adjust volume on a group of audio tracks together.

Really -- I just can't get it stable..

Anyone else having more frequent crashes lately?

Comments

RedRob-CandlelightProdctns wrote on 5/19/2024, 3:38 PM

I sometimes think it has to do with auto-save, but I really don't want to disable Advance Auto Save since it's saved my bacon many times now (and who doesn't like bacon, right?!)

Like just now -- and this is common:

1. Ctrl-S to save

2. I hit "enter" to play the timeline

3. I notice the scrubber isn't moving on the timeline and try hitting "enter" to stop. Vegas is not responding -- can't stop. Video Preview isn't updating. But I keep hearing the audio playing.

4. I kill the process.

J-Toresen wrote on 5/19/2024, 4:08 PM

If you have a problem with auto save, it is simple to resolve it. I always start with a project file like this:

V21B300-project name-10

Then, when I want to back up the project, I create new versions:

V21B300-project name-11

V21B300-project name-12 ...

V21B300-project name-66 …

It works for me. But of course, I must Save as and type in a new number.

Jøran Toresen

Gid wrote on 5/19/2024, 4:09 PM

@RedRob-CandlelightProdctns Hi, yeah sorry I can't offer any advice 😁, in other posts some people are reverting back to the (300) build & others resolve their AVC issue with that or turning on Legacy AVC,

For me (300) & (314) have been the best yet, next to no crashes, & I'm really not an audio person, I rarely stray beyond the volume button, but recently I have been playing with a few audio fxs trying to reduce the noise of my woodworking machines on an 18min UHD project consisting of multiple clips cut up into 60+ events, not having a clue what I was doing I was moving sliders while the project was playing, swapping out fxs without a single crash if I remember correctly.

But my PC is Nvidia GPU with AMD CPU with no integrated graphics & my media was/is HEVC 🤷‍♂️

RedRob-CandlelightProdctns wrote on 5/19/2024, 7:44 PM

If you have a problem with auto save, it is simple to resolve it. I always start with a project file like this:

V21B300-project name-10

Then, when I want to back up the project, I create new versions:

V21B300-project name-11

V21B300-project name-12 ...

V21B300-project name-66 …

It works for me. But of course, I must Save as and type in a new number.

Jøran Toresen

Oh -- I'm very well versed in frequent saves and have my naming system down. The crash seems to follow *any* save followed by starting and/or stopping playback, not just auto-save. And that's just a hunch.. not really a scientific method of saying what the root cause is. :(

RogerS wrote on 5/20/2024, 4:44 AM

There are major bugs with Radeon decoding in VP 21.314 though setting hardware decoding to none or enabling legacy /experimental decoders should avoid them. Otherwise go back to 300 or wait for a patch?

RedRob-CandlelightProdctns wrote on 5/20/2024, 1:45 PM

There are major bugs with Radeon decoding in VP 21.314 though setting hardware decoding to none or enabling legacy /experimental decoders should avoid them. Otherwise go back to 300 or wait for a patch?

Unfortunately, I don't think it'll let me open the .314 project now in any older version (they usually don't allow old versions to open newer files) so that's not really a great option on my active project.

Dynamic RAM set to 0
Disabled Radeon support on the Video screen (no video card used there)
Intel card used to decode on File I/O
Use Legacy Encoder is checked. Experimental HEVC is not checked

Seemed slightly better but just crashed again.. what joy.

RedRob-CandlelightProdctns wrote on 5/20/2024, 4:50 PM

Update: Still crashing, but *appears* to be significantly better after disabling advanced auto-save.

I'm also trying to slow down after saving (count to 5) or stopping/starting playback. I opened another thread about an observation on the Audio Bus with track Reverb applied... may be related.

Resoula wrote on 5/20/2024, 6:17 PM

There are major bugs with Radeon decoding in VP 21.314 though setting hardware decoding to none or enabling legacy /experimental decoders should avoid them. Otherwise go back to 300 or wait for a patch?

Wow. Thank you for posting this. I just tried these options. Build 300 and newer have been essentially unusable on my 5700XT. With the legacy decode AVC actually works again, and with the experimental decode HEVC no longer freezes my PC every time I interact with anything.

Edit: This has also completely solved a memory leak I had on HEVC where Vegas would consume 10-20MBs more of RAM every single second until I ran out of the stuff. Super helpful man. Thanks so much.

Edit2: This also solved a bug where closing one project with media would stop a second already-opened project with media from detecting the media that was shared. Incredible.

RedRob-CandlelightProdctns wrote on 5/20/2024, 6:21 PM

There are major bugs with Radeon decoding in VP 21.314 though setting hardware decoding to none or enabling legacy /experimental decoders should avoid them. Otherwise go back to 300 or wait for a patch?

Wow. Thank you for posting this. I just tried these options. Build 300 and newer have been essentially unusable on my 5700XT. With the legacy decode AVC actually works again, and with the experimental decode HEVC no longer freezes my PC every time I interact with anything.

This community helps each other. It's what we do. :-)

RogerS wrote on 5/20/2024, 7:30 PM

300 can open files made in 314. In general you can't open projects in an older version number (20 can't open 21 projects) but can within the same version; exception being VP 21.208 to 21.300 which is like a new version of VEGAS.

RedRob-CandlelightProdctns wrote on 5/20/2024, 7:39 PM

300 can open files made in 314. In general you can't open projects in an older version number (20 can't open 21 projects) but can within the same version; exception being VP 21.208 to 21.300 which is like a new version of VEGAS.

I think that's generally referred to as major versions and minor versions.

Since when I upgraded from 21.300 to 21.314 it warned "you're opening with a newer version and won't be able to go back" I sorta' assumed it meant it 😉

Went from 300 to 314 hoping it'd fix my frequent crashes lately.. seems like turning off advanced auto-save has helped somewhat as well as (maybe) using the Radeon less. ... not ideal in any way, but I need to get my work done!

RogerS wrote on 5/20/2024, 7:45 PM

314 introduced new crashes for Radeon GPUs. Hopefully that will be fixed soon.

Having a new "major" version within the same major version of VEGAS is a first in my recollection.

RedRob-CandlelightProdctns wrote on 5/20/2024, 9:03 PM

300 can open files made in 314. In general you can't open projects in an older version number (20 can't open 21 projects) but can within the same version; exception being VP 21.208 to 21.300 which is like a new version of VEGAS.

Welp, uninstalled 314 and installed 300. Locked again after pressing "Enter" to play after a save. I have back-to-back projects to edit -- this is becoming unbearable.... I'm going to disable my audio plugins (Reverb mostly on two tracks) to see if it makes any difference next.