Moog Music Forum

Hi Amos,
My first feedback on 1.2.6:
When switching to a preset sometimes first note played is not heard (or maybe filter is very low?)
Issue in relative mode not "totally" solved if osc knobs are not far from 0 i.e when you have to turn them just a bit to go to 0 then you can still hear a sound

I am now waiting for the editor as well!

Thanks Amos. Sorry, I didn't catch that 1.2.6 update until today.

Ver. 1.2.6 appears to have solved all the issues I've encountered while playing. However, there are two minor ones during playback.

With Local Controll off while recording:

- Octave buttons & lights now behave as expected while playing, but during playback there is no change in their corresponding lights. Not a big deal though, but it would be usful feedback.

- 1.2.6 fixed the Volume bug, but now, during playback a second one has developed. There is a slight zipper effect going on as values increase and decrease. As if the pot was dirty or the midi was transmitting at a lower bit rate. It's not smooth anymore.

Sub Phatty Firmware ver. Beta 1.2.6
OS X 10.8.4
Logic 9.1.8

ul303 wrote:Hi Amos,
My first feedback on 1.2.6:
When switching to a preset sometimes first note played is not heard (or maybe filter is very low?)
Issue in relative mode not "totally" solved if osc knobs are not far from 0 i.e when you have to turn them just a bit to go to 0 then you can still hear a sound

I am now waiting for the editor as well!

check your email!

for everyone: here's firmware v1.2.7 which fixes both of the above issues as well.

http://www.moogconnect.net/downloads/su ... v1_2_7.zip

Do you just want the beta Editor feedback here?

Here's the first bugs I've noticed from some quick initial testing:
* When using the Editor in a DAW (Ableton Live), changing knob values from the Editor created crackling and dropouts at one point. However, I've tried it a few times since and it's been fine.
* When using the Editor in a DAW (Ableton Live), changing knob values from the Editor caused stuck notes at one point. However, again I've tried it a few times since and it's been fine.

Not a bug as such but just a set up issue:
* When using the Editor in a DAW (Ableton Live), I had to set the External Instrument device to Moog Sub Phatty, and the Editor in/out to my midi interface in/out. The Editor wouldn't work set up the other way around.

Windows x64, Ableton Live 9 64bit, JBridge'd Editor (since the VST is only 32bit) Any plans to release a 64bit version of the VST?

Apart from those minor issues it seemed solid. The random button is fun for getting some weird and wonderful FX.

barryfell wrote: Not a bug as such but just a set up issue:
* When using the Editor in a DAW (Ableton Live), I had to set the External Instrument device to Moog Sub Phatty, and the Editor in/out to my midi interface in/out. The Editor wouldn't work set up the other way around.

Hi, you should have a look to the instruction file:
For the Windows VST plugin: this plugin uses a special background application to open a direct MIDI connection to your hardware, outside of the plugin host application (your DAW). Because windows is not good about sharing MIDI devices between programs, this means that you can't select the same MIDI device inside your DAW.
The reason it works this way is because the VST standard can't pass SysEx data, which is how the Sub Phatty sends and receives preset files and global data. So, in order to manage presets on the Sub PHatty from within a DAW, a separate MIDI connection outside the DAW is needed. One way to manage this is to use the Sub Phatty USB connection for communication with the Editor plugin, and the Sub Phatty standard MIDI connectors and a separate MIDI interface to connect the Sub Phatty to your DAW. Or vice versa (USB for the DAW, standard MIDI for the editor plugin).


Having said that it does not work for me within ableton 9.
Standalone version of the editor works fine but with vst I still get "hardware disconnected" message (of course usb ports are de activated in Live settings as I use them in the Sub Phatty VST editor as recommended by Amos)
There is a communication however as turning a knob on the Sub makes the corresponding knob in the Editor to move but when I change a preset editor is not updated accordingly.
Also turning a knob in the editors does affect the sound on the Sub Phatty.
So there is a connection but kind of halfway.
I will investigate further as it seems to work for you I must have done someting wrong...

ul303 wrote:

barryfell wrote: Not a bug as such but just a set up issue:
* When using the Editor in a DAW (Ableton Live), I had to set the External Instrument device to Moog Sub Phatty, and the Editor in/out to my midi interface in/out. The Editor wouldn't work set up the other way around.

Hi, you should have a look to the instruction file:
For the Windows VST plugin: this plugin uses a special background application to open a direct MIDI connection to your hardware, outside of the plugin host application (your DAW). Because windows is not good about sharing MIDI devices between programs, this means that you can't select the same MIDI device inside your DAW.
The reason it works this way is because the VST standard can't pass SysEx data, which is how the Sub Phatty sends and receives preset files and global data. So, in order to manage presets on the Sub PHatty from within a DAW, a separate MIDI connection outside the DAW is needed. One way to manage this is to use the Sub Phatty USB connection for communication with the Editor plugin, and the Sub Phatty standard MIDI connectors and a separate MIDI interface to connect the Sub Phatty to your DAW. Or vice versa (USB for the DAW, standard MIDI for the editor plugin).

