IMPORTANT: You must first check for the current SPH firmware version by loading the Editor and looking at the firmware version number in the PREF page. If it says 2.x, you can install the new firmware. If it’s 1.x, please check for your unit’s serial number. If it’s #2892 or lower, please DO NOT update your Sub Phatty firmware, as it requires also updating the bootloader.
NOTE: With the new dedicated driver for the Minitaur posted, there is no need anymore of the generic moog USB driver and it should be removed/uninstalled. Please uninstall any existing generic moog driver from “Programs and Features” (Control Panel), and manually delete the files “moogusbmidi_x64.sys” and “moogusbmidiks_x64” in “Windows\system32\drivers”, before installing this driver.
Updating the firmware:
Connect your Sub Phatty to your computer using a USB cable. Connect it directly, and not using any USB 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.12. If it says anything other than “2.1.12”, it means that the firmware is not successfully updated, and you need to repeat the process again.
Installing the Windows driver:
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.
There are really too many to mention at this (very early) stage of the beta. We are currently mainly working on the most critical issues that are preventing from the app to perform normally. As the phase goes on I will provide more information about the on-going changes.
I have mentioned the feature several times but I don’t think there is a dedicated thread, actually I am not aware if it was deliberate to make it work this way.
Let me try to explain:
In Ableton Live, when I simply load the new Minitaur Editor, the plugin is loaded in a MIDI channel and I can send notes directly to that channel, open the editor and change/automate parameters without making any further settings. The notes are recorded on this channel and I don’t have to make any manual mappings nor load any extra plugin for this to work
If I load the current beta for the Sub Phatty Editor, I have to load an extra channel to send MIDI notes to the unit, since any VST/VSTi which is loaded changes the MIDI output for an audio output. The Editor communicates properly with the synth, but there is no way to route the MIDI notes directly to it.
There is a workaround though; you are able to use the same channel but you have to load an External Instrument in order to send MIDI notes.
This is all unnecessary with the Minitaur Editor, you simply load the VSTi and you start recording right away.
For the record, I never send the audio output for my external synths back to the DAW, since I use an external mixer. What this means is that the workflow might be different for some users.
Anyway, the Minitaur Editor is easier to set up in Ableton than the Sub Phatty.
Installation:
o Installation went fine.
o VST2 and VST3 versions are detected and available under Sonar (By default Sonar hides the VST2 version. To see the VST2 versions you must change Preferences|File|VST Settings|Hide Related VST2 Plug-ins checkbox).
Usage:
Unfortunately, automation is NOT working correctly under Sonar with the following plugin
VST3 VI (instrument) version
Recording automation does not work.
When you create an envelope in Sonar for filter cutoff, the cutoff knob does change, but so does the ‘host bypass’ button.
When you create an envelope for any other setting, none of the other UI elements change.
Automation IS working fine under Sonar with the following plugins.
VST2 VI (instrument) version
VST3 Effect version
VST2 Effect version
Strange ‘Host bypass’ button issue
In both the VST3 Effect and VI plugins, Sonar incorrectly indicates a ‘Host Bypass’ whenever the plugins GUI opened.
So in summary 3 out of 4 plugin versions all working perfectly, only 1 is not (which is fine for my purposes as I am happy using any one of those 3).
A software LFO that can be assigned to any parameter in the patch, sending that modulation over midi
A software ‘Duophony’ mode where MIDI received by the plugin of overlapping notes adjusts the OSC2 Pitch according to the distance between the bottom held note.
Okay, so maybe these features overlap the SUB37 features, so I am probably just dreaming. …right?
PS. Having fun modulating settings of the Sub from Sonars step sequencer…
Thanks chrbay for the report (and requests). I reported your Sonar feedback accordingly.
While at it, what of the issues you previously posted in the following thread, still exist for you using 2.0.0b3 ? They all are supposed to be fixed by now… Will you check them out please ?
As for the requests, they seem to involve major firmware changes which we can’t afford at the moment. We might be able to adapt the Editor with small changes though, if we have enough time and the requests match prioritization.
So from ‘Sub Phatty Editor Release 1.1.0’ testing notes…
1) Plugin detection problems - These are fixed. I think that was clear from my first report.
2) VST2/3 VI (instrument) ‘Echo MIDI from Host’ issue - this problem persists.
The Plugin only ‘sees’ Channel 1 and echos on channel 1. This would be okay if the plugin echoed to the
channel number specified in the PREFs, but it doesn’t.
If the plugin could see channel 4 like the effect version, the method detailed below would work. 3) VST3 fx (effect) ‘Echo MIDI from Host’ issue - this version of the plugin never had an issue because it can SEE channel 4 coming in.
You must select the correct channel 4 in Sonar, at the source, but it works fine.
(I operate my Sub on channel 4. In Sonar I configure VST2/3fx ‘Enable MIDI Input’ and I route my midi to it in Sonar)
4) 32bit plugins - I do not run the 32bit version of the plugins anymore, so can’t comment on them.
5) SUB MIDI Keyboard Sharing: I am still unable to share the MIDI keyboard of the SUB between SONAR and the Sub Editor.
Do I have to be using particular MIDI drivers that support sharing the ports for this???
Hi GilW,
I have ‘Moog Sub Phatty’ in the Device Manager, under ‘Sound,video and game Controllers’, and properties info is…
Driver Provider: Microsoft
Driver Date: 15/07/2016
Driver Version: 10.0.14393.0
Last event…
Driver Management concluded the process to install driver wdma_usb.inf_amd64_134cb113911feba4\wdma_usb.inf for Device Instance ID USB\VID_2662&PID_0FF6&MI_00\7&235BDA36&0&0000 with the following status: 0x0.
Is this correct?
I was under the impression the new MIDI drivers could be shared between the DAW and the SPHE…am I mistaken?
Driver isn’t installed, or not correctly installed. When installed you should see a “Sub Phatty” dedicated entry under the root… It should let you share the hardware midi input between the Editor and DAW, so you can use the Editor and send midi to the hardware via USB at the same time.
If you already installed it, please remove and reinstall. Follow my instructions as posted here, including manual removal of older components.
…right? 