[SPH] Sub Phatty Firmware v2.1.8 ready for test !

There will be another firmware version which fixes a specific bug related to LFO and Clock Sync, and whatever critical issues we may find in the next few days. This version will be used in production of future SPH units.

Then we plan to start a beta phase which will involve both Editor and Firmware. The addition of any new features and bug fixes is something which will be done on the fly, and based on what we found, so unfortunately it’s not possible to publicly put up such a list at the moment.

If it’s already running 2.x.x , it should be fine.

I updated my Sub Phatty from firmware 2.0.6 to 2.1.8 so far everything seems fine.

Just had a chance to update firmware, thanks :slight_smile:

A quick test shows something is a little different than before. Before there was noise if I turn all OSC and Noise to 0 with an open envelope.
If i totally close the envelope the noise becomes a pop which I don’t remember being so pronounced and maybe I actually didn’t test it that way?
However I’m 90% sure I did test modulation with Amp Decay on full, so noise it fully present with note on the ever present noise, which previously had no effect.
Now if I turn EG Amount to any value I get a whirring noise that is not affected by any modulation parameters, LFO rate or amounts. However it is effected by not pitch and also all filter parameters, so much so that that with say C3 pressed and EG Amount at -5 the whirring noise is fully present with filter fully open and totally gone leaving only the ever present noise with the filter fully closed, vice versa with EG Amount on +5 and actually hi pass filtering the whirring noise!

http://forum.moogmusic.com/viewtopic.php?t=23939 When I look at my post regarding noise issues with previous firmware there are definitely differences now. The noise is the same although OSC ever present noise is gone! Also could be subjective as its been a while since I tested the noise, I think its quieter..? Thanks :slight_smile:

Will keep playing around…

Cheers

Hugo

There’s only one way we can confirm a regression issue, and it is saving a patch which demonstrates this behavior, then going back to 2.0.3 and see if it behaves any different.

Send me a preset syx which demonstrates the issue with exact instructions how to reproduce it, and will check it here.

so far it’s working fine–all my patches seem to be in place! seems to connect to the editor software easier than before.

Thanks for the update, please keep us posted.

So far so good for me. Definite improvement with using the editor VST too! Thanks

My limited testing over the last week didn’t find any issues. And the editor is connecting and working reliably for me too.

One issue I had in the past is that is certain saved patches would not allow some parameter changes, almost as if the patches were corrupted in some way. I tried to replicate this one but failed. Did this get addressed at any point?

Will post back if I spot anything else!

What happens when you try to change these parameters ? are they always the same parameters and which ones of them ?

From memory (maybe unreliable!), I think it was amp and filter env parameters, and maybe more? They became unresponsive over both MIDI and via the panel on certain presets.

The only way to ‘release’ a preset with the non-working parameters was to copy another (working) preset over it. It happened to me a couple of times shortly after getting the unit, including with an edited version of one of the factory presets.

But I think I ended up deleting these presets - and have updated the firmware a couple of times since then. I will try to reproduce over the weekend, but I didn’t have this happen since so it might have just been ‘one of those things’ (or user error?).

John

Thanks,

There were so far a few similar reports on the same issue, but couldn’t reproduce it in-house.

We’ll really need some reproducible scenario as far as this one goes.