[SPH] Editor 2.0.0rc2 & Firmware 2.2.0rc1 release candidates

The Moog Forum Moog Beta Forum
1

Sub Phatty firmware release candidate v2.2.0rc1 is now available. Note that the only change over v2.1.15, is the new version number. Please test this along with Editor v2.0.0rc2, and let us know of any critical issues that you may find, on the forum.


Download:

Firmware Updater v2.2.0rc1:
http://www.moogconnect.net/downloads/subphatty/SubPhatty%20Firmware%20Updater-2.2.0rc1-OSX.zip
http://www.moogconnect.net/downloads/subphatty/SubPhatty%20Firmware%20Updater-2.2.0rc1-WINDOWS.zip

Editor v2.0.0rc2:
http://www.moogconnect.net/downloads/subphatty/Sub%20Phatty%20Editor%20Installer-2.0.0rc2-OSX.zip
http://www.moogconnect.net/downloads/subphatty/Moog%20Sub%20Phatty%20Editor-2.0.0rc2-WINDOWS.zip

Windows drivers:
v4.35.0 (Windows 7 and up): http://www.moogconnect.net/downloads/subphatty/SHA256Driver/Moog_Sub_Phatty_USB_Driver_v4.35.0.zip
v2.23.0 (Vista or XP): http://www.moogconnect.net/downloads/subphatty/Moog_Sub_Phatty_USB_Driver_v2.23.0.zip

2

I made the update but a new problem has arised, regarding the VCA.

No matter what I use to control it (CV Input, ADSR on the Amplifier section, or Master Volume control), the VCA only jumps from zero to max, there is no in between, no gradual control. On the ADSR section the Attack section works fine, but during the Release the problem is very clear for me

Are you able to reproduce it? Or shall I try reinstalling the firmware?

3

Thanks Bicho,

I am not sure I understand from your description what the exact problem is. Would you be able to elaborate more clearly ?
Maybe a step-based scenario ?

Reinstalling the firmware might make a change.

Please let us know asap so we can target this issue if still exists.

Thanks!

4

Sorry if I didn’t make myself clear enough :confused:

In short, the VCA is messed up in 2.2.0rc1, while it worked perfectly on 2.1.15

The Release stage, as well as the output level don’t have a gradual change but an abrupt one.

When using the EP-3 on the Vol input, the sound simply begins after a certain treshold is passed with my foot, not gradually. In other words, it works as a footswitch and not an analog smooth CV

I just tried reinstalling 2.2.0rc1 and making a pot calibration to make sure the problem is there, then I went back to 2.1.15 and it works fine

5

Thanks Bicho!

Amos confirms there’s an issue in this area and is checking into it.