V17 makes ableton crash when audio interface goes offline

[ThatRedDot]

Hello,

Not sure what to do with that, but I installed V17 beta yesterday evening and today I have been struggling with Ableton. Every time when the session is left alone for 30 minutes, and Melda plugins are used, the audio interface goes offline. This is normal and I will just go into the audio settings and re-enable the ASIO driver after the interface started up, and session will be restored. It always worked until now. But today, when I do that, its crashes the whole session.

This has happened now several times, and this has never happened before. The only thing that has changed is trying out the V17 Beta.

I'm not sure if its related, but this is a little concerning.

What happens, in order;
1. Create a session and make a song, use plugins as normal
2. Wait for interface to go to sleep after 30 minutes of inactivity (RME ADI-2)
3. Come back to warning message that interface is offline

To this point this is all expected, normally I would click OK on this message box in Ableton and go to audio settings and re-enable my audio interface there. Then session continues as normal... but, after installing V17 clicking OK will crash the whole Ableton session

The Melda plugings used in the session are
TurboReverb
TurboDelay
SpectralDynamics
Tremolo
StereoProcessor
...In case that helps

[ThatRedDot]

OK this is driving me pretty nuts, is there a way to go back to 16.11? Can I just uninstall 17 and re-install 16.11 from the website? Can't remember where I read it, but it was apparently not that straight forward and I don't want to break presets and whatnot.

[martin-meldaproduction]

I did try to reproduce the issue with the mentioned plugins, but nothing happened. There must be something different that plays a crucial role. If you could provide me with a simple project that exhibits the issue, we would be grateful.

Anyway, to install back version 16.11, I see you are on PC:

1. Back up the folder C:\Users\username\AppData\Roaming\MeldaProduction somewhere. This folder is hidden. It may not be necessary, but do it to be sure in case something goes wrong.

2. Run V17 MPluginManager and click "Uninstall All".

3. Install V16.11, ideally download from our web first .

You should be OK.

[ThatRedDot]

Thanks Martin,

Yes it's really weird and started to happen right after V17 install. I would want to roll back to 16.11 to see if it goes away as that's quite literally the only thing that has changed (no Windows/GPU/Audio driver update or the like either).

I would love to get to the root of this as well to remedy it. Hope its something else still that's clashing for some reason.

Let me experiment a bit with it