FLStudio USB to midi DirectSynth Electribe VST

[ARKO]

Hello,

I'm having a Electribe ESX-1 and EMX-1. I want to use FLStudio as my sequencer to send midi signals to my Electribe. I bought a Roland UM one USB midi interface.

1. Installed demo version of: http://www.directsynth.com/catalog/
2. In FLStudio midi settings:
2.1. Output:
- UM-One
- Selected: Send master key
- Selected: Port 1
2.2. Input:
- UM one
- Selected: Enable
- Port: 1
3. Fl studio > Channels > Direct ESX (or EMX) VST
4. Direct VST is loading and showed
5. On my Electribe
6. Patern > Shift > Clear patern
7. Midi:
7.1. Clock ext
7.2. Midi channel: 01

Now the VST say's: ESX not detected. I remeber by connecting the Electribes together I needed to go to midi utility on the Electribe, and change the midi util filter.

I already trying for some day's to connect FLStudio to my Electribe, I don't get it working. Is there someone that please can help me? I'm getting a little frustrated

Kind of regards,
ARKO

[insenico]

Try using different ports for in and out. And make sure your VST is configured to communicate with these same ports.
Filters on the electribe should be PCEN OOOO

[ARKO]

I see, you have the same setup like me. Can you please try it, and tell me how it works? The demo version is free.

How to set the midi port on the VST in FLStudio and the Electribe?

[insenico]

On the Electribe you just need to put the right Midi filters, I think it's under MIDI Utilities / Filters. You'll see PCEN (Program, Clock, Event, Notes), they all should be enabled (0000, not XXXX).

In FL studio you have two things, the main configuration and the VST configuration . For the main configuration, go to MIDI Settings, and you'll see all your devices listed, you'll find your Electribe in both lists, IN and OUT (in my case I have the Electribe chained MIDI-Thru my keyboard, so I choose that keyboard instead), and you have to select a unique Port Number, choose any number, Let's say 11 for In, 12 for out.
Then in your VST, you'll click the little gear icon (config), Processing, and under MIDI you'll see some boxes to specify the ports, select the same ports you defined for in (11) and out (12). That will let the VST know that it has to communicate with that specific hardware (your Electribe) and not any other.

I don't know what type of communication you need for that VST to work, in my case I use Notes (I can play notes from.FL to the Electribe), Clock (I have the EMX-1 in external, FL controls the time by enabling the send master clock option - SYNC), Events (I can play/stop from my keyboard)...

I hope this helps.

[ESXbae]

Hello!

Have you fixed it? I'm struggling since Weeks, tried to contact the Developers, bought the U6-MIDI PRO, which can handle SYSEX without Problems, but DirectESX Plugin says: PARTIALLY COMPATIBLE
Your MIDI interface does not handle SYSEX properly. You won't be able to use dumps and pattern name.
ESX won't be detected, but you can still control and automate all the parameters of your ESX.

But I saw that the Interface can handle SYSEX so I'm wondering why it doesn't work. Then I wrote the U6 Support, without success, they've tried multiple MIDI Devices and said it's because of the OS, tried to run on FL 9 in Compatibility Mode, no success.

I really hope for a response, I really want to use my ESX with FL Studio..

[jakasspeech1]

Hello!

Have you fixed it? I'm struggling since Weeks, tried to contact the Developers, bought the U6-MIDI PRO, which can handle SYSEX without Problems, but DirectESX Plugin says: PARTIALLY COMPATIBLE
Your MIDI interface does not handle SYSEX properly. You won't be able to use dumps and pattern name.
ESX won't be detected, but you can still control and automate all the parameters of your ESX.

But I saw that the Interface can handle SYSEX so I'm wondering why it doesn't work. Then I wrote the U6 Support, without success, they've tried multiple MIDI Devices and said it's because of the OS, tried to run on FL 9 in Compatibility Mode, no success.

I really hope for a response, I really want to use my ESX with FL Studio..

Since the developers mentioned it could be OS-related, it might be worth testing with a different version of FL Studio or on a different machine to see if the issue persists.