Bug: Commit, Freeze Crashes Constantly 2024.6

[Darryl Ramm]

Thanks for the update. I'd sure contact Spectrasonics and just ask them if they know about this already and if they need anything from you. Ask before doing any work on your side for them. And sometimes that question takes a bit of fanagling as front-line support folks often don't know what is needed and can ask for too much info. Try to have them ask developers for you.

Often plugin vendors get info about these kinds of problems fairly quickly. Hopefully they can also confirm they are in touch with Avid already. If the plugin vendor has all they need it also may mean Avid does not need any more info, let Avid support know/ask them.

[Dizzi45Z]

I've already heard back from Spectrasonics and they have already received reports about this issue and have sent me a Beta of their products to test and see if it fixes the issue.

I have to say that Spectrasonics is one of the best companies when it comes to support. I have used their support multiple times and they have always treated me very well and seem to be on top of things. I know their products are on the pricier side of things, but considering their amazing support, I feel it is always money well spent.

I'll report back if these Beta versions seem to fix the issue.

----- I've updated the name of this thread to include Omnisphere/Keyscape

[Dizzi45Z]

Great news! The beta version I got seems to fix the problem. I've tried it out on my session that had the most issues and it is flawless.

Hopefully Spectrasonics releases this sooner than later for everyone struggling with this.

Thank you everyone (especially Darryl) for your help.

[Darryl Ramm]

Fantastic! Thanks for letting everybody know.

It's great when you get good technical support like this from plugin vendors (I've had good experiences from Softube, Eventide, ...). One reason I like to contact plugin vendors as soon as possible once there is suspicion (and worse case it can quickly become apparent if they are terrible, don't have a real developer team etc.).

I wish there was a usable ranking of technical support quality of software vendors in this space, might be a handy purchasing tool. The spread there is so enormous. One of the reasons I'm hung up on RME as an interface provider is just their quality of technical support.

I don't own any Spectrasonic plugins, but now I would be much more likely to purchase them in future.

[emgexclusive]

Having the same problem, mainly AAE -9173. Running the same specs on Ultimate with HDX Magma Chassis on Ventura 13.6.7 Please give insight, problems been imminent amongst all versions since last December


MacBook Pro 16 inch 2019 2.3GHZ 8 Core Intel

[Darryl Ramm]

Originally Posted by emgexclusive

Having the same problem, mainly AAE -9173. Running the same specs on Ultimate with HDX Magma Chassis on Ventura 13.6.7 Please give insight, problems been imminent amongst all versions since last December


MacBook Pro 16 inch 2019 2.3GHZ 8 Core Intel

This makes no sense.

AAE 9173 errors was not the problem the OP was describing.

If you've been having problems since last December it probably has nothing to do with what seems like a new problem on 2024.6 discussed in this thread.

Insight? What more insight could you possibly need than is already in this thread? Did you actually bother to read through this thread?

You have a whole thread here of how to troubleshoot the problem that the OP was having caused by some Spectrasonic plugins on 2024.6. And you may be having the same problem if you have Spectrasonic plugins (maybe even on older versions?) and if so the test there should be simple, as hopefully would the solution to obtain beta plugin updates from Spectrasonics. If you don't have those plugins and are just getting 9173 errors and other problems then your issues likely don't have *anything* to do with this tread and you should look elsewhere. Starting with standard troubleshooting steps, and plugin troubleshooting.

Please be considerate of other users and don't spam threads on DUC with unrelated problems. Doing so pollutes threads that are helpful for other users having the same problem as in the thread.

If you are stuck create your own new thread and clearly describe the troubleshooting you have done. Start by reading and following "help us help you" up the top of every DUC web page and/or open a case with Avid support.

[emgexclusive]

This forum is to report what I'm experiencing less your opinion, if your aren't helping please fall in the trash.


Sincerely the guy you tried to roast

[Darryl Ramm]

No the guy trying to point out you are posting in a completely irrelevant thread and trying to get you to go get help in the right place.

This forum is to help out all users, with some expectations users can be bothered to not just spam their **** onto unrelated threads like clueless morons.

Good luck getting help here.

[noiseboyuk]

Great news on a beta fix already!

Originally Posted by Dizzi45Z

I have to say that Spectrasonics is one of the best companies when it comes to support.

Amen.

A lot of Windows users had issues for years with a very sluggish Omni gui. Spectrasonics could never reproduce it internally, but eventually they did and a fix appeared fairly quickly after that. Their approach and dealings with me were excellent - they really are a class act.

[belolab]

I have same issue. All plugins but only on some sessions. Rock solid protools until 2024.6. Doesnt do it on a new session instigated since the upgrade to 2024.6, only old sessions. I run a pro studio, so have a lot going on, and its not a change in anything else. Just protools. Cant downgrade, as the previous version now gives me an ARA error if I try to open a session I used ARA on on 2024.6.
Weil try importing all tracks to a new session for now to see if I can circumvent it. Its pretty weird, and seems like it might be a bit of a major bus.