Sub 37 pre-release Editor 0.9.25 + firmware version 1.1.13

[ziggomatic]

Hello!

Can someone explain me how to share a patch with the editor? i choose the patch, i press "share preset" and i got a message saying "error. you have to choose a patch"

thanks!

[synththeory]

Although not sure If I correctly understand your question:

If Sub37 is connected correctly with the editor then choose the patch name (or multi patch names) and drag them from the right pane to the left pane on the Librarian page. This can be to whatever folders you have created on the far left hand pane (right click to create)

Is this what you are after?

[TVPC]

Thanks Paul for checking it out. Having to disable it is obnoxious but whatever I guess lol... I wish the editor worked with a generic MIDI track, hopefully it will when it's all said and done

[paul_sub37]

It looks like the minitaur and sub phatty editors both work as effects and not instruments, so I doubt they'll change that for the sub 37. I guess having it run in chain with DAW "external instrument" instrument handling is the attraction of doing it this way - I can see the logic in that.

[TVPC]

I hope that its like the sub phatty and minitaur in that regard!

[breun]

I can confirm the Sub 37 (beta) editor works in the same way as the one for the Sub Phatty.

[AudioRoyale]

Hey guys, I am using the editor in Ableton Live 9...
I start to make a patch on the hardware... and if the editor is minimized everything is OK, so I don't look at the editor... But when I choose to bring the editor up it restarts to a INIT preset... Is anyone else experiencing this? Is there a way to make the editor not to initialize the patch when i maximize it?
Is this a bug or something?
Thanks

[synththeory]

Hey guys, I am using the editor in Ableton Live 9...
I start to make a patch on the hardware... and if the editor is minimized everything is OK, so I don't look at the editor... But when I choose to bring the editor up it restarts to a INIT preset... Is anyone else experiencing this? Is there a way to make the editor not to initialize the patch when i maximize it?
Is this a bug or something?
Thanks

Yes it's something you have to watch out for, lost a few myself already. It does not always happen but one workaround is to hit the 'compare' button before starting the editor. After the editor has loaded hit 'compare' again and your patch should hopefully be intact.

Editor could maybe do with a code change in this department.

[ziggomatic]

@synththeory

cool thanks! i shared a patch but i haven't received the email with the patch. do you know how long it takes?

[synththeory]

Build: 0.9.29 on FW: 1.1.13
Driver: 3.3.0

Standalone: thanks for adding the Quit and fixing the windows positioning issue. All good so far.

VST + Standalone: Presets do not seem to be occasionally getting reset on Hardware when opening Editor now, So far so good:-) , I am cautious though as it might show up again.

The 'current' preset name on the hardware still does not always show on the Editor GUI preset name display. The user is faced with a blank Preset name panel.
-----
No issues encountered with installing new Driver.

Great work.

[synththeory]

@synththeory

cool thanks! i shared a patch but i haven't received the email with the patch. do you know how long it takes?

No idea. depends who you sent it to:-) From what you wrote it seems you tested the sharing facility by sending to yourself yes?

[LuLoop]

@synththeory

No idea. depends who you sent it to:-) From what you wrote it seems you tested the sharing facility by sending to yourself yes?

Hi,

Sending to yourself, works also fine.

Regards Luloop

[dieter198]

Is there anybody who tryed the VST Editor in Windows7/Cubase?
After moving any of the knobs the value snaps to zero.
This problem only occurs in the VST-Version. The standalone version works fine.

* When i load the VST in Wavelab it works fine too. It really seems to been a special problem with Cubase.

[Amos]

If I'm tweaking via the software editor, then ableton records those changes as being from the editor with all the nice parameter names, and on playback it gets sent to the editor and shows knob movements. The editor sends the changes to the synth, not ableton.

If I'm recording changes from the hardware, then the synth is sending MIDI CCs to ableton, which is recording them, and on playback it is sending those same MIDI CCs back to the source - ie the hardware synth.

Like you, I think it would be great to have it all consolidated to the editor device - but really not sure if that's possible given the signal chain.

There is one way that definitely makes this work in Ableton, but it's a bit tedious... on the other hand, it might be the correct/only way, if there's not a way to make it automatic. (I may need to check with the Abes on this)

The idea is, when you turn the knobs on the Sub 37 you just want it to control the plugin automation, you don't want to have a separate lane of raw MIDI CC numbers to worry about. So what you want is for the Sub 37 panel to just act as a hardware controller for the plugin.

To do this, you have to set up Live's MIDI mapping exactly the same way you would for any generic MIDI controller and any plugin.
Go to Settings, and on the MIDI page, click to enable REMOTE on the line for Sub 37 MIDI input.
Then type ctl/command-M to open the MIDI mapping interface... click a virtual knob in the Sub 37 Editor plugin and tweak the real knob on the panel to make the MIDI mapping. Do this for every knob for which you want to record automation.
Then when you hit Record and turn knobs, it should be recorded directly as plugin automation.

If you don't go through these steps, Live doesn't know that the MIDI from the Sub 37 is associated with those particular knobs -- it's easy to overlook this because the plugin has them all mapped internally, but Live doesn't know that.

[dieter198]

After moving any of the knobs the value snaps to zero.

still same problem in fw 1.1.14.

could anybody test the it in Cubase and provide a feedback please.