Sub 37 pre-release Editor 0.9.25 + firmware version 1.1.13

[paul_sub37]

can someone maybye send me the vst os x editor plugin. i m thinking of upgrading to sub 37 from sub and like to comapre virtually

It's not publicly available yet, it's a by request thing - see this post by Amos:

http://forum.moogmusic.com/viewtopic.ph ... 75#p148894

[braddo]

Hey can someone using the new firmware comment on new features? We heard about dimmable LEDs (awesome) anything else?

[LuLoop]

We heard about dimmable LEDs (awesome)

Hi,

You can dim the leds, using the Editor but not on menu from the Sub 37.

regards Luloop

[paul_sub37]

Hey can someone using the new firmware comment on new features?

I've not seen anything new in the firmware with regards to stand-alone features - I think it's more about providing the necessary compatibility with the editor.

The firmware changelog doesn't have any entries for 1.1.13

[Glynbo]

Hi all, I have the new editor and Firmware and so far I think it is great. I have one problem and that is, how do you set up the VST editor to work in Ableton Live 9.5, it`s baffling me? Many thanks Glyn.

[LuLoop]

Hi Everyone

Found some 2 more issues.

Running now on Firmware 0.9.26 Windows 7 and Midi cable connected. (no USB connection)

1. in editor: init preset is not responding.
2. in editor: Random Preset not responding.

Regards Luloop.

[paul_sub37]

I just hooked up my sub 37 via 5 pin din midi to my steinberg ur22 interface on my mac and the editor is working the same as it does via usb (other than needing to have the correct midi input/output ports selected in the editor).

I can send my own patches from the librarian to the 37, I can use init and random too - and the sub 37 is sending the sysex to the editor when I change preset on the 37, keeping everything in sync.

editor is 0.9.26 firmware is 1.1.13 - mac running OS X el capitan 10.11.1

[LuLoop]

I just hooked up my sub 37 via 5 pin din midi to my steinberg ur22 interface on my mac and the editor is working the same as it does via usb (other than needing to have the correct midi input/output ports selected in the editor).

I can send my own patches from the librarian to the 37, I can use init and random too - and the sub 37 is sending the sysex to the editor when I change preset on the 37, keeping everything in sync.

editor is 0.9.26 firmware is 1.1.13 - mac running OS X el capitan 10.11.1

Hi Paul,

I found the problem.

My midi interface "Miditech MIDIface 4x4" is the problem maker.
Chance the interface and all is working fine. Windows 7 and OS X.
Thanks for the tip

midi to my steinberg ur22 interface

Have a nice day

Regards Luloop

[LuLoop]

Hi all, I have the new editor and Firmware and so far I think it is great. I have one problem and that is, how do you set up the VST editor to work in Ableton Live 9.5, it`s baffling me? Many thanks Glyn.

Hi,
The VST plug-in Folder from Ableton, often has two separate installation locations. The stand-alone version usually gets installed into a subfolder of "Program Files". This subfolder is normally named after the plug-in developer. The second location is for the VST plug-in DLL.

The Sub 37 pre-release Editor has no install procedure, so you have to do it manual.
You have to copy the "Sub37 Editor.dll" ( found in the zipfile , VST(x64) or VST(x86) you got from Amos into the plug in folder from your Ableton.

Wish you all the best,

Regards Luloop

[paul_sub37]

Hi all, I have the new editor and Firmware and so far I think it is great. I have one problem and that is, how do you set up the VST editor to work in Ableton Live 9.5, it`s baffling me? Many thanks Glyn.

Hi Glyn - this is what I did to get it working in live 9.5

Drag Instruments>External Instrument to a midi track
In the External Instrument device set Midi To to the Moog Sub 37
Set Audio From to the relevant audio eg your audio interface
Drag the sub 37 editor plugin after the external instrument device
Now when you record on that track it records midi from the 37/editor and plays the audio returned from the 37
If you enable Automation Arm in live you can then record changes made via the editor/hardware

It's a very sweet setup, having access to all of ableton's automation tools to control the 37 as if it were a vst instrument - but with that amazing sound that only a real analog synth can give.

[Glynbo]

Hi LuLoop,Paul and everyone, thanks for the advice but I had already carried it all out and it has been working but not in a way I thought it would. I have done some midi recording of notes and various control movements, cutoff and resonance with great results but the GUI of the editor has no signs off response! But on playback it funtions perfectly with still no response in the GUI.Maybe I have the inputs outputs set up wrongly in the editor? Cheers Glyn.

[Amos]

Please post a few screen shots of the editor while we anxiously wait for Amos' reply email. Thank you.

I would happily do so, but with Amos not making the link public and not posting any screenshots of it himself as far as I'm aware, I don't feel comfortable posting screenshots.

I checked with our marketing folk; they say it's OK to post screenshots if you want. Thanks very much for your consideration!

[paul_sub37]

You probably get the same as me then Glyn - if I make changes in the editor then it is recorded and played back with the editor knobs moving. In envelopes it shows as a "sub 37 editor" parameter with the correct name eg Filter Cutoff

If I make changes with the hardware, then it gets recorded as a "Midi Ctrl" parameter with the midi cc number rather than name eg 19 for filter cutoff. As you said, it sends the correct midi to the sub 37, but it's not reflected in the editor in real-time as those changes are made.

I guess this makes sense:

changes originating in the editor are sent from the editor to the 37 and are recorded by ableton. On playback, ableton sends the ccs to the editor, and the editor sends them to the 37. So the editor is in the loop and can reflect the changes.

Changes made on the 37 are sent to ableton and recorded as they would be with no editor present. The editor does reflect these changes in realtime when they're being recorded. When played back, ableton sends the ccs to the source - namely the 37 itself rather than the editor.

Not sure if there's a way to get the editor to show in realtime what is being sent by ableton to the 37.

[paul_sub37]

I checked with our marketing folk; they say it's OK to post screenshots if you want. Thanks very much for your consideration!

Great - thanks for that. I think everyone should see the quality of the work you and your team have been doing with this:

[paul_sub37]

And a couple more: