[SPH] Sub Phatty firmware 2.1.9 and Windows driver available

The Moog Forum Moog Beta Forum
1

Hello moog beta group!

Following is a new Sub Phatty release-candidate firmware v2.1.9.

This version includes some few bug fixes, and should be tested for general functionality and stability. Please update your Sub Phatty, and use it as much as you can, reporting any issue on the forum. The version will be installed in the next production line of the Sub Phatty, so we have to make sure it works perfectly.

Additionally, we have created a new, dedicated Windows driver for the Sub Phatty. This new driver should allow DAWs use the Phatty’s Midi ports while used by the Editor plug-in, meaning that you should be able to send and receive Midi to and from the unit, while using the Editor.

NOTE: With the new dedicated driver for the Minitaur posted, there is no need anymore for the generic moog USB driver and it should be removed. Uninstall any existing generic moog USB driver from “Programs and Features” (Control Panel), and manually delete the files “moogusbmidi_x64.sys” and “moogusbmidiks_x64” under “Windows\system32\drivers” before continuing.


IMPORTANT:
Please check for your current firmware version, by loading the Editor and looking for the firmware version number in the preference page. If it’s 2.x, you may install the new firmware. If it’s 1.x, check for your unit’s serial number - if it’s #2892 and lower please do not update your firmware as it requires updating the bootloader. If higher, it’s safe to update to this new firmware.


Download:

Editor version is unchanged. For latest version, please see:
http://www.moogmusic.com/sites/default/files/Moog_Sub_Phatty_WIN.zip
http://www.moogmusic.com/sites/default/files/Moog_Sub_Phatty_MAC.zip

  • OSX users should run the installer

Firmware v2.1.9, packed with the C6 sysex program:
http://www.moogconnect.net/downloads/subphatty/Sub_Phatty_Firmware_Beta_v2.1.9.zip

Sub Phatty Windows driver:
v3.30.0 (Windows 7 and up): http://www.moogconnect.net/downloads/subphatty/Moog_Sub_Phatty_USB_DriverSetup_v3.30.0.zip
v2.23.0 (Vista or XP): http://www.moogconnect.net/downloads/subphatty/Moog_Sub_Phatty_USB_DriverSetup_v2.23.0.zip

Please note the driver should only be installed after upgrading the firmware to 2.1.9, and not before.


Updating the firmware:

  1. Connect your Sub Phatty to your computer using a USB cable. Connect it directly, and not using any hub.
  2. Turn the Sub Phatty on. Push HARD SYNC and PITCH AMT and while holding them both, push ACTIVE PANEL twice. If you push it only once, the update won’t work.
  3. LFO RATE indicator should blink slowly. This means that the Phatty is now ready to receive the new firmware.
  4. Load the C6 sysex program.
  5. Configure C6 midi ports so they point to Sub Phatty In/Out (“CONFIG”)
  6. Load the firmware syx file into C6 (“LOAD”)
  7. Mark the syx file by clicking it once, and then click “SEND”
  8. MIDI LED should now flash slowly. If it flashes very fast it means that the Phatty receives midi, but not updating the firmware. In this case turn the Phatty off and back on, and repeat the 3-button push scenario.
  9. Once the update completes, the Phatty should restart itself automatically. That means the new firmware is now updated.
  10. Run the Sub Phatty Editor and check for the firmware version by clicking on “PREF”. It should now say 2.1.9. If it says anything other than “2.1.9”, that means the beta was not updated, and you need to repeat the process again.


    Installing the driver (Windows only):
  11. Power off your Sub Phatty and disconnect its USB cable
  12. In case you do not have any Minitaur in your system, uninstall any existing generic moog USB driver and manually delete the files moogusbmidi_x64.sys and moogusbmidiks_x64 from Windows\system32\drivers. Do NOT remove any existing Sub 37 drivers.
  13. Restart your computer
  14. Power on the Sub Phatty, connect the USB cable and let Windows auto-detect and install the default SPH driver. This may take a few minutes so be patient.
  15. Once detected, install the new Sub Phatty driver. The installer should load two popup windows, asking to confirm the driver components. Mark the checkboxes in those popups, and let it complete. If asked by the installer to disconnect and reconnect the cable, please do so.
  16. Restart your computer
  17. Check your Device Manager settings. There should be separate entries for the Sub Phatty, and also the Sub 37, in case one is present is your system. The entries should appear under the root tree, with no exclamation mark in them.
  18. Open the Editor, click the PREF button and select “moog Sub Phatty In/Out” from the Midi Input and Output menus. To sync all preset, click the GET button.


    Testing:
    As already noted, the main goal is to make sure that nothing is broken, compared to the version currently in production. Please try to extensively use your Sub Phatty, and test it across all features.

