@thesammy58

I can feel your frustration, I have a completely different system and OS (see signature), but the 'permanent hang' issue + audio keeps playing is something we share unfortunately. I get this on average about once per hour editing, sometimes more, sometimes less, sometimes it even does not hang for hours (!).
It is a good thing you enabled the hang detection.
I do use a lot of FX, practically on every clip, especially Boris FX Continuum for color, masking, sharpen and transitions, and Mercalli V6 OFX for stabilization. Occasionally, NewblueFX and Neat Video 6 (but not recently, so these are not to blame).
I edit with legacy AVC decoding enabled as a workaround for a decoding issue with VP23.
Very recently I increased the Dynamic RAM preview max from the 5% default to 25% (I have 64 GB in total), and at first it seem to fix the issue, until I got a hang again. It does seem to decrease the hang frequency occurring, but it could just be random beginners luck fooling me, certainly not the solution, but may help a bit.
I must say the autosave is a lifesaver.
Do report here if you happen to find an offending FX which can cause the hang issue.

It's not only 3rd party FX. I get this a lot as well, and I only use the built in FX, no 3rd party stuff. I also noticed the ellipses following the frame number. When i see this, I immediately save. It usually saves ok, but not always.

If you bypass all Fx does it still happen? It would be good to narrow down the Fx that are causing an issue (assuming that's the problem).

Yes, bypassing all FX stops the issue.

BCC+ Video Glitch causes it nearly instantly. However, I don't even have to have any OFX Plugins going for it to happen either. For example, applying two VEGAS Chroma Keyers + VEGAS Flicker Control to a piece of media will cause it to happen as well. So it seems to hang after pausing when too many FX are displaying at once (only with certain combinations of FX)?

BCC+ Video Glitch freezes the program immediately if I use it in my project how it is (it seems to be very resource-intensive), but if I remove everything from the project's timeline and apply that same FX to a single piece of media with nothing else in the timeline, it runs fine.

Interestingly, if I click around a bunch of times to trigger the "not responding" dialog, the entire PC will hang for a few seconds, including the mouse and all audio from the speakers. I rarely see it get that bad. When this happens Event Viewer will show the hang type as "cross-thread".

I think I may have found a (possible) lead, but I'm not exactly sure. Setting "Enable multi-core rendering for playback" to FALSE in Vegas' internal settings stops these hangs from happening. I stress tested with an obnoxious amount of FX until the preview dipped down to 3 FPS, and no hangs. However it disables a lot of OFX (namely BCC+ ones) so this definitely is not a solution.

I think report these details via a support request and include a link to your .veg project so the VEGAS developers can test and confirm this.

I think report these details via a support request and include a link to your .veg project so the VEGAS developers can test and confirm this.

Gotcha, I have never done that before… should I just include my project + its files in a .zip? It lets you attach up to a 5mb zip file which is enough.

My only concern is they wouldn’t be able to test my issues with my specific GPU (turning off GPU acceleration in Vegas stops the freezing) or use the OFX plugins (unless that’s somehow possible in their testing), but I suppose it’s worth a shot.

Just write to support and ask if they can accept a zip. Upload to Google Drive or somewhere.

I'd assume VEGAS developers have access to Boris and other common plugins as well as a variety of GPUs. If there's an issue with an RTX 4070 Super other NVIDIA GPUs would likely be affected too.

I just noticed that the patch notes for build 203 list "Flicker Control may cause the application to hang" as a known issue... I feel silly for not seeing this before I went down this rabbit hole but I'm hoping when it's corrected it will fix other FX that hang in the exact same manner as well. I already contacted support though and will try to ask when the fix for it will come and if they expect it to correct certain other FX (namely Newblue and Borris) hanging as well, as I assume it must be an underlying issue with the OFX pipeline and not just Flicker Control itself.

I wouldn't assume it's all the same issue (though it may be). If there are issues beyond flicker control please report them.

Thanks for the suggestions. I’ll report back what info I get since it looks like others are seeing the same problem.

@bitman, @thesammy58

the 'permanent hang' issue + audio keeps playing is something we share unfortunately. I get this on average about once per hour editing, sometimes more, sometimes less, sometimes it even does not hang for hours (!).

I also have this experience every day editing (Vegas Pro 23, build 302), unfortunately.

@bitman, @thesammy58

the 'permanent hang' issue + audio keeps playing is something we share unfortunately. I get this on average about once per hour editing, sometimes more, sometimes less, sometimes it even does not hang for hours (!).

I also have this experience every day editing (Vegas Pro 23, build 302), unfortunately.

Does it only happen when you use the Flicker Control effect (like the patch notes say is a known issue) or others as well? For me it has been happening with more than just flicker control. Currently I am editing with GPU acceleration turned off and it’s dreadful but it’s my only option until this gets fixed because it’s so incredibly pervasive in my project.

@thesammy58 It happens daily in my routine of editing. It happens in many possible scenarios, for example, while the audio keeps playing or when I use color grading or just edit for more than one hour without stopping, making simple cuts or moving events. I mean basic editing stuff, not only the Flicker Control effect  or other effects. I edit with the GPU acceleration turned on. Maybe that is what is causing the issues. It is annoying, but I can live with that until a fix is released (maybe not too soon). Most of the time in my daily routine, Vegas does not freeze; what happens a lot is the cursor position freezes while the playback continues. And I also experience exactly what @bitman said.

@thesammy58 Do not focus on "flicker control" plugin, it is a known issue, brought up some time ago already in this forum. I never use it in my own projects, but I tried it once, and can confirm it was an issue when I tried it.
The freezing matter however can occur anytime, with or without OFX, and with or without stills, but it is fair to assume the chances it occurring rise with the mix of video and stills and the more OFX are added.
As I mentioned before, increasing the Dynamic RAM preview max from the 5% default to 25% (providing you have ample memory) seems to lessen the hang frequency a bit, but they still happen regardless.
But it is fair to assume there is still a bug in the Vegas coding.
Here are some common reasons (I personally suspect a race condition):

• Deadlocks: Two or more threads wait for each other to release resources.
• Race Conditions: Incorrect sequencing of events or state changes in multi-threaded apps.
• Resource Exhaustion: A full log file blocking log operations.

@thesammy58 Do not focus on "flicker control" plugin, it is a known issue, brought up some time ago already in this forum. I never use it in my own projects, but I tried it once, and can confirm it was an issue when I tried it.
The freezing matter however can occur anytime, with or without OFX, and with or without stills, but it is fair to assume the chances it occurring rise with the mix of video and stills and the more OFX are added.
As I mentioned before, increasing the Dynamic RAM preview max from the 5% default to 25% (providing you have ample memory) seems to lessen the hang frequency a bit, but they still happen regardless.
But it is fair to assume there is still a bug in the Vegas coding.
Here are some common reasons (I personally suspect a race condition):

• Deadlocks: Two or more threads wait for each other to release resources.
• Race Conditions: Incorrect sequencing of events or state changes in multi-threaded apps.
• Resource Exhaustion: A full log file blocking log operations.

Yes I definitely feel you’re on to something with the former two bullet points because disabling multi-core rendering in internal settings fixes the issue (at the cost of losing some OFX capabilities) and Windows event viewer will 90% of the time report the hang type as a cross-thread issue

So far I have yet to hear back from support but I understand it takes 2-4 days for a response and it’s the weekend. Curious to see how technical they are able to get with their guidance/insight on these issues

Interesting development... it seems Thursday's release of Nvidia studio driver 591.44 may have resolved most of the issues I've described? I updated yesterday and have yet to see VP freeze once. If another Nvidia user could report back after updating as well that would be great. Maybe I'm just having an amazing streak of luck.

@thesammy58 I have the new studio driver as well, but I can tell you the hangs are not solved with this driver. Mind you, I do have legacy AVC decoding enabled as a workaround for a decoding issue with VP23, so I am not sure this contributes extra to possible hangs. All my hangs are submitted to the Vegas team (enabled hang detection).

@thesammy58 I have the new studio driver as well, but I can tell you the hangs are not solved with this driver. Mind you, I do have legacy AVC decoding enabled as a workaround for a decoding issue with VP23, so I am not sure this contributes extra to possible hangs. All my hangs are submitted to the Vegas team (enabled hang detection).

Thank you for the follow up. Unfortunately the hangs have returned for me as well. Seems VEGAS was just having a good day when I posted that. No response from support yet.

Updated to the latest build today. I am still able to reproduce the hang even with all OFX plugins removed on this latest build. All I have to do is apply lots of VEGAS FX and pan/crop events to reproduce the hang upon pausing playback, signaling that something is going on within the VEGAS engine itself. So frustrated that this is still an issue in the new build and I can't get support to respond either.

Sorry to triple post but this HAS to be a joke… 20 days later I finally get a response from MAGIX Support telling me to update to build 356–the one that got pulled last week.

Honestly I think at this point I would have just preferred no response because this feels like insult to injury… not to mention 356 did not fix the problem I originally started this thread for.

It’s clear there are some dire communication problems happening within the support team and I feel it’s starting to reach a boiling point here because what on earth is this response after 3 weeks.

It’s clear there are some dire communication problems happening within the support team

@thesammy58 My understanding is that MAGIX Support is running mainly on AI so your request probably never got near a human.

I think reply to keep the ticket active and hopefully in front of a human when they return from holiday leave. Update to 356 is bizarre advice but you can say it didn't work anyway.