Page 1 of 1

Sub phatty editor in Windows standalone &DAW issues

Posted: Wed Nov 13, 2013 2:15 am
by Thomas Greco
I can't get it to function properly in Ableton or standalone. We need a big fix Amos. :( I'm running Win7.

Re: Sub phatty editor in Windows standalone &DAW issues

Posted: Wed Nov 13, 2013 2:20 am
by Thomas Greco
I was told by support to get a seperate midi interface because of windows limitations at least for the time being :? Aw man this is getting old! :!:

Re: Sub phatty editor in Windows standalone &DAW issues

Posted: Sat Nov 16, 2013 9:20 am
by barryfell
Yeah it's not an issue Moog can fix as it's a Windows issue.

You need to use MIDI DIN and USB if you want to use the editor in a DAW in Windows. It's just the way it is until Windows 9 or whatever.

Re: Sub phatty editor in Windows standalone &DAW issues

Posted: Wed Nov 20, 2013 5:35 am
by Blackout
so just to be clear...why do we need both??...because the USB works with the standalone editor and we need to use the Midi DINs in the DAW? or vice versa?

Re: Sub phatty editor in Windows standalone &DAW issues

Posted: Wed Nov 20, 2013 5:46 am
by barryfell
Blackout wrote:so just to be clear...why do we need both??...because the USB works with the standalone editor and we need to use the Midi DINs in the DAW? or vice versa?
You can use either when using the standalone editor but when using a DAW you need both. I can't remember the exact technical reason, but it's due to a limitation with Windows and MIDI.

Re: Sub phatty editor in Windows standalone &DAW issues

Posted: Wed Nov 20, 2013 8:05 am
by Bald Eagle
barryfell wrote:
Blackout wrote:so just to be clear...why do we need both??...because the USB works with the standalone editor and we need to use the Midi DINs in the DAW? or vice versa?
You can use either when using the standalone editor but when using a DAW you need both. I can't remember the exact technical reason, but it's due to a limitation with Windows and MIDI.
This was copied from another thread and while this may be a Windows limitation I don't know of any other synth that has run into this limitation.
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).

Re: Sub phatty editor in Windows standalone &DAW issues

Posted: Wed Nov 20, 2013 8:20 am
by barryfell
Yeah that's the official answer I was thinking of.

What other synths do you know of which have VST editors and don't have this issue?

Re: Sub phatty editor in Windows standalone &DAW issues

Posted: Wed Nov 20, 2013 8:35 am
by Bald Eagle
barryfell wrote:Yeah that's the official answer I was thinking of.

What other synths do you know of which have VST editors and don't have this issue?
Korg M3, Kronos

Re: Sub phatty editor in Windows standalone &DAW issues

Posted: Wed Nov 20, 2013 8:45 am
by barryfell
I see. I wonder why they don't have an issue but the Sub Phatty does.

Re: Sub phatty editor in Windows standalone &DAW issues

Posted: Wed Nov 20, 2013 9:20 am
by Bald Eagle
barryfell wrote:I see. I wonder why they don't have an issue but the Sub Phatty does.
I don't know the implementation details of either so I can only speculate. Korg installs a USB MIDI device driver and communicates with it. This driver won't be affected by vst limitations. The driver would also be the application with the open physical connection so it would be in a position to manage device sharing itself rather than letting Windows get in the way. Of course this is all just one possibility.