Bug: Commit, Freeze Crashes Constantly 2024.6

[Dizzi45Z]

I am so excited for all of these new features, but unfortunately, I have had so many crashes every time I try to commit or freeze faster than real time on all types of audio and instrument tracks. Typically it goes through the process of looking like it is rendering and once it gets to the end of the rendering process, it hangs for a second and crashes.

I have noticed this happens with multiple virtual instruments including Omnisphere, Superior Drummer, Komplete Kontrol, etc. In fact, I don't know that any of my Virtual Instruments that are not crashing after I try to commit or freeze. This includes Committing or freezing the whole track, up to a certain insert, dragging the MIDI to an Audio Track. It doesn't seem to matter if you have the track "do nothing" or "hide" after the commit.

I'm also getting crashes trying to commit or freeze any audio tracks in my sessions even if they have no plugins on the track.

Some people in the thread "PT2024.6 | Issues, Bugs and Observations" have mentioned that Omnisphere could be a culprit regardless whether you are committing or freezing an Omnisphere track. I do use a lot of Omnisphere in my sessions, so it's a possibility.

I have sent tons of Crash reports to Avid and I have one I can send to anyone that happened from just trying to commit an Audio track with no plugins on it.

I'm on an Intel Mac Pro 3.2 GHz 16 Core Intel Xeon W with 160 GB of Ram on Ventura 13.6.7

If anyone else is having this problem, please chime in with any findings or possible work arounds.

I did have one session where committing by choosing to commit the selection over the track seemed to work for a short time. I'm still hoping to find a work around.

[Dizzi45Z]

I also should add that these crashes were not an issue in 2024.3.1 or earlier versions for me.

[Darryl Ramm]

Originally Posted by Dizzi45Z

I also should add that these crashes were not an issue in 2024.3.1 or earlier versions for me.

Lots of things changing in Pro Tools plugin land recently and causing instability for multiple users. (While looking at stuff you should also check all your plugins are up to date. PT Prefs 2 plugin report can help there, and anything badly out of date goes to the top of my list as a suspect plugin to test remove/replace).

[ajp99]

Having this issue as well. Doesn't seem to be plugin specific. Some tracks with the same plugin chain will commit perfectly fine, while others while crash at the end. Really frustrating.

[Actionmusic]

I've seen some crashes/hangs with (suspected or mentioned in crash report) Little Alterboy (using automation) , Trillian, Omnisphere (automation may be a factor in this as well fyi), VPS Avenger, Shaperbox 3.5.2 , Kontakt 7. The reproducible ones I've sent to support. As mentioned in other posts, there is a good possibility other track plugins in the session and NOT the plugin track you are trying to bounce are at fault.

My troubleshooting was to inactive half the tracks at a time, repeat, until I narrowed down the problematic plugins. in my example, Kontakt was hanging commit, but only by Ominsphere being inactive would it commit as expected. So which is at fault ?

Similarly had a Trilian commit problem but this time it actually was the Trillian at fault.

Just flagging for general information

[tope d]

Hi!

There are a few known issues with third party plugins, but let me check further on this and get back to you.

Thanks

[marianna]

Originally Posted by Actionmusic

I've seen some crashes/hangs with (suspected or mentioned in crash report) Little Alterboy (using automation) , Trillian, Omnisphere (automation may be a factor in this as well fyi), VPS Avenger, Shaperbox 3.5.2 , Kontakt 7. The reproducible ones I've sent to support. As mentioned in other posts, there is a good possibility other track plugins in the session and NOT the plugin track you are trying to bounce are at fault.

My troubleshooting was to inactive half the tracks at a time, repeat, until I narrowed down the problematic plugins. in my example, Kontakt was hanging commit, but only by Ominsphere being inactive would it commit as expected. So which is at fault ?

Similarly had a Trilian commit problem but this time it actually was the Trillian at fault.

Just flagging for general information

Hi there Actionmusic....

I didnt see a case for you on this with support...... " The reproducible ones I've sent to support." did you have a case going and if so what was the case # so I can tie these together so we can figure out what is causing this.

Marianna

[Darryl Ramm]

Originally Posted by Actionmusic

I've seen some crashes/hangs with (suspected or mentioned in crash report) Little Alterboy (using automation) , Trillian, Omnisphere (automation may be a factor in this as well fyi), VPS Avenger, Shaperbox 3.5.2 , Kontakt 7. The reproducible ones I've sent to support. As mentioned in other posts, there is a good possibility other track plugins in the session and NOT the plugin track you are trying to bounce are at fault.

My troubleshooting was to inactive half the tracks at a time, repeat, until I narrowed down the problematic plugins. in my example, Kontakt was hanging commit, but only by Ominsphere being inactive would it commit as expected. So which is at fault ?

Similarly had a Trilian commit problem but this time it actually was the Trillian at fault.

Just flagging for general information

Since Marianna reminded me of your post by replying to it...

