We would love to have some more feedback specifically related to OSX and Editor as a plug-in. If you do use it in your DAWs, please try to max it out, try some automation, create custom presets and banks, export and import, save and reload the sessions and verify that what you saved is what’s reloaded. My estimation is that there’s some more to be found in that part of the software.
Thanks for your precious feedback !
I just started using the editor in Logic Pro X. Most of the automation values are on scale of 0 to 1. It would be nice if they were numbers relating to the parameter. For example, it would be great if Filter Cutoff value was actually the frequency and not just the decimal.
Hi. Not sure what you mean. Do you see range of 0-16383 on automation for rotating control ? If yes than it’s makes sense, as this is the range of values set for knobs and you would need the automation range match the actual range used on the plug-in. Otherwise the knobs will have bigger steps and less resolution.
It has been pretty smooth so far on OS X 
In the first public beta version, I had one small issue when I opened the editor. But I was not able to reproduce it so I never reported it.
Upon opening the editor, the “not in sync” pop up window would display, but each time i clicked OK, it would reappear. After clicking OK about 5 times it then went away. This was in Bitwig, but like i said i haven’t been able to reproduce it again.
Is it possible that the GET process was not able to complete on each of the previous attempts before it stopped showing again ?
Hey Guys,
I haven’t been able to pin it down, but sometimes the Editor (v0.9.31) and Sub 37 (v1.1.14) stop communicating with each other in the middle of a session when using Ableton v9.5.
To try and get it to communicate again, I tried deleting and re-loading the plugin, then loading a patch – no go. Then I turned off / on the Sub 37, which got them communicate again, but the meter in ableton went red, then a rainbow wheel, then crash. I saved the report in case you guys want to have a look.
I’m not sure what sequence of events causes the communication to stop, but I’ll go to work on other plugins for awhile when I come back the Editor channel won’t work. The MIDI is sending receiving, but no meter out of the hardware.
Do any other Ableton users experience this?
Jay
Hi Jay,
Are you connected to the Sub 37 using DIN or USB ?
Thanks.
Hey Gil,
USB direct to Mac Pro’s front port. The crashed thread was 11, which was something
about MIDI callback.
Edit: I just sent you an email w/ crash report, editor settings screen grab, etc. Let
me know if you’d like anything else, or for me to try something.
Best,
Jay
OK thanks. Will pass that to the development.
I updated the Editor to version 0.9.33 and still having quite a bit of weirdness going on inside Ableton. Things like the hardware losing connection, a patch seemingly latching without the Amp Env being latched, filter not responding, patch sounding REALLY whacked out.
In Ableton, I have the Editor setup with the Moog Sub 37 as the only MIDI input, local control OFF, MIDI channel 1.
I usually have to go through a series of things to get it working properly – reload patch, choose a different MIDI input then back to Sub 37 input, unplugging and replugging the USB cable in. I’m not sure exactly what works, but last time it was changing patches back and forth… but then I got the weirdness going on.
I have this in an existing session, but I’ll try on it’s own session to narrow it down. I feel like other people would be having this issue, and i haven’t seen any reports on this board. I have a launchpad, a faderport, a livid code v2, a Kawai VPC USB controller and old Evolution controller… but they’re all on discrete ports.
Thing is, once I get it working, it’s good for awhile. Then all of a sudden it disconnects and the fun begins. Hope to figure this out 
Hi,
Well I did some recording in Logic with automation and found out that every thing is working smoothly.
Automation is not working when you use the editor.
But that is not a problem on the moment.
You always can make adjustment in Logic.
I am sorry that I have not work more in Logic and try things out.
In any way.
using v0.9.33 and the last firmware
Regards Luloop
Can you please give more details about this one ? Is Editor automation not working or automation not working in general when Editor is active but works when not ?
Thanks for reporting Jay. Do you happen to have an Ableton project which can demonstrate this ?
When this happen, if you save and reload the project does it fixes itself or you still experiences all these issues once reloaded ?
Well… Editor is working very good, but when you want to use record automation using the editor (moving the knobs and so in the editor)…This Is not responding in Logic. So No recording.
Only the Hardware knobs (sub37) are recording in logic the automation. And that is working fine.
Editor is not build for this I think. It is not a real “Instrument”.
I really hope that I am wrong…Would be awesome to use the editor…moving knobs…and this all will be recorded.
Regards Luloop
Does it work for you if you use a different plug in, the same way you are trying to record automation with the Editor ?
Hi,
Every plug is working with record automation. I mean plugs like software synths.
But the Sub 37 editor is not a software plug.
The editor is software but only a surface from the Hardware… It is not responding to Logic directly.
Try it out and you will see.
I hope I am wrong.
Regards Luloop
I believe it should respond to automation like any other plug-in. Actually it was tested a few times (mostly on Cubase) and used to work nicely, but on latest version I did encounter some similar issues under Windows/Cubase. It might be some kind of fault. I will pass that on, thanks.
Hi, testing team.
It would be nice to get some response from you who are using Logic.
Is the editor working like a “software synth”? So you can record the movements from all the knobs?
Thank you so much. I really would like to know this.
Thanks in advance.
Warm regards Luloop
Hey Gil,
Whatever problems I was having, the ‘Restore Default Global Values’ button seems to have helped… it modified the date on the Application Support / Preset Preferences file. It didn’t appear to change anything that I can see, other than the DIN / USB selection, but must have done something under the hood that I’m not aware of. Sorry for false alarm.. I’ll try to leave some constructive feedback now that I’m out of the woods.
Jay, any kind of feedback is always constructive. Please do not hesitate to mention any issues you may come across.
I am interested to know what of the previously mentioned issues you had are still happening ?
Luloop,
I will have to check it out locally. Thanks.