Ableton Forum

try this

load a convolution reverb pro
turn the width and dry/wet up to 100%
turn the audio engine off
save the project
quit ableton
load the project
the width and dry/wet will now be at 0%

this happens with at least two other devices, too

the workaround is to never save with the audio engine off

http://i.imgur.com/Qr8fmy0.png

jbaylies wrote:try this

load a convolution reverb pro
turn the width and dry/wet up to 100%
turn the audio engine off
save the project
quit ableton
load the project
the width and dry/wet will now be at 0%

this happens with at least two other devices, too

the workaround is to never save with the audio engine off

http://i.imgur.com/Qr8fmy0.png

Can't reproduce in Live 9.7.1 64bit on OS X 10.11.6.

Stromkraft wrote:

jbaylies wrote:try this

load a convolution reverb pro
turn the width and dry/wet up to 100%
turn the audio engine off
save the project
quit ableton
load the project
the width and dry/wet will now be at 0%

this happens with at least two other devices, too

the workaround is to never save with the audio engine off

http://i.imgur.com/Qr8fmy0.png

Can't reproduce in Live 9.7.1 64bit on OS X 10.11.6.

OK, after further testing I think you're misinterpreting your results. I'm not sure how this is supposed to work, but it's clear to me that loading a Max For Live Audio device with the audio engine off mean it's inoperable and will remain so until the audio engine is on.

In the case of saving a set with the audio engine off, the preset will still be respected if you load it with the audio engine on. So the problem, if it is a problem, is about loading MFL devices with the audio engine off, not saving.

I mistakenly loaded with the engine on when attempting to follow your steps, so that's why I couldn't reproduce at first. With the engine off also when loading I could. Turning the engine on at this stage doesn't activate the preset, a reload is needed.

I think Strom's point is quite valid, still your finding is worth a check with [email protected] imho.
I'm pretty sure that starting Live with the audio engine turned off is not something really common, but I have the feeling that if what you've observed isn't intended this could at least shed a light on other issues.
Would you take care of reporting this please?
thx

This is still a problem.

turn the audio engine off

MaxforLive devices don't work, this is desired behaviour and not a bug....

Cheers
D

I simply never turn the audio engine off anymore. It causes other issues with things like outputting audio to channel #s > 13.