This thread is not for the Sub Phatty - it is for the Little and Slim Phattys. Good ideas though!
David
NZ
My suggestion is to get a firmware update that get oscillator two in a more stable tuning to oscillator one. Can this be done?
I love the sound of my slim phatty, but it is frustrating when I save a patch where the two oscillators are in tune, and when I later choose this patch oscillator two has drifted out of tune.
Any revised predictions on when the next stage/slim update will arrive?
this year some time… I might do a quick bugfix update soonish (like, next month or so) - at least to patch the vulnerability to MIDI Time Code messages.
Thank you.
Thanks Amos 
Not sure if this would relate to my current issues but hopfully so.
Since the latest Tempest OS update allowing for sequencing external gear, I have been going midi out from Tempest to midi in on my SlimPhatty.
LOTS OF FUN!
I have the arp and lfo clock set to external on the SP.
And I go out from the SP Midi Thru to sync other gear.
When playing the Tempest pads the SlimPhatty often hangs as if a note is being held. The Tempest pads then trigger the SP in reverse, and if pushing a pad is note off and release is note on.
Currently I just toggle the SP arp on and off right quick when this happens.
At first I thought this maybe a Tempest issue, but only the SP responds like this, so I am assuming this is some kind of midi issue with the SP.
So when you say the “vunerability to MIDI Time Code messages,” could that be whats causing this?
Thanks AMOS!
Sorry if I’ve missed anything but, with the discontinuation of the LP does that mean we’ll never see another firmware update? There are still some things in this thread that really should be addressed.
For now, the Little Phatty OS update is still to be delivered sometime this year. Plus the discontinuation news doesn’t deal with Slim Phatty
My hope is that the slim is the saving grace for at least one more firmware update. If the newest firmware doesn’t materialize or doesn’t do it for me, I may get the usb debugger and roll back pre 3.0. Maybe just in my head, but menu nav doesn’t seem to flow as smooth for me. I’d probably end up missing at least a feature or two and updating back to newest, but I might give it a try anyway.
Will a Sub-P rack kill the slim?
[u]Hirlostek[/u] solve the missing noise source of the Little/Slim Phatty, but we desperately need an “Audio Input” level… please !
A volume control for the Audio Input is exactly the function that lacks Little Phatty-
Amos please turn this option on the next update 
New firmware for Christmas?
+1, for this gift!
Amos? Any info?
Hi, I happen to be working on Little Phatty firmware today.
I can’t control the external audio input level in firmware; it’s not possible. The external audio has no hardware VCA, therefore you must control the external signal level yourself, before you apply it to the LP. Sorry about that!
Things I am doing right now for the LP:
- trying to fix polychaining so that it never loses count of any notes
- fixing MIDI Time Code vulnerability
- reading this thread to see if there’s anything else I can do…
as usual, I have to fight for every byte of code space, as there’s really none left… but I keep finding creative ways to get a little bit more
Thanks Amos.
Hi Amos. This is great news!!
Thanks for keeping us informed
It’d be super sweet if you could squeeze LFO Rate Key Tracking in there!!!
Think I found a bug..
When I connect a midi din cable from MIDI OUT(merging the input) on my Slim Phatty-1, it sends the button messages: sync, octave, mod source and mod destination to my Slim Phatty-2 
without the SP1 set to send any CCs. All other controlls doesnt send anything, only the buttons generating CCs.
Its impossible to turn this off when using the merge function on the output..