Split + Delete (While Playing) Causing Huge Hangs

Phil_P wrote on 7/23/2020, 4:06 AM

Hi all,

Windows 10 here Vegas 17. Vegas user since the early Sony days.

I just wanted to see if any one has any ideas what may be causing this one. I have had this issue for a long time and not posted about it.

Using a basic, simple video project with one audio track and one linked video track. I will go through it and trim the "errrs" and "eerrrms" and other gaps. Using ripple so that when I remove a part it joins the gaps. Basic stuff right?

I use the "s" key to split then let the video play then "s" again then highlight the resulting section and hit "delete".

I have been having huge issues with this. Vegas just locks up after some time, exactly when I hit delete, (while transport is playing). The audio continues to play in the background...

Only today I discovered that it is in fact a lockup and not a complete crash. I walked away for a while and came back about 5 minutes later Vegas is OK again.

My machine is maintained meticulously as I run a recording studio. I do not have any issues with any other software.

So in a nutshell:

*
Ripple On
Split [
Split ]
Delete [] (While in still play mode)
*
Repeat*
After some time Vegas locks up (audio continues) - it is not responding in Task Manager
After 3-5 minutes Vegas comes back to life.

Any ideas or suggestion will be highly appreciated.

Thank in advance.

Back to post

Comments

Phil_P wrote on 1/25/2021, 5:16 AM

Also try reducing thumbnails to just "head/tail" or turning them off.

Hehe thanks fr0sty, still battling away.

Even turning thumbnails to show every millennium doesn't make any difference to this issue.

pete-g wrote on 2/1/2021, 2:15 PM

Also try reducing thumbnails to just "head/tail" or turning them off.

Hi fr0sty thanks for the tip. I turned thumbnails off, and I think this appears to have lowered the frequency - but it hasn't fixed it entirely.

I was editing a project all day today and it hung once. Normally it would hang several times.

A step in the right direction all the same! Will keep an eye out for future updates and on this thread too.

Keep fighting the good fight Phil_P and cheers for starting this thread and getting the ball rolling ✌️

I will be so happy when this finally gets solved.

Phil_P wrote on 2/1/2021, 10:31 PM

I’m always very grateful for any help or suggestions with an issue.

In this case though, the thumbnail thing had no noticeable effect for me at all.

As mentioned, being a QA tester myself, I do tend to try plenty of obvious options before posting and asking for help

In fact I’m finding that nothing helps this. Certainly some videos seem to be affected worse than others but so far there is no pattern to that.

The only thing I’ve found that helps is turning auto ripple off. Which of course defeats the object completely.

fr0sty wrote on 2/1/2021, 11:26 PM

This is a VERY old bug in VEGAS... as in, it's been around as long as I can remember, and I've been with it since 2003. I couldn't even count the thousands of crashes I've had over those past 18 years because of this exact thing... but I can say that it rarely ever happens to me these days. They've made great improvements to that stability, but the issue is still there somewhat.

Phil_P wrote on 2/1/2021, 11:33 PM

Please note: Just because I decided to post about it last year, does not mean that that was when I first had the issue.

However, it was never as bad in the very early days.

Also awareness is important. So, an issue was discovered years ago? That does not mean that one should not post about it now.

I searched heavily for solutions before posting. There are none. There are still none.

And there are still people adding to this thread which really means it is still a valid issue.

Saying it’s has got better does not help at all, it has verifiably not got any better for many of us. Sorry.

Cheers. P.

relaxvideo wrote on 2/2/2021, 8:39 AM

I still use V11 :) :)

pierre-k wrote on 6/16/2021, 3:33 AM

This bug is still not fixed. Since version 12 -18

Phil_P wrote on 6/16/2021, 3:44 AM

This bug is still not fixed. Since version 12 -18

Yup. We live in hope. :-) It must be something very tricky for the devs to deal with I guess. I am now using alternative methods for my workflow. Shame but had to be done.

walter-i. wrote on 6/17/2021, 3:52 PM

I am now using alternative methods for my workflow.

Maybe it would be helpful for others if you would present your method here?

The forum lives mainly from mutual help - and not from mutual regret.

Illusion wrote on 6/18/2021, 6:17 AM

.... Shame but had to be done.

By the use of those words, my guess is the alternative is a different NLE.

Phil_P wrote on 6/18/2021, 7:29 AM

I am now using alternative methods for my workflow.

Maybe it would be helpful for others if you would present your method here?

The forum lives mainly from mutual help - and not from mutual regret.

Hi guys, sorry for the small amount of info. Got a bit distracted with the birth of my granddaughter.

However there is absolutely no need for snarky comments like that. Please remember that you don't always know everyone's situation - what they are doing and how much spare time they may have at the time. And in fact I was trying to be polite by adding a quick reply and also positive and not complaining by stating that it must be a tough one for the devs. I also had every intention of posting more fully detailed explanation as soon as possible (as I always do).

