Quote:
I did some more tests, and the BETA1011-013 version is playing nicely in *newly-created* Ableton Live sessions. Where things are going really sour are existing sessions that were created on my previous (Intel-based) iMac. 9.92 just plain crashes trying to load one of those sessions on my new Mac Studio, and the beta (and the 10.10 release) both exhibit slow/weird GUI behavior.
I also can't seem to find the "extreme tweaker" setting in the new versions, did that get deprecated or moved somewhere obscure?
Can you check the following? This might help in the (rather unlikely) case that Ableton does the same thing that Audition 1.5 does.
What I think is happening (only read this if you're interested, not relevant for the solution)
What Audition 1.5 does: It appears that Audition has a fixed size for the storage of parameters. If a plugin exceeds that number, the remaining parameters will get random values that seem to come from uninitialized memory. They are usually - but not always - 0. The maximum number of parameters appears to be around 8000. Audacity has had a similar problem in the past, with the maximum number being 4096 - we ran into that multiple years ago when we exceeded 4096 parameters and they fixed that. Audition 1.5 is very old so that can't be fixed anymore. It's also possible that programs just set all new parameters to 0.
So if we have a slider that has a range, like from 0.0001 to 0.50, it will likely be set to 0. As you may know, you can set most sliders outside of their official range and for 99% of sliders that's perfectly file - the range might be weird from an audio perspective but the software will do what you asked for without any issues. But there are some sliders where setting them to 0 causes issues. We have in recent versions added protections against invalid values if they would cause crashes, which is likely why 9.92 crashed and 10.11 does not.
Possible solution
There is a new parameter that controls the screen update speed. Its range is 0.5 - 60 times per second. You can find this setting in multiple places, among others: Application settings -> Resources -> Graphical User Interface. Open the detailed settings and the "Framerate" slider appears. Please check what it's set to and report back here. If this is indeed the issue, I'll change the behavior such that when it's set to 0, we'll use 60 instead of 0.5. 0.5 would mean 1 image per 2 seconds, so that matches your description.
Warning: If this helps, please be aware that this probably means that ALL new settings that were added are set to invalid values.
Edit: I did that anyway. This is clearly something that can go wrong.