[SPHE] UPDATED: Sub Phatty Editor 2.0.0b6 is ready to test !

The Moog Forum Moog Beta Forum
1

Hello beta group,

Sub Phatty Editor v2.0.0b6 is ready to test!

Changes in this version:

All automation issues should be solved by now. Please verify and let us know if you still see any problem/s using automation.

Fixed: Recording automation, settings do not always go back to where automation started
Fixed: Automation doesn’t work well in Cubase / Sierra
Fixed: Critical automation issues
Fixed: Critical connection issues reported in Sonar
Fixed: It should be possible to only use English text for preset and folder names
Fixed: GUI corruption issues in FL12
Fixed: GUI Pitch Wheel not returning to absolute position, reflected as changes in LFO rate
Fixed: “Syncing presets” message shows Cancel button smaller then usual in collapsed mode
Fixed: Editor Standalone freezes and hangs-up. No freezing should happen anymore - please verify and let us know.
Fixed: Small value field shows in Windows when restoring GUI while in collapsed
Fixed: Windows GUI frame looks different between 1.x and 2.x, both different from OSX
Fixed: Editor doesn’t detect synth if synth turned on while app is loaded
Fixed: “hardware disconnected” shown for a second, once GET completes
Fixed: Editor loads in collapsed mode and then opens up to a full screen
Fixed: “Standalone will now close” message issues (Windows)
Fixed: Active preset should be highlighted upon loading
Fixed: Folder changed when dragging a syx file into the middle pane
Fixed: GUI should load with the same state it was previously closed
Fixed: Should ask for GET if connection is made after loading the app
Fixed: Standalone crashed once loading VST and performing GET
Fixed: Change installer “Factory Presets” to “Custom Presets”
Fixed: Rearrange message “Editor cannot connect to hardware”
Fixed: SPHE OSX installer - typo and some more text related fixes
Fixed: Change name of “Reveal in explorer”
Fixed: OSX installer says “Sub Phatty Editor Installer Installer”
Fixed: Edit cursor is black instead of white
Fixed: Make ENTER select a preset
Fixed: Rightclick menu displacement
Fixed: Change message box appearing when choosing Delete
Fixed: Load error message when hardware not found upon loading

Editor:
http://www.moogconnect.net/downloads/subphatty/Sub-Phatty-Editor-2.0.0b6-WINDOWS.zip
http://www.moogconnect.net/downloads/subphatty/Sub-Phatty-Editor-2.0.0b6-OSX.zip

Firmware v2.1.12 (unchanged):
http://www.moogconnect.net/downloads/subphatty/Sub_Phatty_Firmware_Beta_v2.1.12.zip

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.

Windows Drivers:
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 be installed only once upgrading the firmware.

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:

  1. Connect your Sub Phatty to your computer using a USB cable. Connect it directly, and not using any USB 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.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:

  1. Power off your Sub Phatty and disconnect its USB cable
  2. 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.
  3. Restart your computer
  4. 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.
  5. 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.
  6. Restart your computer
  7. 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.
  8. 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.

Thanks for your cooperation!

2

Installed and everythings fine here

3

Automation in Cubase seems a lot better. From what I could tell with the quick test I did yesterday evening, the patch returned to it’s original state where automation starts.

Will test more this evening

Good job guys, much appreciated.

4

OK, so after using it in Cubase for some time I did notice one issue.

If you create a new patch and hit the save button on the editor it just overwrites whatever preset that was loaded rather than bringing up explorer and letting you do a save as like it used to. It still does it correctly in the stand alone version, just not Cubase.

Obviously, the workaround is saving a Cubase fxb file for the patch but this way is limited to Cubase.

5

Working fine here, Only small issue I saw was when I first loaded it up and wrote some automation (cutoff and resonance) the resonance knob got stuck on the GUI but it played ok. I tried to reproduce it by starting over and it was fine. Also tried other parameters and also fine.

6

We have a reproduction of this on an old version of Cubase (5 / Windows), will look into it.

7

SAVE button functionality has changed. Currently, upon loading the Editor, if the currently loaded preset is not a hardware preset (but rather one from the custom folders) clicking on SAVE will act as SAVE AS.

If hardware preset is selected upload loading, clicking SAVE will act as a regular SAVE button, and will overwrite the current preset.

Alt-clicking or Command-clicking on SAVE button, always acts as “Save As” and should load the file dialog.

Does that work for you in both standalone and plugin ?

8

okay, I wasn’t aware of this change. ALT+ Save works as a Save As inside Cubase, using just Save works as a Save As for me on the Stand Alone Editor (Outside Cubase).

Is this how it’s suppose to work?

9

Currently, upon loading the Editor, if the currently loaded preset is not a hardware preset (but rather one from the custom folders) clicking on SAVE will act as SAVE AS. So it all depends on whether a hardware preset is selected, or a custom preset is selected.

10

Thanks and sorry I forgot to mention this was on Cubase Pro 9.

11

Thanks, added this information to the report.

12

Hi Gil,

Sorry I’ve been busy lately and not had much time for testing (or rather reporting). I have still same issues with Automation on the VST3 Instrument version under Sonar Platinum. I have not seen other reports from Sonar users so it could be that only I have such issues. Does anyone else out there have any problems with the VST3 instrument and automation?

I will not be able to test the others till the weekend…

Chris

13

LOVE U GIL, I got the Sub Phatty Editor-VI(x64) VST3 version (2.0.0b6) to open (others didn’t but I don’t mind) and everything seems to work swimmingly. Also the moog usb driver gil also helped with my minitaur editor finally recognize my minitaur. I was so desperate for a editor for the SP I started building one in Ctrlr, but yea this is great, thanks man, I’ll report back if anything funny happens.

14

Glad to hear it works for you!

But, what do you mean by “others didn’t but I don’t mind” ?

Are there any plugin components which do not load / have issues ?

Can you specify what the other problems are please ?

Much appreciated!