This version uses a new SDK, which has a potential for new regression issues. Please use it extensively and report anything unusual.
Note that we’ve posted a few questions to members who reported issues in the past, that are supposed to be fixed by now.
We’d be interested to know if they still exist, and would appreciate your feedback.
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, 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.
Working great over here on Cubase 9/Windows 10. I really tried to trip it up with automation and it really seemed to handle it well and always returned back to the original state.
Thinks you guys really nailed it and are going to make a lot of people happy.
I have done some testing with Sonar Platinum. Its a case of good news, bad news.
Firmware: 2.1.12
Version: 2.0.0b9
VST3i version
Bad - Editor detection seems to be broken. When the gui opens it always sais Sub Phatty Editor is already running. I cannot access the gui. I have tried several restarts of Sonar started/stopped the standalone editor. I have not restarted the entire OS.
Good - Automation appears to work. I can create envelopes in sonar and they apply to the SPH. I can also move the knobs on the hardware. This is the first time I have seen the VST3i work, so thumbs up there. I suspect the new SDK has helped.
No if you can just fix the false editor detection…your sooo close…
VST2i version Bad - Whenever the transport starts or stops, the Sustain stage of the Volume ADSR resets to 0…every time…this may have started in beta 8, but I’ve only narrows it down in beta 9. Good - Automation still works fine.
Bad > - Editor detection seems to be broken. When the gui opens it always sais Sub Phatty Editor is already running. I cannot access the gui. I have tried several restarts of Sonar started/stopped the standalone editor. I have > not > restarted the entire OS.
I can’t reproduce this. Using 2.0.0b9 VST-FX/VST-I/VST3-FX/VST3-I in Sonar Platinum / Windows 7, they all load, no disabled GUI… Can you try to restart the OS and Sonar, Create a new project and load the plugins? Is it possible that you have another instance of the plugin loaded somewhere ?
VST2i version> [/size] Bad > - Whenever the transport starts or stops, the Sustain stage of the Volume ADSR resets to 0…every time…this may have started in beta 8, but I’ve only narrows it down in beta 9.
I don’t see it… Sonar Platinum Windows using 2.0.0b9. Sustain knobs remain at their place.
Have restarted Windows 10, started a fresh Sonar Platinum instance, created a new blank project, added a instrument track for the Moog SPHE VST3i and I still receive the “Sub Phatty Editor is already running” message. It may be a Windows 10 specific issue.
(As a software developer myself I’m curious to know what mechanism the plugins use to ‘detect’ when the editor is open - is it a registry entry?)
VST2i version> [/size] Bad > - Whenever the transport starts or stops, the Sustain stage of the Volume ADSR resets to 0…every time…this may have started in beta 8, but I’ve only narrows it down in beta 9.
I don’t see it… Sonar Platinum Windows using 2.0.0b9. Sustain knobs remain at their place.
Let me clarify. The Knob on the GUI does not reset to 0, but the actual synth does (audible).
Steps to reproduce.
Select a patch that has a long sustain (something you will notice a massive change in sound if the Sustain on Volume EG is lowered to 0).
Play some notes. All good.
Then start the transport in Sonar and play some notes…blip…blip…wheres my sound gone…boooo…
But if you slightly move the Sustain Knob on the GUI, the sound jumps back to life.
Same also if you slightly move the real knob of the hardware.
Hi Gil,
Thankyou for your patience. Your feedback has lead me to uncover the cause of both problems - human error.
So it turns out the ‘Empty Project Template’ I was starting with every time ‘wasn’t so empty’. Turned out to have a instance of the VST3i still there. I had created a template in Sonar with the synth track deleted, but it turns out Sonar does not delete the synth when you delete the a synth track (gotcha!). I had no idea…
So I have re-tested and …
VST3i - Automation works flawlessly. No more problems with automation recording. No more problems with ‘Synth Bypass’. All good.
VST2i - Everything works as well as the beta 8 did - perfectly.(no issue with the Sustain setting). All good.
There were a few issues in Sonar you mentioned in the past. Do all work correctly for you by now ?
There were:
Misc automation issues mentioned
Some component were reported to not load or run correctly
“Strange ‘Host bypass’ button issue. In both the VST3 Effect and VI plugins, Sonar incorrectly indicates a ‘Host Bypass’ whenever the plugins GUI opened.”
“MIDI forwarding does not work - when ‘MIDI Out’ of the plugin is enabled in Sonar, playing keys on SP do not appear to be received by Sonar.”
Note events from the SPH hardware have never been echoed out the Fx plugins VST MIDI outputs. I think this should only be considered a feature request, not a bug report. It is easier to achieve the same result with the new MIDI driver installed. Its not a necessary feature anymore IMO.
I have a problem after installing a driver on Windows 10: Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)
Hello Nick, and thanks for the update. Indeed there’s an issue recently found with the driver signature. We’ll be able to post a new one later today for test, which hopefully solves this problem. Keep in mind that we’re beta testing, and everything is really possible, this is why we’re working on a new version Will keep you updated.
32 bit and 64 bit VSTi Loading and working like a dream in FL12, wrapping o.k. and showing as “o.k” when scanning and verifying plug ins within FL.
I have also tried automating every parameter and multiple parameters at once with zero problems.
This is sensational!! I have not been able to stop playing around. Public release was showing all but 64 VST in error for me on 2 pcs but this seems to have done the trick for me in FL 12…good job
Will keep you updated.