Sub 37 Editor + Cubase 12

[Julien]

Hi ,
Does someone use cubase 12 with the latest sub 37 editor update ?
Cubase & my sub 37 connect each other very well , I’m using the virtual instrument version .
(I mean when I turn a knob on the plug-in ,
I can hear the sound changing . )
I can write the automation but the sub 37 editor can’t read it . I mean the automation doesn’t change anything on the plug-in so it doesn’t change the sound on the synth itself .
So if you have this setup , could you confirm me it’s working or not …?
Moog support couldn’t help me on this particular issue .
I have the latest sub37 firmware as well.
Cubase 12.0.30
I’m on Mac OS X Monterey 12.3.1
iMac i7
Thanks !

[MrChumley]

It's the same with the Sub 25 editor - it doesn't read its own automation, which seems to be a fault with the plug-in.

The AU version works fine in Logic Pro, but I'm guessing that's not much help to you.

[Julien]

Hi , thanks for your answer . It looks like I’m not the only one on earth .
Did you reach the moog support ?
I did , but they can’t help . I already told them there is an issue with the plug-in .

[MrChumley]

Hi Julien

I didn't bother contacting support because (a) I'm mostly happy to record my controller changes direct from the Sub and (b) because I'm quite likely to move over to Logic when my trial period's up.

I'm happy to drop them a line though if it would add some weight to your discussions with them?

[Julien]

Hi !

Thanks for your answer .
I’m going to automate the sub 37 with Midi CC like you do , waiting for a proper plug-in update .
But yes , if you can reach the moog support it would be great .
It’s very kind of you !
Have a nice day .
Julien .

[MrChumley]

No worries, you too!

[MrChumley]

Well it's a week now since I emailed Moog support and apart from the usual automatic reply I haven't heard a thing.

A bit disappointing to say the least.

[Julien]

Yes , the support is useless unfortunately ...
I will try to reach them again ...
Anyway , thanks for your help !

[MrChumley]

No worries and good luck.

Not the first company I've come across selling expensive gear and seemingly caring very little for their customers.

[oli@sub37]

I ran into this exact issue today, when trying to automate filter cutoff in Cubase. I used to do that all the time in earlier version, but it fails with Cubase 13. The editor software hasn’t been updated since 2022.
Did anybody find a solution?

[Julien]

Hi ,
I still have this issue unfortunately , and the moog support didn’t help me at all and no update since I posted here … they told they didn’t have cubase for testing it haha !
So I automate using the old fashioned style : midi CC …
Don’t hesitate to send an email to the moog support , maybe they will wake up one day !

Julien .

[oli@sub37]

Hi Julien
Thanks for your reply.

I did some more tests today and found that the automation still works fine in the VST2 version of the Editor, but does not work in the VST3 Editor or Editor-VI.

Therefore I submitted a bug report. I hope they'll somehow react.

[oli@sub37]

@Julien

In my case the problem only happens with version 1.1.1 of the Subsequent 37 VST3 plugin. I also encountered severe problems with proper recall of presets. After reverting to version 1.1.0, everything seems to be working fine again.

[Julien]

Hi !

Thanks for the advice ,
I’m on cubase 13 and Mac osx Sonoma now .
I will check tomorrow and let you know .

Have a nice day .

Julien .

[motion drive]

@Julien

In my case the problem only happens with version 1.1.1 of the Subsequent 37 VST3 plugin. I also encountered severe problems with proper recall of presets. After reverting to version 1.1.0, everything seems to be working fine again.

Do you know where to get the 1.1.0 Version? I want to try if it helps my problem.

On the homepage there’s 1.1.1 only