"Alternative methods", merely meant that I am disabling auto ripple when doing these kind of edits. So the procedure is basically no auto ripple. Cut the audio or video. Group and move everything across manually. I have set up some hotkeys and a macro to assist but it is very basic stuff. Also using Happy Otters Tools (best purchase of the year tbh), to make super lightweight proxies makes everything much easier to deal with.

I did first post about this issue almost a year ago. So you would kind of expect that since then I have been trying alternative workflows. None of which are ideal in all honesty.

Also @Illusion you were right I did briefly consider moving away but I have too much invested in Vegas to do that. And I do really love Vegas at the end of the day.

My best, P.

Illusion wrote on 6/18/2021, 7:34 AM

Also @Illusion you were right I did briefly consider moving away but I have too much invested in Vegas to do that. And I do really love Vegas at the end of the day.

My best, P.

Congrats!

I am happy to hear that, I feel in the same situation as you. I am so fluent using Vegas that any edit is just a breeze, no matter the complexity.

pierre-k wrote on 8/21/2021, 5:15 AM

even in version 19, this bug is not fixed. I still stay with v17.

pierre-k wrote on 2/8/2022, 9:06 AM

even in version 19 update 3, this bug is not fixed.

pierre-k wrote on 2/8/2022, 9:10 AM

If I count correctly, this bug is celebrating its 15th anniversary.

Shame.

pierre-k wrote on 2/8/2022, 9:26 AM

Can anyone please check if this bug also affects editing on SSD disks?

Former user wrote on 2/8/2022, 10:23 AM

Is this topic still about about Split + Delete (While Playing) Causing Huge Hangs?

'Ripple On

Split [

Split ]

Delete [] (While in still play mode)'

Twice today i've put 2hrs of 4k on the timeline, S [ S ] delete whilst playing, deleted 30+ bits, couldn't get it to crash whatever i did

pierre-k wrote on 2/8/2022, 11:14 AM

Twice today i've put 2hrs of 4k on the timeline, S [ S ] delete whilst playing, deleted 30+ bits, couldn't get it to crash whatever i did

Yes. You're a lucky man. But it is not possible to make a conclusion after a short test.

RogerS wrote on 2/8/2022, 9:00 PM

If you want to make this scientific would you like to provide a sample project and media to test?

pierre-k wrote on 2/8/2022, 10:44 PM

If you want to make this scientific would you like to provide a sample project and media to test?

You can trigger this bug with events from the media generator. It doesn't matter what video format you use.

RogerS wrote on 2/8/2022, 10:56 PM

Okay, then please create a sample project using the media generator and describe how to trigger the bug if you want others to do identical tests and validate your result.

pierre-k wrote on 2/8/2022, 11:01 PM

Okay, then please create a sample project using the media generator and describe how to trigger the bug if you want others to do identical tests and validate your result.

Read the whole discussion.

Former user wrote on 2/9/2022, 12:32 AM

Read the whole discussion.

@pierre-k Read the whole discussion,

very little mention of what hardware used, the majority haven't filled in their Signature

Many different scenarios shown so it's impossible to accurately reproduce what's been posted here, a few mentions of 'I can reproduce this in 30secs using Empty events or Media Generator files' - Not me, my PC has been on 36hrs, i've tried this over 10 times using different formats (inc empty events as mentioned near the start of this thread), different timescales & amounts of tracks, i still haven't reproduced this, I know that i have a fairly powerful PC but if this is a Vegas bug the power of my PC wouldn't make much difference, the bug would arise & no amount of power would push through that.

Phil_P wrote on 2/9/2022, 12:55 AM

If this is not happening for you great. How long your PC has been "on" is irrelevant. Trying it 10 times is also irrelevant. Sometimes it takes 50 tries, sometimes it happens on the first try.

There is no need to supply a project. Just use whatever project you have handy, even that is not required, blank empty media will do, and repeat the steps in first post as fast as you can. Also sometimes with no preview it will go longer without freezing. (All this is mentioned in the thread).

Unfortunately some issues are not repeatable by every single person, every single time. One key to the repro is to do it fast, follow the steps in my first post, fast, as if you are editing with a deadline.

It has been confirmed by a large number of users in this very thread, even some who were initially sceptical, and It was confirmed by someone at Vegas too iirc. Please read the thread if you are interested.

This is being looked into, and is listed in our issue tracker.

There is really no need to keep resurrecting this thread to argue about it or deny that it happens. There is tons of info here and tons of confirmations from other users.

I totally understand that reading the whole thread is chore but in that case you are missing vital info from other contributors.

I also understand that the developers might not make this a priority, I am sure they have lots of other issues to deal with and they will have their reasons that we don't all necessarily know about.

My best, P.

1 … 5 6 7 8

of 8