Just did the firmware upgrade 1.1.16 and installed the latest editor 0.9.36.
Ableton Live 9.6 32 bit, crashes instantly after the editor is loaded (OSX 10.11.3).
When I try the standalone version the editor opens fine, after a few seconds the preset name of the current selected preset on the Sub 37 is displayed and after that the editor freezes completely, just showing a spinning beachball.
Thanks for reporting. Can you save that crashing Ableton project and send it to gil@moogmusic.com ?
We would like to investigate this case if possible. Thanks!
Hi,
Have you the same result with both the AudioUnit and VST ?
Thanks,
Salvator
The audio unit crashes instantly after opening in Ableton 9.6 32bit
Also if any other Live/OSX users could test and chime in their experience, it would be helpful. Thanks!
-Amos
I reinstalled the 0.9.33 editor which worked fine for me.
If the Sub 37 is switched off, the audio unit or vet is loaded properly but as soon as i switch on my Sub37, Ableton 9.6 32bit crashes.
Could it be a firmware issue?
Works great here – I did a quick test in Ableton v9.5 (have not updated yet) with Editor 0.9.36 and Firmware 1.1.16. Loads, plays, communicates with the hardware fine. Did a few automation parameters – filter, resonance, drive… automated those with MIDI LFO’s from Max. I’ll be using more tonight in existing session now that it proves stable! I wonder if it’s something in Ableton 9.6 – one of the reasons I turned off auto-update there.
it’s a 32-bit plugin issue; here’s a fix:
http://tritonedigital.com/temp/Sub_37_Editor-0.9.37-OSX-AU.zip
http://tritonedigital.com/temp/Sub_37_Editor-0.9.37-OSX-VST.zip
fix will be included in next official build.
With the 0.9.37 update everything works fine again 
Thanks for the report. Are you using AU or VST ? Can you switch between the two from time to time ?
Hey Gil,
I was using VST. I’ll try AU today. Also going to test multiple instances, and grouping the Editor into a Rack and configuring 8 macros for automation.
That would be great ! We really need to confirm that Ableton is stable. Please note there’s 0.9.37 already available, so it worth updating before starting.
Okay, will do. Here goes..
I noticed a few weird things when using the Editor (v0.9.37) with Ableton (v9.5) with multiple instances. I’m not sure the intended behavior though, and would appreciate a quick cap of what to expect.
The way I’d like to use the Editor in Ableton is creating and External Instrument device and the Editor plug-in, then group them together into an Instrument Rack. That way, I can configure 8 parameters and map them to the Macros.
When using in this way, it seemed that the controller information from one lane got mixed up with the other. It didn’t exactly correlate, but resulted in the sound breaking up and muting when I tried to have two instances play at once.
I thought setting them to discrete MIDI channels would keep them happy, but it did not. Each instance did retain it’s respective preset, but going back and forth between them resulted in this quirky behavior.
I tried not grouping them into an instrument rack, but then the MIDI channels would follow each other… one instance would take on whatever value you set in the other one, and vice versa. The preset, too, would follow in a similar way.
As I understand, only 1 instance can be active at once? I work with a MIDI track and PRINT track anyway, and print to audio before moving onto the next part, but here it seems like multiple editors interfere with each other, and aren’t kept separate (presets, controller info, etc).
If I’ve got it all wrong, please let me know! It’s different concept from soft synth entirely – with one hardware to communicate with an effects plugin. Should I expect to be able to run multiple instances with separate presets, and be able to go from one to another to work on separate parts?
Just wanted to bump this thread… curious how we can expect to work with the Editor with multiple instances… if there’s some kind of configuration that is recommended. Thanks 
There is indeed a fundamental problem with having multiple instances active at the same time. Unlike with a soft synth, the actual hardware would always be shared between all plug-ins. The best solution we have devised is a mechanism to “make active” a certain instance of the plugin while de-activating all other instances… this would allow you to toggle between instances as you want to print or work on each one in turn. After all, only one could really be playing live at a time anyway without causing confusion.
Getting this new feature tested and working across all platforms has been deemed to be more than we can guarantee in time to release soon, so this feature (deactivating multiple/background instances of the editor) is currently scheduled for a first update after release.
The way I usually work when I have one hardware synth and I want to use it for a bunch of parts is a little different… I have one MIDI track that hosts all the MIDI clips I want to play, and then multiple audio tracks (all set to the same hardware audio input from my synth), one audio track for each “part” I want to record, like bass, lead, fx, etc… I put all my MIDI clips for the different parts on the one MIDI track, and dial up whatever sound I want for a given clip and then record it as audio. This has the obvious limitation that you can’t arrange all your MIDI in parallel and leave it as MIDI while buiding your whole arrangement, like you would with a soft synth… but it’s a natural way of working when you have only one synth playing multiple parts and you’re working without patch memory (which admittedly the Sub 37 has, but I started working this way when using synths with MIDI but no memory, where you had to design a sound and record it before you could use that synth for any other sounds)
sorry for the ramble, hope it helps
Ah! Good to know. I didn’t think it was working as it should
Very helpful! I’ve done it a few different ways, but until the “make active” feature is implemented I’ve settled on a dedicated Editor track that drag MIDI to – from a dummy MIDI track that’s grouped with it’s respective PRINT track. This way I know where the MIDI in the arrangement is, and I can more easily edit and re-print.
I also save each preset in a project as an Instrument Rack with up to 8 parameters configured to the Macros.. which I can drag into the session from Ableton’s browser. Not a bad way to work at all. The “make active” thing will help, but definitely not a deal breaker.
Thanks Amos!