Thanks all for your cooperation!

2

I installed firmware 2.1.9 without any problems and the unit seems to work fine. I have not installed the driver yet since step 2 is quite confusing. If I do have a Minitaur (and most likely the latest Moog USB Midi driver), should I uninstall it or not, before installing this one?

3

In this case keep the generic driver.

4

Excellent work guys, tested here and looking good. Tried in both Ableton 9.6 and Cubase 8.5. Multiclient driver worked fine, was able to control automation in both.

Only small issue that remains is when quitting Ableton I have a hardware disconnected message in Cubase. I have to quit Cubase and then manually end the Sub Phatty editor process in the task manager before opening Cubase again (or just know to quit it initially before loading).

5

Hi,

Thanks for the feedback.

Would you please provide more details about this issue ? It’s not clear if you have the SPH plugin loaded in both Ableton and Cubase, or only Cubase. If you could describe in steps what should be done in order to reproduce it and what are the results, it would be great.

6

Hi Gil, sure.

What I mean is when I load the plugin into Ableton, then quit Ableton, then load Cubase I get this issue when trying to load the plugin there. So no they are not being loaded both at once. It just seems like the driver is not being released/reset etc… when quitting out of Ableton.

Cheers

7

I see, thanks for clarifying ! will check this out asap.

8

I have the latest Moog USB Midi driver from the Minitaur beta, not a generic one…

9

I realize that you actually have both MTR, SPH and S37 in your system. In this case no generic moog driver should be installed, but the 3 dedicated drivers (the dedicated MTR driver hasn’t been posted yet, but I understand you got it already).

Check Windows\System 32\Drivers, all following 6 files should appear:

moogminitaurmidi_x64.sys
moogminitaurmidiks_x64.sys
moogsub37midi_x64.sys
moogsub37midiks_x64.sys
moogsubphattymidi_x64.sys
moogsubphattymidiks_x64.sys

The two should not appear though:

moogusbmidi_x64.sys
moogusbmidiks_x64.sys

10

Thanks Gil,
Everything was installed correctly, hopefully I can begin doing tests in the next few days :smiley:

11

Cool, let me know if you need any further testing on that.

12

Thanks both !

13

My update SPH Firmware 2.1.9 went smoothly. Played with it for an hour, and all working fine so far.

Installed new Multi-client SPH windows driver (W10x64). That also went fairly smoothly. I had to select new MIDI ports in the Editor before it worked, but having re-read the instructions, I now see that step is explained (missed it first time). In my case, I did not see any popup windows, and didn’t have to uninstall any previous drivers. I suspect the OS restart was not necessary either, but I did it as instructed anyway.

Tried some automation of multiple parameters and messed around with MIDI synced LFO. I didn’t even realise I needed the multi-client before this day. Now I see my DAW (Sonar Platinum) can only send MIDI Sync out a genuine MIDI device, so I had the perfect example to exploit the new multi-client driver. Seems to be working well.

I will keep experimenting over the coming days and report back later.

Cheers,
Chris

14

Thanks for the update !

15

Apologies I haven’t manages to post again about EG Amount effecting sound with all OSC’s and Noise off.

Here a patch. (.syx file was not allowed to upload so its zip’d)

When any key down there is noise effected by envelope (On my Sub at least..). EG amount +5 and Cutoff 20hz, the noise pulses. EG amount -5 and Cutoff 20khz same effect same result although noise is filtered according to cutoff.

Play around with keyboard pitches and noise changes as does pulse and strength of effect in relation to cutoff.

I’m using headphones to test this…

Before 2.1.8 update I could also hear OSC noise when they were at 0 and this is definitely no longer the case :slight_smile: Yay!
EG Amount Noise.syx.zip (362 Bytes)

16

Will check this out asap, thanks for reporting !

17

Apologizes, but I’m not sure I understand the scenario, results and expected results. Also, the preset loads with EG AMT set to 0.

Will you be able to provide a details stepped scenario (A, B, C etc) which describes exactly what should be done, what are the results and what would be the correct behavior you’d expected ?

Thanks !

18

Well, not much left to be said with this efficient title. While turning the noise volume knob, LFO slows down about 10 to 20%.

19

Interesting find,

Does this happen only when turning these knobs on the Editor, or also when using the synth only ?

20

Thus far i’ve only tried this on the synth only.