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 !
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.
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 .
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?
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 .
No worries, you too!
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.
Yes , the support is useless unfortunately …
I will try to reach them again …
Anyway , thanks for your help !
No worries and good luck.
Not the first company I’ve come across selling expensive gear and seemingly caring very little for their customers.
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?
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 .
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.
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.
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 .
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
Sorry, I totally missed your reply.
No, I don’t know where to get it officially. I had the 1.1.0 Installer in my software archives.
BTW, I tried to contact Moog Music, but nothing ever happened…
I found this thread because I have the exact same issue, although I’m currently running Cubase 14. I own both a Subsequent 37 and a Minitaur – and both editors give me this exact same issue. I can move a knob (such as filter cutoff) and hear the synth react in real time, and thus draw automation in write mode. However when I go to play back, even though the automation is written, the plugin does not move and the synth does not change.
I also have Logic and Ableton on this computer (mac), where I tested the AU plugin and automation works fine when playing back. So it appears this an issue with the VST plugin. Unfortunately for me I prefer working in Cubase, so I am hoping that they will update the plugin to address this issue. The editor is so close to making it a perfect hybrid ecosystem of hardware+software, allowing me to use my live synths as if a plugin, but without automation that aspect isn’t so useful.
For now I can confirm that CC data recorded in the midi region (key editor) does work, but this defeats the purpose of the editor panel and ease of automation, which I find much nicer to do on the track lanes.
I submitted a ticket to support, but based on what it sounds like around here, I will be lucky if I hear anything back. If I do, I will report here.
If anyone is able to share the VST2 version or 1.1.0 version for Mac, please do! Although I am not certain it will work for me, since the release notes say 1.1.1 added Apple Silicon support which is what I need. But it would be nice to try to see if it will work.
Did you ever get anywhere with this?
Cubase 15 officially dropped VST2, so the old editors won’t work going forward.
Hi, unfortunately no. I haven’t updated to C15 yet but what I ended up doing was building my own editor in cubase to create knobs just for the CC I most often need to automate (cutoff, LFO speed, and couple others). I didn’t even bother to make it look nice - just some knobs in a window, mainly just so I can access them as automation. Bummer though because the plugin is much nicer looking and represents the synth 1:1…
My feeling is that Moog needs to update all their software, but even though I submitted a support ticket back in February, it’s been crickets from them. Sigh.
Ugh. That’s a pity, and I don’t expect we will get a software update anytime soon, if ever.
I have managed to get it to work somewhat (still using 1.1.0), where I can automate parameters, but it doesn’t update the plugin when playing back. Conversely, when I automate by adjusting the plugin’s knobs with my mouse, it seems to write to the correct parameters and update correctly when playing back. Cutoff is a good example, from the plugin knob it writes to and updates the ‘Filter Cutoff’ controller lane in Cubase, but if I do it from the hardware directly, it writes to CC19 and doesn’t update the plugin when playing back (but it does change the sound). It’s bizarre and frustrating. I am going to see if there’s some way of forwarding the CC19 controller automation data to write to the ‘Filter Cutoff’ lane correctly. Don’t know if this is possible, but it seems like the only way.
I don’t know much about editor building in Cubase, but I might look into this. Can anyone do it? Like you, there are some parameters that I use often (I have also programmed the 8 encoders on my NI S88 to do this) and wouldn’t need a whole bunch of functionality since a lot of it is set and forget and requires no automation.