I got Windows 7 64-Bit Professional running here, and it is not at all possible to use the firmware updater. I am pretty sure the issue is still the MIDI driver.
What I have to do to get the Sub 37 recognized by Windows:
Simply switch on the synth? No. Windows always (reproducably) tells me there’s an unrecognized USB device that it couldn’t find any drivers for.
Unplug the synth from USB, the switch it on, and after some seconds plugin in the USB cable again? Yes, that way it works.
So it seems after being switched on the synth needs a little moment to become recognizable for Windows.
When trying to update the firmware with the updater tool:
As always, I have to plug the USB cable into the switched-on synth to make it usable. The update tool then recognizes the synth and gives me the usual instructions how to start the update: Cutoff and fine tune knob to minimum, hold pitch bend wheel up, then restart the synth.
The problem is that when I restart the synth, the USB driver problem kicks in again, and the synth is recognized correctly.
When I unplug the USB cable and plug it back in after the synth has restarted, Windows recognized it, but the updater does not. I’m stuck with “Installed version: Unknown”.
So, as a conclusion, the firmware of the synth has already been deleted by the cutoff/fine tune/pitch bend combination, but I have to boot Mac OS to install the new firmware version
Same here Win 7 64. Latest Moog USB 3.30 driver.
So I tried manually but only updated the firmware not the panel (Firmware 1.1.14 -Panel 1.1.13).
The Sub37 then went with blank display and all panel leads on.
Finally I use my MacBook Air and everything was fine.
Just so it won’t be forgotten: The Windows issues are still unresolved.
If the Sub 37 is switched on while connected to the computer, Windows (in my case 7 Pro 64-Bit) does not recognize it and reports an unknown MIDI device. It does work if the synth is switched on first, and then - a few seconds later - connected to the computer.
Because of (1), neither the Updater nor the manual update with MIDI-OX work smoothly. Everytime the synth reboots, the MIDI connection is lost and the previously selected MIDI device is invalid. One has to unplug and then re-plug the USB cable, wait for a few seconds, and then restart MIDI-OX so it searches for MIDI devices again.
OSX (currently latest version of El Capitan) does not have any of these problems. Manual update as well as the updater work perfectly fine on Mac.
I have some difficulty in testing to reproduce this problem.
I have a couple of native Windows PCs here for testing… testing now on the Win 7 x64 one…
It appears I can leave the Sub 37 connected via USB and switch its power off and back on again, and it consistently is identified by this PC.
In MIDI-OX, each time I do this I have to go back to Options>MIDI Devices and click OK, in order for MIDI-OX to refresh its connection to the MIDI device, but it then works. (This is normal for MIDI-OX any time a MIDI device disappears/reappears to the OS).
At this point I wonder a couple of things:
does the USB chipset on the motherboard make a difference (some work some don’t)?
does your particular PC have this same problem when using old production firmware (v1.1.0, v1.0.5 or so)?
If you care to try downgrading firmware to check this, I’d appreciate the effort (although that won’t necessarily lead to a fix, it’s just more information at this point). I apologize for the trouble and we’ll certainly do what we can.
One other thing you can try: Un-installing the Moog USB MIDI Driver v3.30.0… with no driver installed, do you get the same error when powering-on the Sub 37 while USB is connected to the computer?
Also there is now a driver v2.23.0 ready to test; this driver is the main one we are now recommending for Windows 7 because it can be installed without needing to do any Windows Update (v3.30.0 can require a Windows Update in order to read its code-signing certificate, where v2.23.0 os signed using a legacy certificate which doesn’t require any update).
So, after you uninstall the v3.30.0 driver and see if you have the same problems with no driver,
please try installing this v2.23.0 USB driver: http://www.moogconnect.net/downloads/usb/MoogMusic_MIDI_DriverSetup_v2.23.0.zip
Thanks, Amos. I will try all that. Let’s see if I find the time tomorrow.
Can you give me a link to an old firmware version? Or should I try the released version from the website?
Also, maybe it’s relevant that I’m running Windows with Bootcamp on an iMac?
That’s extremely relevant! The firmware updater is known not to work well on virtual machines.
We’re investigating a fix for this but didn’t want to change the updater so soon to release, given the amount of testing that’s been done already with the current version.
Nobody had mentioned they were using a virtual machine out there in the “real world” until now so I hadn’t thought to mention it in the documentation, but I’ll add a note about this to the ReadMe_First document.
In your circumstances your best bet for firmware update is probably the OSX installer on your native Mac system.
Regarding the USB device errors under Bootcamp… Sounds like I need to gather more info about this.
I’ve always used Parallels for Windows on my Mac and never had USB problems; I also don’t have this problem on my native Win7 system.
However, I have a tablet PC running Win10 that does give an occasional “USB device has malfunctioned” error associated with power cycling the Sub 37, so I’ve seen something – just don’t know what it means yet.
By the way, I have uninstalled the MIDI driver version 3, and instead installed version 2 (as it was recommended for Windows 7).
Unortunately, the behavior didn’t change at all…
Having the synth plugged in when switching it on results in Windows now recognizing it. The Sub 37 appears like this in the device manager:
Unplugging and the re-plugging the USB cable while the synth is already switched on fixes everything:
This still makes the Firmware Updater unusable on Windows.
And I still think, the whole problem would be fixed if the synth would finish booting up before reporting its presence over USB.
My suspicion is that Windows asks the synth for its information before the synth is able to reply properly (because it’s still booting up). That would also conform with the message that is shown in the “Gerätestatus” field on the first screenshot, which in English means: “this device does not work properly, because the device’s firmware does not provide the required resources”.
Therefore, I used OSX to update to the latest firmware, using the Updater App. Worked totally smooth, like always.