I did, hence why I set up both USB and DIN MIDI connections as instructed. As I say, it works perfectly with the Sub Phatty set to send/receive MIDI via USB and the Editor to send/receive MIDI via DIN.

Here's the working setup:


My observation was just that it didn't work the other way around with the Sub Phatty set to DIN and the Editor set to USB.

Having said that it does not work for me within ableton 9.
Standalone version of the editor works fine but with vst I still get "hardware disconnected" message (of course usb ports are de activated in Live settings as I use them in the Sub Phatty VST editor as recommended by Amos)
There is a communication however as turning a knob on the Sub makes the corresponding knob in the Editor to move but when I change a preset editor is not updated accordingly.
Also turning a knob in the editors does affect the sound on the Sub Phatty.
So there is a connection but kind of halfway.
I will investigate further as it seems to work for you I must have done someting wrong...

You shouldn't be deactivating the USB ports, you need them to send/receive MIDI to/from the Sub Phatty. I bet if you reactive them it will work perfectly as you have the Editor working fine via DIN it seems. The USB connection is your missing half.

Hi Barryfell,
OK so for you it doesn't work in live with editor to USB and Sub to DIN but it does work the way around.
But for me none of these work although the standalone works fine in both USB and DIN mode

When I say I have to "deactivate" (should have said disable) USB in live settings is when using the editor in USB mode. Otherwise it tells me "can't open USB" which I can understand.

Hi guys -- next build of the Editor will merge the MIDI from the DAW into the editor plugin -- so you won't need double MIDI connections to the synth. That should work much better.

Also, I'll start a new thread for editor testing feedback...

-Amos

Hey guys, just got my sub phatty. gonna install the new firmware now

I've installed the latest firmware for my recently acquired Subphatty, hoping that it would address some bugs I've encountered, but sadly, they are still there: both amp and filter envelopes won't reset from zero or multi-trigger every time. Sometimes I've successfully applied these functions, but even then, envelopes would start from zero for a while then suddenly go back to normal behavior, all while playing (I didn't touch anything but keys). And more often than not, these functions wouldn't even turn ON from the beginning. All other shift modes I've tried (so far) works as intended.

By the way, this is the best sounding piece of gear in my studio. Absolutely amazing, I haven't slept properly since I got it.

Hello,

I notice than when I Draw automation in Ableton Live 9 with Mouse ( I prefer to do it like this, more precise for me ) this doesn't work correctly with Sub Phatty.
It only change value when it read a point but the curve between those points are ignored ? Is this something normal with Analog gear or a bug ?

Thanks.

nofuturenocore wrote:Hello,

I notice than when I Draw automation in Ableton Live 9 with Mouse ( I prefer to do it like this, more precise for me ) this doesn't work correctly with Sub Phatty.
It only change value when it read a point but the curve between those points are ignored ? Is this something normal with Analog gear or a bug ?

Thanks.

Anybody there having the same problem ?

@nofuturenocore
I'm not using Ableton, but I guess this would be a problem with any software that works with drawing automations... maybe I can test my Sub Phatty with Logic or iPad and share my experience with you. Next time I put my hands on it, I'll try it.

nofuturenocore wrote:Hello,

I notice than when I Draw automation in Ableton Live 9 with Mouse ( I prefer to do it like this, more precise for me ) this doesn't work correctly with Sub Phatty.
It only change value when it read a point but the curve between those points are ignored ? Is this something normal with Analog gear or a bug ?

Thanks.

I'm not experiencing this issue. (Live 9 x64, Win8 x64, Firmware 1.2.7)

dodecabilly wrote:I've installed the latest firmware for my recently acquired Subphatty, hoping that it would address some bugs I've encountered, but sadly, they are still there: both amp and filter envelopes won't reset from zero or multi-trigger every time. Sometimes I've successfully applied these functions, but even then, envelopes would start from zero for a while then suddenly go back to normal behavior, all while playing (I didn't touch anything but keys). And more often than not, these functions wouldn't even turn ON from the beginning. All other shift modes I've tried (so far) works as intended.

+1. I am also sometimes getting amp and filter env not resetting. Not 100% sure what I did to achieve it, but I do know I was in panel mode and then after a bunch of tweaking NOT in shift mode, the envelopes started getting weird. So then I did the shift mode "initialize preset" thing and yes that did bring things back to normal.