Sub Phatty release-candidate firmware v2.1.12 is ready for testing. This version fixes LFO Rate changes when tweaking EXT IN.
Installation instruction remains the same. Please update your SPH, use it massively and report any issues as new threads on the forum.
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.
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.
*Please note the driver should only be installed after upgrading the firmware to 2.1.11, and not before.
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.
Updating the firmware:
Connect your Sub Phatty to your computer using a USB cable. Connect it directly, and not using any hub.
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.
LFO RATE indicator should blink slowly. This means that the Phatty is now ready to receive the new firmware.
Load the C6 sysex program.
Configure C6 midi ports so they point to Sub Phatty In/Out (“CONFIG”)
Load the firmware syx file into C6 (“LOAD”)
Mark the syx file by clicking it once, and then click “SEND”
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.
Once the update completes, the Phatty should restart itself automatically. That means the new firmware is now updated.
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):
Power off your Sub Phatty and disconnect its USB cable
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.
Restart your computer
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.
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.
Restart your computer
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.
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.
Sub Phatty Editor development is put in hold at this point in favor of the Minitaur Editor, which has been given a higher priority. We are currently working on a new MTRE version which will introduce major bug fixes. However, it may take while as Amos is held by higher-priority tasks, and is expected to be back into MTR development next week. I could post the latest version, but would rather have everybody install a version which introduces a major improvement.
I am beginning to feel lost. What’s the status on the completion of the Minitaur firmware?
When will you get back to the SPH?
Until now, i checked this forum daily but i am going to stop doing that because there is zero information on progress. Maybe it’s a good idea to post something like a timetable to keep expectations realistic?
I’ve updated to the new firmware and installed the USB driver. After installing these my SPH is identified as “2 - Moog Sub Phatty”.
I am using Sonar Platinum which cannot load the current version of the VI editor.
I attempted to load the older 1.03 version of the VI editor. I was able to load the 32bit version only. However I could not select “2 - Moog Sub Phatty” for input or output, and the editor could not connect to the hardware.
The 1.1.0 version of the editor (not VI) shows “2 - Moog Sub Phatty” and can connect. It seems to function normally. However I do not appear to be able to route midi to the SPH using this version, or record midi from the SPH, so I don’t see much utility from it.
Am I right in assuming the VI version allows you to route midi to and record midi from the SPH? If so that is what I am after, and I will be keenly awaiting a new beta of the VI editor that will load in Sonar.
What’s allowing midi interaction with SPH while using the Editor plugin, is the Windows driver (OSX doesn’t need any).
There’s nothing that the VSTi component does which the VST doesn’t. There are some issues we know about that can prevent the plugin from loading, which is set to the highest priority for fixing.
EDIT: I think I understand the intended workflow of the editor now. I got thrown off by the instruction to ensure the SPH is NOT included as a controller when you use the VST.
I tried running them both together and it works fine, I can route midi normally to the SPH, and use the editor to manage patches and controls. It seems you can only have one instance of the editor in a project.
This being the case, I don’t think I need the VSTi so urgently, but I’m still keen to try it out and see if it improves my workflow in Sonar.
This may be off topic then, maybe I should start a different thread?
I can set the VST as a VSTi in Sonar, which is what I am doing. The VST connects to the SPH, and can change patches and modify controllers.
But I can’t see how to send note information to the SPH, i.e. actually play the synth from a midi track in Sonar. I’ve only been able to do that by adding the SPH as a controller in Sonar, and according to the manual for the SPH I can’t do that and use the VST at the same time.
Am I missing something here? Should I be expecting to play the synth by sending midi to the VST, or is that not how it works?
Should I be expecting to play the synth by sending midi to the VST, or is that not how it works?
That’s not how it works. The software editor doesn’t produce any sound, it’s the hardware synth that produces audio, so you’ll have to send MIDI to the synth and connect the audio out from the synth to your DAW.
