Previously discussed here and here.

Why do you want to delete events while they are playing?

cause time is money and....

i mean really, it's no wonder so much of what i see looks badly cut if this is the way they're doing it.

i don't mean any offense to the op. but whoever thinks this is the way to edit is in the wrong profession.

I've only been editing for 20 years... Just because I'm faster at it than you are does not mean I am in the wrong profession or that my work doesn't look good... it just means I know what I want, and if I see a clip I do not want while it is playing (often while reviewing edits I already made), I don't expect my $800 editing app (I bought the suite) to crash when I press the delete key, or if I press ctrl+x to cut to to my clipboard for later use down the line.

When you are editing video set to the beat of music, like a festival recap (what I specialize in), each scene is equal or a division/multiple of the length of the clips around it (as they are all cut to the beat), so all of the clips are easily interchangeable. Once you get the clips laid out on the timeline, deleting one is easy with auto ripple on, as it pulls the rest in sync with the beat again. Sometimes I realize that one scene works better in another spot, so I will cut it to the clipboard. I do all of this while the video is playing while reviewing my initial edit. Nothing lazy or sloppy about it, just efficient.

This bug has been present in some form for years, I'd say at least since vegas 11/12. Nothing worse than making a ton of progress on a project very quickly, pressing delete, seeing Vegas freeze and the audio keep playing, and praying it eventually snaps out of it (sometimes it doesn't). Then, when it does crash, realizing auto-save still put you back a good 20-30 minutes worth of work. That is another thing I would love to be able to do, adjust the auto-save frequency. It sometimes seems to have a mind of its own, and sometimes saves 5 minutes before, sometimes it seems like much longer. If there is a way to adjust this, can anyone point it out to me please?

Autosave interval appears to be influenced by "Internal" setting msAutoSaveInterval as shown:

300,000 ms would be 300 seconds / 60 = 5 minutes

I've never changed the setting.

I've had msAutoSaveInterval set at 60,000 (1 minute) for a few years. But it can interrupt things sometimes, like when I'm in the middle of typing a subtitle into a region name (although it might be the Vegasaur autosave that is doing the interrupting). I just wonder if it might also interrupt fr0sty's cut-to-the-beat workflow when it happens.

Always kept Auto save interval at 150000 since VP10.
Never noticed it "invading"/interrupting some other processes... 🕵

Thanks, folks!

Always kept Auto save interval at 150000 since VP10.
Never noticed it "invading"/interrupting some other processes... 🕵

I think it's probably my Vegasaur Autosaves doing it, rather than Vegas' own saves. I could test this by adjusting the interval of each of those in turn to be very short and then continuously typing into a region name until I get interrupted, or not.

I have a similar problem to Nick. I'm trying to edit a Boris Title and Vegas is auto-saving the project. At 33% the auto-save fails, and it's not possible to return from Boris to the Vegas timeline.. have to kill the whole process. :(

Any tips on this? It looks like it's not a Vegasaur autosave because (a) the filename is not timestamped and (b) the file left behind have .veg.tmp extension (and the original .VEG file has been deleted?!

I still get this -- not necessarily with Boris. Today I had Neat Video ("Reduce Noise v4") open when it tried to auto-save.. same thing.. 13%, stops.. freezes Vegas. Seems to be whenever a non-native Vegas window is open (OFX effects only maybe?), and auto-save kicks in, Vegas 14 hangs.

Anyone else experience this, and know if it's something that's address in VP16?

@RedRob-CandlelightProdctns In VP16 there is the new Advanced Save Utility, accessed from the Tools menu, which I guess *might* help with this issue. I haven't tried it yet and I don't see any documented help for it. The tooltip for "Use Advanced Backup" reads "Check to use the advanced backup feature. Uncheck to use legacy autosave." And there is a choice of save location.

@RedRob-CandlelightProdctns

Use the latest Vegasaur version (currently 3.4.2), with a few bug fixes

Latest Vegasaur installed -- I don't know that it's a Vegasaur bug or Vegas. This is so frustrating!!

It seems whenever a modal window is open and auto-save kicks in, it stops at 33% and I'm stuck. I can move the top window around still, but the app is otherwise unresponsive, ultimately leading me to kill the Vegas process. Fortunately, it leaves behind the actually auto-saved file with a .VEG.TMP file extension, and a simple rename yields no data loss, just the PIA of having to restart... again.

Grrr... anyone else experiencing this still? Fixed in VP16? Or environmental and I'll still have the problem?

Anything unusual about the drive you are auto-saving to?

Why do you want to delete events while they are playing?

Isn’t that kind of irrelevant when discussing a bug?