Often when opening the project with the Convolution Reverb Pro the patch is default, not the one I chose…
I think it happens after opening Ableton after a crash.
Anyone else had the same issue?
max for live Convolution Reverb Pro WRONG PATCH
-
Samuel L. Jizzle
- Posts: 466
- Joined: Tue Jan 21, 2014 12:42 am
Re: max for live Convolution Reverb Pro WRONG PATCH
With other plugins, yes. After a crash.
-
TomViolenz
- Posts: 6854
- Joined: Mon Dec 13, 2010 6:19 pm
Re: max for live Convolution Reverb Pro WRONG PATCH
And it seems to be notoriously hard for M4L devices to retain presets/settings.
-
DaWrecked1
- Posts: 10
- Joined: Mon Jun 09, 2014 6:35 am
Re: max for live Convolution Reverb Pro WRONG PATCH
I really hope when Ableton (and other DAW's) updates in the future they adopt a design from Bitwig's "sandboxing plugins" feature. That design seems flawless. 10 out of 10 times it's a single plugin that crashes your entire DAW. For music creation I still easily prefer Ableton over Bitwig....but that 1 feature in Bitwig is a game changer. If a plugin crashes....it doesn't crash your entire DAW along with it.