Hi,
I'm having an issue with the Orchestools Sections in Ableton Live 11.2.7.
When I have more then one instance of any of the four plugins in any Live set and I try to load the set, something wrong happens in the loading process and breaks MAX for Live plugins.
For example, I first noticed that the impulse response samples (IRs) of Abletons Convolution Reverb Pro don't load into the effect, hence pratically deactivating it and blocking audio completely. It is a MAX for Live effect. In fact all MAX for Live effects in my set stop working. Their UIs load fine initially but they are mostly unresponsive and block the effect chain. Deleting the broken MAX effect and putting a new one in doesn't help. It seems MAX was not loaded correctly at all. This happens even with a new, nearly empty set, that only has two default instances of OT Sections and one Convolution Reverb Pro effect.
But if I first open a set with just two instances of OT Sections (MAX not started during set-load) and add a MAX effect afterwards, MAX works just fine, until I save the set and try to load it again.
Also, another VST3 plugin I have in my set, Decent Sampler, doesn't load its configuration and samples correctly and is unresponsive after loading of the set finished, very similiar to MAX effects.
With a comparsion tool I compared Ableton's log files from a succesful set-load with just one OT Sections instance and a broken set-load with two instances. The only difference I can spot is this line appearing in the log of the broken load:
2023-01-22T11:59:33.085177: error: VST3: plugin processor output audio bus 0 could not be deactivated (error: false)
And of course the second OT Sections instance being loaded, but it is not diffrerent to succesful load:
2023-01-22T11:59:22.541183: info: VST3: Going to restore: OT PERC
2023-01-22T11:59:22.845283: info: VST3: plugin processor successfully loaded: 3VStudio 'OT PERC' v1.0.2 (cid: {56535441-6263-646F-7420-706572630000})
2023-01-22T11:59:22.847744: warning: VST3: plugin did not follow bus configuration protocol (error: false)
2023-01-22T11:59:22.847949: info: VST3: plugin supports the IInfoListener interface
2023-01-22T11:59:22.850677: info: Vst3: couldn't initialize controller with processor state of OT PERC: not implemented
2023-01-22T11:59:22.850691: info: VST3: parameter count is 2081
2023-01-22T11:59:23.003568: info: VST3: couldn't hand processor state of OT PERC to controller: not implemented
2023-01-22T11:59:23.003823: info: VST3: Restored: OT PERC
Nothing about MAX not loading correctly.
Any idea what could cause this issue when I have two instances of OT sections in my set?
Hey,
after some more testing it seems that some MAX for Live (M4L) devices still function, but not correctly. Their UIs don't update. I can still change parameters in M4L devices, but their UIs only update delayed, when the focuse changes out and back into the device. But still, they are unusbale that way and I can't get the Convolution Reverb to work anyhow.
Furthermore, I have the same issue on my Laptop, too (I'm on Windows 10, BTW). When I create a new, empty Live set and add two instances of OT Sections, save and reload, M4L devices don't work correctly.
I'm currently working on an orchestral set, that is fairly big, mostly sample based instruments. It includes several instances of Spitfire Audio's Labs and BBC Simphony Orchestra. With this set on my Laptop, one instance of OT Sections breaks the set compared to two instances on my main PC. Both have the same Ableton and MAX version, all the same plugins and the same amount of RAM.
This baffled me, so on my Laptop, I tried deleting plugin after plugin from my set but kept one instance of OT Sections. I saved and reopened the set after every plugin I deleted, until M4L worked again at some point. At that point adding a second instance broke M4L again.
This is all very wierd to me. First I thought it might be related to RAM issues, because the set uses up nearly all I have, but then again, I have issues with empty sets as well as described above.