[SPH] Sub Phatty release candidate firmware 2.1.11 available

The Moog Forum Moog Beta Forum
1

Hello moog beta group!

Sub Phatty release-candidate firmware v2.1.11 is ready for test.

Following is a list of changes in the version:

  • Fixed a Pot Mode bug (Relative pot mode) - master volume was max on boot, until master vol knob was tweaked. Now should get correct (preset or live) master volume on boot.
  • Updated USB stack in firmware to work with Moog USB Driver (Note: also changed Sub Phatty USB “Product ID” number to be different from bootloader PID, so that Moog USB Driver will only try to work with new main firmware, not old firmware or bootloader, since the older firmware and bootloader use old USB stack which isn’t compatible with driver)
  • Fixed the LFO Rate/Noise issue and Octave. Behavior is back to default.
  • New feature: Polychain (requires support on Editor side)
  • New feature: Delayed Transpose (KB Octave change affects only subsequently-played notes, not notes which were already held when changing KB Octave) - also require an update on Editor side. Default is the old behavior (KB Octave change affects all notes including those already playing)

We will start another (and hopefully final) regression phase to make sure everything works as expected, and then it will go into production. Please update your SPH, use it massively and report any issues as new threads on the forum.

Windows users should use the dedicated Windows driver, which allows the Phatty’s Midi ports to be used by both the DAW and the Editor plug-in at the same time. This is the same driver posted with firmware v2.1.9 so no need to reinstall if you already did.

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 SPH 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, please check for your unit’s serial number. In case it is #2892 or lower, please do not update your firmware as it requires updating the bootloader. If higher, it’s safe to go and update the firmware.


Download:

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

Editor version is still the production one:
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

Windows driver is unchanged, download from:
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.11, 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.11. 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 Windows driver (Note: If already installed, there’s no need to reinstall):

  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:
    The main goal is to make sure that nothing is broken compared to the version currently in production. Please use your SPH extensively and report any issues in new threads on the forum. All features should be verified.

Thanks for your cooperation!

2

Thanks, updated, so far so good.

3

Dear Gil, since this is labeled as a release candidate i would like to pose a few questions:

To have anything properly tested, there should be proper release notes with a change log accompanying each release. Thus far, i have only seen “Sub_Phatty_Firmware_Changes_2.0.pdf”, repeatedly bundled with each new beta firmware, which describes changes in the last major release and not the ones it is bundled with. Is there a dedicated team of testers at Moog who have access to the relevant release notes/change logs or is Moog relying solely on the exploratory testing efforts of its end users, in this case the Beta testers from this forum?

Is it possible to give us a status update on the requested features; are there any implemented, and if so, shouldn’t these be tested as well? (And the editor would likely have these new features in its interface as well.) It would be very nice to know which features were requested and which ones have ‘passed the bill’ and which ones didn’t make it into the new firmware.

4

Update went smoothly, the LFO/noise bug is gone indeed!

I agree with @Space Lee that if this is a release candidate the beta testers should have an update history at least as a plain text.

5

So far so good. The octave switching behavior bug I posted in the main board is now gone, and octave behavior working as expected since the last update.

Rock solid so far!

6

Hi,

Thanks for the update. I added the list of new features and bug fixes in this version to the main post. Overall, it would be most beneficial if you’d just use your SPH regularly and extensively, and watch for oddities. Bug fixes are mostly tested and verified in-house, and the new features in this specific case won’t work, as they need to be supported on the Editor side.

7

Thanks Gil! Much appreciated.

8

My firmware update went fine. I will report back if find anything strange.

Although I appreciate that the in-house testing of known bug fixes would be extensive, I would still like to add my voice to what Space Lee has said. I would like to see a bit more attention given to the release notes, in the official release at the very least. I too have found the repeated posting of the old “Sub_Phatty_Firmware_Changes_2.0.pdf” in firmware zips pretty annoying.

Thanks Gil, and looking forward to a new Sub Phatty Editor …

Cheers,
Chris

9

Thanks for your feedback. I will pass that to Amos who is in charge of publishing all release notes.

10

Ah, when you see Amos, please remind him of the oscillator drift function that is obsessively wanted :wink:

11

+1!

12

Installation went smoothly and everything seems working fine.

It happens to me that, everytime i update firmware, LFO rate changes in one particular patch. :unamused:
It´s the same patch which I told before, has an issue I already reported. ¿Could be possible that a patch is corrupted?

13

Is that the “La Vida” patch ?

Thanks.

14

Yes, that’s it. Thanks for remembering.

15

Couldn’t reproduce that. LFO rate is the same when using both 2.1.11 and 2.0.3.