|Name/Version:||M4L Moog Phatty Editor 0.953|
|Description:||This is a bi-directional hardware control patch created for and tested with Moog's Slim Phatty, but which should also work with Moog's Little Phatty.
I both welcome and appreciate constructive feedback, feature requests, and especially bug reports.
DISCLAIMER: No guarantee regarding functionality or stability is expressed or implied, and by using this device, you consent to waive any liability on my part for whatever harm it may cause you. I should also probably mention I am in no way affiliated with Moog other than that I own a Slim Phatty.
- Moog Slim Phatty (Won't get far without this!)
- Slim Phatty OS 3.1.674.31 (This is what was used during development anyway)
KNOWN ISSUES: (No one's perfect!)
1) Arp clock source must be set via the hardware LCD, as the SP doesn't currently respond to MIDI requests on this CC, nor does it generate a message for this when changed via hardware. I have a post up about this in the Moog forum that has been quiet for some time. If Moog fixes this issue according to their documented spec, my UI should start working accordingly.
2) There is not currently a way to pull a patch from the hardware into the software without touching/refreshing every knob/parameter. Moog would have to implement a function to push the patch via MIDI based on a LCD menu option or a MIDI trigger. If they do this, I'll happily implement a 'receive patch' button.
1) CRITICAL - You must set the following options on your Slim Phatty hardware/LCD for this patch to work correctly.
Local Control: OFF
Send 14bit MIDI: OFF
Program Change: SND: ON, RCV: ON
2) Though optional, you probably want to send MIDI clock out to your SP (in Ableton MIDI settings) if you intend on using your set tempo to drive your Moog Arp and/or Modulation clocks.
3) Also, in case it wasn't obvious, this device needs to be loaded into a MIDI track that takes input from your Slim Phatty. You probably want to stick an Ableton 'External Instrument' device after this patch, and route the MIDI data back out to the Slim Phatty.
Personally, I choose not to take audio back in from this particular External Instrument device, and instead create a second (audio) track with another External Instrument device that /does/ return the audio. I then group these two tracks, and use the MIDI track to keep automation and note data, and the audio track to hold my bounced clips.
TO-DO: (In approximate order of completion)
- Figure out hi-res/LSB MIDI control for the couple of parameters which support it (Mod Wheel, Filter Cutoff, and Arp Clock Rate)
- Look into possible usability issues regarding parameter automation lanes and Ableton "Hot Swap" feature
- Improve the aesthetic appeal of the UI
- Investigate possible patch retrieval & storage, with or without SysEx. Probably relies on Moog helping with a few things on the firmware end.
|Live Version Used:||9.0.2|
|Max Version Used:||6.1.1|
|Date Added:||Jan 06 2012 21:39:07|
|Date Last Updated:||Jan 11 2017 17:15:03|
|Average Rating (3)||5|
|Rate this device:||(must be logged in to rate devices login)|
|License (more info):||AttributionNonCommercialNoDerivatives|
|Device File:||Moog Slim Phatty v0.953.amxd|
Login to comment on this device.[ browse device library ]