Was working with the standalone 0.9.31 and suddenly noticed it was no longer sending some data (but not all) to the Sub 37. It seems to be receiving all data – i.e. changes made on the keyboard showed up in the editor, and some changes made in the editor (such as osc buttons, knob settings) show up on the Sub 37 but I cannot change presets and a few other things from the editor. I tried the following to no avail:
rebooted PC and Sub 37 several times.
reinstalled the latest driver (3.30)
deleted the entire Sub 37 folder under AppData/Roaming/Moog Music Inc and had it read over all the presets
I even reverted back to 0.9.30 and 0.9.29 saw the same issue
Finally, I have verified via MIDI-OX that MIDI data is flowing to and from the Sub 37 via the USB cable.
Is there any other settings (folder with data or registry entries?) I could delete to start anew, or does this sound like a bug in the driver?
From your description it looks like you did all needed to “reinstall” the current version. I wonder if any other Windows users (and Windows 10 in particular) are experiencing similar issues ?
Meanwhile I should ask if you could possibly find any reproducible scenario which can make these problems show up ?
Unfortunately I can’t reproduce it, as I have yet to get it working properly again. When it happened I was only using the standalone editor (windows, 64-bit) and MIDI-OX and the Sub 37. No other MIDI devices were connected and no other programs were running on my PC.
Tonight I just did clean install of 0.9.33 and I have a similar issue. However it now appears the only thing(s) not sent from the editor to the hardware are preset changes. If I change preset via the browser Preset Name or Category controls or the Library Hardware Preset list, the hardware does nothing.
I can make changes to presets (knobs, buttons) and even send changes to MIDI settings, General settings, etc. It’s just presets that are not getting sent.
For what it’s worth, when I select “get” (to force it to get all the presets) I see sysex messages via MID-OX. When I select a preset on the hardware, I see sysex messages via MIDI-OX. When I select a preset on the editor I do not see any messages on MIDI-OX.
Edit – since typing the above I have tried the following to no avail
completely removing driver 3.30, re-installing it
re-booting PC and Sub 37
another clean install of the 0.9.33 editor
turning off DIN MIDI on the Sub 37
problem remains, can’t change presets from editor, though I did notice something interesting
when I started the editor after doing the above, and after it sync’d to the hardware, the MIDI Input said “3 - Moog Sub 37 In” and the MIDI output said " 3 - Moog Sub 37 Out". I though this was interesting because in the past I had to actually select the IN/OUT from the drop-down (whereas this time it seemed to know what to select by itself) and it used to have a “2” instead of a “3”
It happens with and without MIDI-OX running. I’ve run the editor right after a PC boot (so as to avoid contamination or influence from any other program) and still observe this behavior.
I’ve even tried swapping USB cables…
Edit:
a few more things:
I had been using a USB 3.0 port on my PC, I tried switching to a 2.0 port and the problem remains
I found that I can copy a preset from the hardware preset pane into the preset library pane, then double click on the preset and it will send the data to the hardware buffer (to the current preset)
This might be a head slap moment , but the more I dealt with this the more it seemed like a MIDI program change receive or send issue (send from the editor’s perspective, receive from the hardware’s. Sure enough, once I set MIDI program change receive to on, it worked as it should.
Now, I’m not so sure that I accidentally turned this off the other night. I don’t usually change this setting hardware or otherwise.
Must program change receive be on to work properly with the editor? (if so, then I wonder why send doesn’t have to be on for it to work the other direction…) If so, it might be good for the editor to detect the state of this switch and alert the user if it is in the wrong state when the user tries to change programs via the hardware present pane on the editor. Might prevent others from pulling what’s left of their hair out trying to figure out why it suddenly stopped working.
I think I understand this. Although, maybe there does need to be some change to make it more user-friendly.
The Sub 37 hardware has always had the option to disable sending/receiving Program Change messages, because some people need this in their complicated MIDI setups (for instance, the Sub 37 is controlling some other synth, and you want to be able to change presets on the Sub 37 without changing presets on the other synth it’s controlling… or vice versa if the Sub 37 is being controlled by something else but you want it to ignore Program Change messages from this other controller).
So all that is fine, but it can create a problem with the Sub 37 Editor, as follows:
When you double-click a preset from the Hardware Presets list in the Editor (Librarian page), the editor only sends a Program Change message (for example, select preset 4 from the Hardware Presets list, the Editor just sends the message “change to program 4”) instead of sending the entire preset data as sysex. The assumption is that the presets on the Hardware Presets list are already in the hardware. When you select a preset from the user library, the entire preset data is sent to the hardware as sysex, because it’s assumed that this preset isn’t already in the hardware’s memory.
So this is fine as long as the hardware is not ignoring program change messages… the Editor should probably be smart about this; maybe if Receive Program Change is disabled, then the Editor can always send the sysex even when you are clicking on the hardware presets list…?
I think it’d just be good if the editor could alert the user when he tries to do something that won’t get done because of the settings at the given time. (In this case, alert the user if he tries a program change (double click in hardware presets) while the hardware is set to ignore program changes).
, but the more I dealt with this the more it seemed like a MIDI program change receive or send issue (send from the editor’s perspective, receive from the hardware’s. Sure enough, once I set MIDI program change receive to on, it worked as it should.
