... Thank you!Regarding the issues: this stuff can pretty much be worked around, so nothing too critical. Still, it can hit the otherwise magnificent workflow. I constructed a Live (5.2) set in which I use multiple instances of LiveSlice 1.40 as a regular multiout VSTi plugin. I noticed that the GUI stops responding every time I open the interface of another instance, then close it and open another one.
I can also repeat this with just two instances: load the first one, do some slicing, close the interface. Load the second instance, try to do something with it -- and both GUIs stop responding. More specifically, you can't do edits like place slices or set volume/MIDI values, adjust number boxes and so on, i.e. everything having to do with mouse movements. Normally the cursor changes into a pointing finger, now it just hovers over the area as a regular arrow and doesn't adust any edit values.
Other than the mouse editing actions, in this state the GUI responds as usual, especially the sample/file browser still works normally. The arrangements also trigger as they should. The plugin itself doesn't actually lock up.
[Edit: This appears to happen when loading LiveSlice in EnergyXT as well, just tested on a different machine.]
Only those instances of LiveSlice which are loaded from the same directory (instances which reference the same .dll and its associated settings) are effected by this issue. If I create a directory under the LiveSlice plugin directory and copy the content there as well, I'm always able to load both of those individual copies and everything works as it should. So now I have three or four LiveSlices nested in the LiveSlice directory in such a manner for multiple instances
Also, if I save the plugin bank in Live, only the first arrangement (triggered with C1) and the first loop in the Loops list get saved. When running another instance of the plugin and loading a bank, I can restore only these.
Now, normally this wouldn't be an issue in Ableton Live, since I could save the whole plugin state as a "Live Clip" and then just drag it into a project when I need it. Many times I actually tend to use this method even with stuff that saves the banks perfectly. However, when these two issues are combined, they are quite nasty: if I'd like to save a copy of the content in one LiveSlice instance and do a variation of it in another one, I can't save it in this manner as it would then reference the same .dll and the GUI would lock up. I can't transfer the content as a bank either, since it leaves most of the stuff unsaved.
I would be (even more) grateful if these things were looked into at some point. Thanks!
