Slim Phatty + Pro Tools 9 works great. Can record and playback every parameter change with MIDI CC automation.
Yet when I use the VST-AU Editor (I use the Vienna Ensemble Pro as the “AU bridge” to PT9), there’s always something wrong.
(1) Since there is no “Slim Phatty Factory Preset” for the Editor, when it runs, I can’t edit anything in SP (hardware), since anything I do will change the patch into the corresponding setting in the editor, which is never a SP patch.
(2) I tried to use the “Get Patch” feature in the Editor to manually assemble and save a Slim Phatty Factory Preset bank for the Editor, but no luck, since the “Get Patch” feature doesn’t work 100% correctly. The setiings it gets from the hardware is always somewhat different from the hardware itself.
Has anyone ever use the VST-AU Editor happily? Please let me know if there’s anything I’ve done wrong, or this Editor will just end up like the Virus TI VSTi interface that stays unusable forever…
I will write to the developer of the Phatty VST Editor now. It needs to be updated to support all the features of the v3 Phatty operating system.
The VST-AU version has been in “beta” for over a year now. My hope is that the new Phatty firmware update will finally spur the editor to completion.
I guess I feel a little better to know that Access has had a similar problem… but it’s not much comfort, as I want only good working tools for Moog users.
Thanks, Amos. I just want to be able to save and organize my custom patches, as promised in the product description of the Editor.
As for now, I think I’ll just go the SysEX route and make notes. Not modern enough, but still better than in the old days.
The Virus TI VSTi interface is much worse. It reports huge latency for Pro Tools to compensate, while with realtime playing it’s far less from that value; yet what makes it unusable is that it loses link with the hardware from time to time, and once the link is lost there’s no other way to get it back than reboot the Mac and the Virus TI. (FYI, my Virus TI is always connected to the USB port on the computer, not through a hub or share the port with anything else.) And the sad thing is that it’s been like this for years. A friend of mine even sold his Virus TI because of this. The rest of us just got ourselves an USB MIDI interface.
Any update on the VST/AU Get Patch feature? I have the VST-AU version (thanks to Amos/Perry) with an SP on a Mac running Live/Logic, and still get garbled results with the ‘Get Patch’ feature.
I also have the Little Phatty Editor Librarian which appears to only read and write .lpl and .mlp files, rather then the .fxb files used by the VST/AU. As such I can store patch data via the Librarian but there is no way (that I am aware of) for the VST/AU to open bank or patch files created by the Librarian. Since the VST/AU essentially manages the patch data during a session, the only way I can see to ‘easily’ open existing Live/Logic sessions is to strictly create patches (or manually replicate from the SP knobs) using the VST/AU so that the SP remains in sync with the session plug-in instance. So much for tweaking knobs . Any suggestions?
The version that I have does not have a notable version id (at least anywhere that I see), either in the installer file or the plugin itself. I received it from either Perry or Amos in August when I emailed a support request.
I contacted Rekon audio about the issue. ‘Ianrosta’ from rekon audio stated that the 2.1.0 is supposedly available via Amos, and that it corrects some issues with Logic. However, I did not receive a follow up email about the specific issues I mentioned here.
I just bought the Editor (v. 2.1.0) not aware of these ongoing issues.
I get similar results unfortunately. Patch name field scrambled, corrupted Octave setting on OSC1, Filter KB setting etc.
Also, Phatty tends to completely ‘freeze’ when changing its internal presets with Value knob while the AU Editor is opened. When this happens its knobs and switches will stop responding. Quite frustrating. When is this going to be fixed?
Tested with Logic (both 64 & 32-bit) and Live on MacPro and MacBook Pro with Slim Phatty v.3.12.
I am astounded that Moog is selling this software. I purchased tonight, thinking that it must work as advertised, only to discover that it’s plagued with bugginess.
The standalone version causes some havoc in the mixer that turns my monitors into howling feedback microphones.
The AU version in Logic is so unstable that it causes my SP to freeze every single time I’ve tried to use it. I get garbled text in the AU LED display, and random behavior, delayed MIDI messages to the SP, and finally freezing the synth to the point where I have to quit Logic, turn off the SP and restart.
I have followed all instructions perfectly, so it’s apparent that this software is faulty, and should not be for sale. I’ll be asking for a refund right away.
I emailed rekon - the maker of the AU software and was informed that it only works when used with standard MIDI cables.
So what’s the point of a USB interface when the software doesn’t work with it? I don’t get it - if they are going to charge for the editor, which is non-standard these days, they need to make sure it works.
Hopefully this info helps someone else out.
As for me, I guess I’ll just stick with controlling it straight from logic and get a refund.
Can anyone confirm if the standard editor (made by a different developer) has the same problems?
My hope is that the new Phatty firmware update will finally spur the editor to completion.
