Anyone else having these issues?
I have a similar problem with a hardware disconnect problem which doesn’t allow me to use the editor. There was a similar problem with the subsequent 37 which has evidently gotten a firmware fix for it. Meanwhile I believe I’m still hanging in the wind assuming that the sub37also needs a firm update. I haven’t had time to get to playing my sub37 for a while much less sitting down with the editor so I haven’t followed up. But no response to my problem. Pretty disappointing.
Here is the thread I started:
https://forum.moogmusic.com/viewtopic.php?f=21&t=28696
Ok, yesterday I responded here because I had some time to look into what was.going on with my Sub 37 and the editor. Upon a bit more investigation and careful reading I saw that is is recommended to plug the USB cable directly from the synth into the computer and NOT into a hub going into the computer (my Mac has only one USB input and I listen to it through Logic with my audio interface). Thus the hub I’d been using.
And plugging straight in solved my problem. I had to plug into a different set up to listen to it but now I’m all updated, my custom presents saved and kudos to some of the other presets included with the editor by other users which I added as new presets. Some good stuff there.
So perhaps this is your problem if you are having editor issues with a Sub 37 or perhaps a Subsequent.
I am having the same problem with my Sub 37, just tried what you described and I’m still seeing the problem.
I found another solution to the problem, but it isn’t pretty. If you open up the editor, then go to your Sub 37 and iteratively walk over all of your presets and save them with AUTO SEND enabled in the HARDWARE PRESETS section of the LIBRARIAN, apparently it’ll send an updated sysex dump for the preset as part of the save, and overwrite the screwed up preset in the current location with the correct one. I just did it and everything looks straight now.
Yes. Same problem. Connecting both over USB and DIN MIDI.
Are you on Mac OS High Sierra?
I can’t believe that I’m having this issues with Moog again.
First was the Minitaur (and still is) and now the Sub 37 that was working ok before… the disconnected problem in a new PC with clean Windows install.. Can someone explain what happen with Moog and all this issues?? they don’t try the drivers before releasing them out or what? uffff 
Windows 7 x64 + Ableton 10
Minitaur: Firmware 2.2.1 + Editor 3.2.0 + USB driver 4.35.0
Sub 37: Firmware 1.2.0 + Editor 1.0 + USB driver 4.35.0
Can someone say to me, what should I do to stop the “cannot connect with the hardware” message PLEASEEEE???
Having this problem too. Was hoping to load my presets into a rental Sub 37 for a gig.
Sub 37 is plugged directly into the MacBook (no hub). It sometimes seems to work, but the patch names are wrong (they reflect what they were before I edited them and saved them under a different name). Please fix this, Moog!
So, this is going on in Mac too. Nuts. It was supposed to be a Windows issue only, and no one from Moog is answering with help…
I repeat always the same, so many years without solving a simple driver, imagine if you have a problem with a modular.
I have this problem here too. Hardware presets list doesn’t match what’s on the actual hardware, looks like they’re all shuffled in order.
Going through the presets on the synth and re-saving each one fixes it but only temporarily - pressing ‘get’ in the editor will put me back in the same mixed up situation as before.
macOS 10.13.3 and Sub 37 connected directly.
Seems to be that they are not available to help users that already bought their products. (Yes, I’ve contacted them thru their CONTACT option in their website too, but no answers until now [7 days]).
Maybe we have to pray to deserve their time and help.
Hello all,
I believe most of our problems here are due to the editor. I will share a collection of links for the latest beta versions of the editors that work with OSX High Sierra and drivers that should help with the Windows connection problems as well:
Sub 37 Editor v1.0.0 (Windows) & 1.0.1 (OSX), fixing preset sync issues in High Sierra:
http://www.moogconnect.net/downloads/sub37/Sub_37_Editor_v1_0_1.zip
Subsequent 37 Editor v1.0.0:
http://www.moogconnect.net/downloads/subsequent37/Subsequent%2037%20Editor%20v1.0.0.zip
Subsequent 37 CV Editor v1.0.0 and new firmware v1.3.2:
http://www.moogconnect.net/downloads/subsequent37cv/Subsequent%2037%20CV%20Editor%20v1.0.0.zip
If updating the editor and/or MIDI driver does not correct your issues, please contact us directly at techsupport@moogmusic.com so we can help you individually.
All the best,
Hi everybody,
take care with the mentionned upgrade, it fully messed up my wave potentiometers, it’s definitely not bug free at least on the subsequent 37 cv.
This synth was fully functionnal before the upgrade, it really looks like a last minute bug.
Is any of you aware of a way to roll back to previous firmware version ? is it a supporte method ? the new cv-out mapping in the editor is nice, but the price is too high for it…
→ problem description
potentiometers calibration :
on the physical synth :
the 2 oscillators wave potentiometers are not aligned properly any longer on the physical device :
When the pot is set on the synth on the sawtooth, it’s off by one full graduation.
Using an oscilloscope confirm this.
It’s consistent on the 2 oscillators
On the software :
aligning the potentiometer on the software to the sawtooth, produce a sawtooth really, but it’s then off by one full mark of the physical device.
The drawing of the editor, is not aligned to the physical panel (but is indeed to the internal calibration which is now off).
Are you aware of this issue ? what can I do ? can I rollback to the 1.3.1 ? FYI, I’m using mac os 10.11.6
FYI, it was fully fine before the upgrade, played all the day without any trouble.
Another problem :
added to this, the 2 octave rotary switches, if moved too fast, are not reflected properly in the editor, it was fully fine before the upgrade.
tried to reset back to 1.3.1 → no change
tried the pot calibration method → no change
can anyone share if you have the same issue ?
Hi
After installing this Windows version of the Subsequent 37 editor, when I open my Plugins folder within Ableton Live I have two plugins available;
Subsequent 37 Editor(x64)
Subsequent 37 Editor-VI(x64)
What is the difference between these, and does it make any difference which one I use? They look identical when I open them.
They are identical. The VSTi can have its GUI automatically adjusted when sending program changes to the hardware from within a DAW. AFAIK that’s the only difference.
Cheers, I guessed something like that but always nice to have confirmation.
I’ve contacted Moog by email 7 days ago, and still no answer.
I spent all night reinstalling all my system, migrated to Windows 10 Pro, I have everything working as intended now and like it must be, with MIDI only thru USB.
Because I’m not a moron, I came back to update, because I really complained about the editors, and the “disconnected” issue, but I also must say that I never got support from Moog by email nor in this forum. The thing just doesn’t work in Windows 7 if you have a modern PC (z270 / z370).
Anyways, everything working now on Windows 10 Pro + Ableton Live 10 (USB driver 4.35.0 + Firmware 1.2.0 + Editor 1.0)
Best.
It sounds as if you had reminiscents of older drivers in your System32\drivers folder, clashing with the new ones. When you move on to the newer 2.23.0 (for Sub 37) in Windows 7, you should really remove the generic moog driver and files. Note that for minitaur, the correct driver for Windows 7 (and up) is 4.35.0.