We are starting a new beta phase for Sub Phatty firmware.
This new firmware includes bug fixes and some new features. We will detail them all soon in a separate post.
Our main goal at this point would be verifying that nothing was broken in this version, compared to the one currently in production. Once we assure that, we can go on and test the new features.
IMPORTANT: Please check for your Sub Phatty serial number. If it’s #2892 and lower and your current version is not 2.x.x, please do not install this beta, as it requires updating the bootloader first. I will provide instructions about this procedure later on.
Download:
You will need the Sub Phatty Editor in order to verify the correct firmware version, once updated.
To update the firmware, please see the following procedure:
Connect your Sub Phatty to your computer using a USB cable. Please do not use any USB hub and connect it directly.
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. This 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.8. If it says anything other than “2.1.8”, it means that the beta was not uploaded, and you will need to repeat the process from the start.
Test:
As noted, our main goal for now is to make sure that nothing was broken in this version, compared to the one currently in production. So please try to generally and extensively use your Sub Phatty, and report anything unusual. All features appearing on the owner’s manual should still work, so best thing would be confirming that against the manual.
Please report all issues on this beta forum, adding the prefix [SPH] (stands for “Sub Phatty”) to the subject line of each thread added. This will help us distinguish these posts from posts made for the other betas.
Had some time to check this out a little today and working well still. Ran the editor in both Live 9.6 and Cubase 8.5 no problems. In Cubase the editor got the hardware disconnected status after I removed and tried re-instantiating the plugin. I had to kill the port process in the taskbar to get it to come back.
Is it possible to get the editor to echo out the local midi keyboard information so we can use it to record without having to go out a physical midi out? Basically like the midi echo is now but the other way around.
Also I’m sure I’m imagining this from not having spent much time with the Sub recently (due to time constraints) but I swear it sounds better after this firmware, seems a bit more alive and crisp.
We will start a SPH Editor version soon, in which we would like to target as many stability issues as possible.
We’re also working on a new driver, which (along with this new firmware) will allow using the SPH MIDI ports both by the DAWs and the Editor plugin at the same time - as done on the Sub 37.
One other thing I forgot to ask: the editor updates when moving controls directly on the SP, but it doesn’t seem to pass this on to automation control. I have to grab the controls with the mouse directly. Is this something that can be added as well?
This is something which we’re still investigating actually, but can be worked around the following way:
In Live, enable MIDI mapping by pressing command-M, then click a knob in the plugin and turn the knob on the hardware to set its MIDI mapping. Live will now know that the MIDI CC from the hardware should be associated with the corresponding knob in the plug-in.
We will probably be able to post some more information about the firmware changes on the next beta version.
Thanks Gil. I assume for that solution you mean to have the physical MIDI out of the SP connected as well? Guess this will be easier once the ports are available internally.
I know it’s currently mapped only to filter cutoff, but are there any plans as to have aftertouch from a midi source to be assignable to anything?
That would be a great addition to the Sub Phatty’s overall sonic and musical capabilities as well as expressiveness.
Dear Gil, i really hope that means yes. And i’d really like to know the development planning for the next updates, like which new features will be added, what bugs are going to be fixed, etcetera.. would it be possible for the beta testing group to know what’s going on?