You did some good troubleshooting, but to try to make more progress here you might try moving suspect .aaxplugin bundles out of the plugin folder (I would also then trash prefs including being sure to trash the new style plugin cache files).

Try moving out the plugin(s) you suspect most (seems like Omnisphere?) and see if things get stable. Inactivating a track may not be enough to stop all interactions with a bad/incompatible plugin. I would hope that might be able to narrow things down more for you.

[Darryl Ramm]

What are some of the crash messages? I mean you are asking for help on an error... tell us the error message ¯\_(ツ)_/¯ (or multiple of them if they are not seemingly consistent). Crash stacks will often show plugin causes. So copy and paste some of that stack track output as well or drop the files somewhere. First pass is do you see what looks like plugin names in that stuff... sometimes you just get lucky.

What do the Pro Tools log files show? Anything consistent there at the crash time?/end of log?

It is natural to suspect plugins but the troubleshooting you are doing is just not a good approach to finding potential problems here

Have you trashed prefs then tested after that? Make sure you are trashing prefs properly for the new style (2013.12 and later) plugin cache files. Or just use the latest version of PT Prefs 2.

Then since suspecting plugins seems very reasonable you should move all .aaxplugin bundles out of the plugin folder, start Pro Tools and see if this still happens, if so put them back/remove in batches until you triangulate on suspect plugin(s).

Or if you suspect Omnisphere remove that .aaxplugin and start Pro Tools and see if that helps.

This should be what is documented for folks to do in standard troubleshooting, I'm not sure why the stuff there has gotten so useless. (If my tone comes off bad here, I'm not frustrated at you I'm frustrated how badly the Pro Tools troubleshooting documentation sucks).

The tests you should really care about is you fully removing that plugin from the Pro Tools plugin folder and restart Pro Tools. Deactivating plugins, hiding or deactivating tracks are frequently useless as a test of plugin problems. Yes I know about the new dynamic plugin add stuff, don't mess with that. Stop and restart Pro Tools in these tests. I would also trash prefs and the (new-style) plugin cache after major changes while troubleshooting these plugins.

You have support cases open for this? What has Avid support told you? What are those case numbers?-- in case the Avid folks here can help.

[marianna]

Originally Posted by Dizzi45Z

I am so excited for all of these new features, but unfortunately, I have had so many crashes every time I try to commit or freeze faster than real time on all types of audio and instrument tracks. Typically it goes through the process of looking like it is rendering and once it gets to the end of the rendering process, it hangs for a second and crashes.

I have noticed this happens with multiple virtual instruments including Omnisphere, Superior Drummer, Komplete Kontrol, etc. In fact, I don't know that any of my Virtual Instruments that are not crashing after I try to commit or freeze. This includes Committing or freezing the whole track, up to a certain insert, dragging the MIDI to an Audio Track. It doesn't seem to matter if you have the track "do nothing" or "hide" after the commit.

I also am getting crashes trying to commit or freeze any audio tracks in my sessions even if they have no plugins on the track.

Some people in the thread "PT2024.6 | Issues, Bugs and Observations" have mentioned that Omnisphere could be a culprit regardless whether you are committing or freezing an Omnisphere track. I do use a lot of Omnisphere in my sessions, so it's a possibility.

I have sent tons of Crash reports to Avid and I have one I can send to anyone that happened from just trying to commit an Audio track with no plugins on it.

I'm on an Intel Mac Pro 3.2 GHz 16 Core Intel Xeon W with 160 GB of Ram on Ventura 13.6.7

If anyone else is having this problem, please chime in with any findings or possible work arounds.

I did have one session where committing by choosing to commit the selection over the track seemed to work for a short time. I'm still hoping to find a work around.

Hi Dizzi45Z

Darryl makes some good suggestions and asks some great questions.....

1. what error messages are you seeing exactly?
2. can you capture any log files? here is how.....

• Launch Pro Tools
• Reproduce the problem
• When the problem occurs press the SHIFT and ~ keys on your keyboard - this will enter a "trace flag" into the log that indicates when you observed the problem
• Locate the most recent log file (locations are documented below) and attach it to your support case (note: do not move the log file from its current location if Pro Tools is still running)

macOS
Macintosh HD/Users/<username>/Library/Logs/Avid

Click the Go menu from the Finder and select "Go to Folder".
Type ~/Library/Logs/Avid
Click the Go button

Windows
C:\Users\<username>\AppData\Local\Avid\Logs
Note: You may need to show hidden files and folders (check the box in Windows Explorer > View menu > Hidden items)

Simply navigate to the above directory, locate the appropriate log file(s) - they are named by the date and time created - if found you should create a case and attach it.

3. Have you trashed prefs?

4. THIS IS IMPORTANT! move all .aaxplugin bundles out of the plugin folder, start Pro Tools and see if this still happens, if so put them back/remove in batches until you find the suspect plugin(s).

Happy to get a case going but I need to know the above....

Marianna