I’ve completed a firmware update for the Slim Phatty. Here are the changes:
Preset Name save bug fixed (this bug affects all units with OS 3.03, serial# 171 and above)
Some parameters were not updating displayed value in response to MIDI – fixed.
Osc1 and Osc2 Octave parameters now respond to CC values 0-15.
Osc2 FREQ responds more smoothly to MIDI CC modulation.
Increased MIDI input buffer size, to avoid stuck or missed MIDI notes.
Implemented all “All Notes Off” / MIDI Panic messages per MIDI spec
Tuning Scale “Root Note” now displays flats instead of sharps (Db vs. C#), to be consistent with PhattyTuner software.
USB firmware v31 fixes bug when MIDI IN data received during Slim power-on.
This forum release is the last step before we put the new firmware in production.
I (and a few volunteers) have tested it carefully, and I think this version is ready for release.
Please check it out, and post any feedback you have here. I think you’ll find it to be a very stable and useful upgrade.
You must read the included README file for firmware update instructions.
NOTE: the Mac OS version does NOT include the USB update; for some reason this update is not working via SysEx Librarian.
I’ll figure it out next week. For now, you’ll need our Windows app to update the USB. No problem updating the main firmware via Mac. The USB update fixes the problem where you get no MIDI input if there’s MIDI streaming into the Slim while you power it on. All other fixes are contained in the main firmware.
I hope you’ll have some time over the weekend to check this out… thanks very much, and enjoy!
Real Soon on the Little Phatty. Basically, it’s the same firmware… so, provided the Slim update tests well and nobody finds any bugs, the Little Phatty update should follow next week! ^-^ 0_o XD
There will be an update for Tribute but it might take a little longer… for some strange reason, sending MIDI CCs doesn’t work right on the tribute (using the same code as on the other Phatty varieties)! It seems like a weird compiler issue or something along those lines… in any case it will take additional time and resources to get right. The decision was made to go ahead with the Stage/StageII release since it’s working already, and then to continue working on the Tribute version.
I just discovered that after updating the firmware, the preset names had all turned to garbage. It would also take a second or so to “scroll” past certain presets when using the Value knob to select presets. Sending my backed-up preset list (a dump of v3.03, via SysEx Librarian) didn’t fix the issue.
After trying a multitude of things (power cycles, factory reset, going back and forth between 3.03 and 3.04), I discovered that after a factory reset and the 3.04 update, all factory presets were fine. However, it turns out that uploading the SysEx Librarian dump messes things up again. Going back to v3.03, the same issue occurred: the factory presets were A-OK after a factory reset, but after uploading my preset dump, things got garbled.
Long story short, it means I don’t have my presets at this time. I’m not sure if the problem lies with the v3.03’s ability to dump presets, SysEx Librarian’s ability to record the dump, or v3.03/v3.04’s ability to load the dump.
I’ve attached the SysEx dump to this post, in case it helps to figure out what could cause this. Moog Slim Phatty Presets.zip (7.28 KB)
I’ve been able to load my presets saved by OS 3.0.3 into 3.0.4 using Sysex Librarian without any issues. I was doing it via USB, and I have the timing set a bit slower in the preferences. I didn’t try your sysex dump though.
Works great! I’ll add that I have SN#60 and was also affected by the “preset name-save” bug. This update corrected it all the same, though! Thanks Amos!
last thing Friday evening (still at work at almost 7pm or so), I discovered that not everything was flawless when using SysEx Librarian.
Some users are reporting it may work better if you significantly reduce the transmission speed.
If you use DIN MIDI rather than USB for sending presets, it will run at a much slower (than USB) rate, and ought to work with no errors.
I’ll be looking into this in more depth on Monday… if all else fails and you have access to a PC, you can try the PC update files, which have given me no problems.
