
The original Phatty lineup, produced between 2006 and 2013, consists of the Little Phatty Tribute (2006) and Stage (2007), Little Phatty Stage II (2008, with USB interface), Limited Edition, and Slim Phatty. Amazona provides a nice (german language) article.
I have no clue whether the circuitry of the Sub Phatty also was borrowed from this product line or is closer to the Sub 37 (which I sold about 5 years ago) and Subsequent 37 lineup (Synthway provides a comparison). Since I assume the latter, this posting probably does not apply to it.
According to the specs, the features of the Phatties are rather limited, so I never paid attention to them. Just recently, a friend of mine mentioned it during the conversation about the Minimoog Voyager. The Phatties are the last synthesizers influenced by Bob Moog (though he died before the release), so I decided to get one 2nd hand.
I’ve played a lot of synthesizers during the last decades, and there were only a few which were outstanding. The Phatty is one of them. Its sound engine can do only a couple of tricks more than the original Minimoog did. But its sound is completely different from what I knew from digital synths, VAs, software plugins, or even several other modern analog synths. Drift, saturation, and its feedback loop play important roles in its sound design, all elements seldom to find elsewhere. In short, I absolutely can recommend that you try this machine. Here’s a couple of pitfalls and information potential buyers should be aware of.
- I would have preferred a keyboard version, e.g. the Stage II. However, users report that the wheels and side panels get sticky and the keybed yellow due to out-gassing. So I purchased a Slim Phatty instead, avoiding those issues.
- Though it is class compliant, USB connectivity on a Mac does not work (the machine does not show up at all). Apparently macOS is quite picky with its friends. It works well on Windows, though. Mac users should use a USB-MIDI-cable attached to the Phatty’s DIN ports.
- I once had some issues with MIDI not triggering any notes. It turned out to be a phatty issue. “MIDI IN” was correctly set to “DIN/USB”, but after I changed it forth and back the synth suddenly responded to MIDI events again. This only happened once and does not seem to be a general issue.
- Tuning issues. It is common sense that the machine needs 30-45′ to warm up before running stable.
- One issue is that the 2nd oscillator is not in tune with the main oscillator, and additionally it does not scale properly over the octaves. The menu provides some calibration routines (note that the note calibration will last for about two hours), but those didn’t fix the issues. Eventuelly I noticed my machine ran firmware version 3.12, whereas the latest was 3.21. Fortunately Moog still provides it as a download. After the update, I ran the calibration process again, as adviced by Moog Tech Support and finally the 2nd oscillator is in tune. Here’s some info of the firmware release notes which may be related to the issue:
»V3.21: Bugfix update. Note Calibration would not tune all octaves if Local Control was off; also removed Local Control: “noKB” option from the Slim Phatty (which has no keyboard).«
- One further issue is its master tune, which is often not at a0 = 440 Hz. The menu provides three settings:
- Auto. Interpreting the abovementioned Moog Tech Support posting, it probably is not meant to be enabled permanently, but to be re-run every now and then after the environmental temperature did change significantly.
- Off. This deactivates the front panel pot “Fine Tune” and allows to enter a tuning offset manually using the value encoder. That’s the setting I’m using, e.g. -711.
- On. This is the setting which activates the front panel pot “Fine Tune”, so the user can tune the instrument just like it was a guitar. I don’t use it, since the pot is placed in a way that I often touch it accidentally while using the edit menu.
- One issue is that the 2nd oscillator is not in tune with the main oscillator, and additionally it does not scale properly over the octaves. The menu provides some calibration routines (note that the note calibration will last for about two hours), but those didn’t fix the issues. Eventuelly I noticed my machine ran firmware version 3.12, whereas the latest was 3.21. Fortunately Moog still provides it as a download. After the update, I ran the calibration process again, as adviced by Moog Tech Support and finally the 2nd oscillator is in tune. Here’s some info of the firmware release notes which may be related to the issue:
- Understanding SysEx dumps is important. My recommendation is to do a backup before sending any SysEx to the device, since it will eventually overwrite stuff you didn’t expect. The following is unverified but my current understanding what happens.
- “Send cur preset” dumps the currently selected memory slot. When such a dump is sent back to the Phatty, it will overwrite the currently selected memory slot. For me this was an unexpected behaviour I’ve never seen on any other synth. I expected it to be written either to the edit buffer or to the original location, but not to the currently selected location.
- “Send cur panel” dumps what other synths refer to as “Edit buffer”. It’s a bit misleading, since “Panel mode” on other synths usually means that the synth engine reflects the current position of the physical controls. Besides the menu command, here’s the command to request a panel dump via a SysEx message:
F0 04 05 06 03 00 00 00 00 00 00 00 00 00 00 00 F7 - “Send all presets” will dump all presets as one huge 0xF0 System Exclusive 0xF7 block. This should be used in case you want to share your presets with other users.
- “Send Bulk Dump” will send both all presets as well as all global settings, including the tuning tables, as one huge 0xF0 System Exclusive 0xF7 block. I recommend to use this dump frequently for personal backups. I once transferred a preset bank from the web to my Phatty, which was a bulk dump of another machine. This exchanged my global settings and tuning tables with values of another machine, so I needed to re-run the whole calibration process. My recommendation is to never share such a dump with other users.
- The various Phatty editions shipped with different factory presets. I accidentally found this link somewhere, which contains the factory presets of the Tribute, Stage, Stage II, and Slim editions. I actually want to recommend the additional material, it’s well worth the effort.
- The Phatty’s engine is quite simple, and its interface makes it easy to understand how a preset is composed. Until now, I didn’t feel the need to work with any editor or librarian. In case you want to use some software librarian or editor, here are some links.
- The soundtower editor is available as a demo version, which I recommend to try first. I used it to rename a couple of presets on the device.
- David García Goñi shares some still maintained librarian for Linux, with access to some menu parameters.
- Mougue – Big Skinny is a simple, MIDI-CC-based panel for the Ctrlr project.
- About 10 years ago, Jean Pierre Cimalando shared some editor code on Gitlab. Its source code is a rare documentation of the SysEx encoding (e.g. see tools/codegen-fmt.lisp and the generated phatty-fmt.x).


























