In this topic you can report whether a particular MIDI interface is capable of transferring the FCB1010's ultra-long SysEx messages during SYSEX SEND/RCV operations.
Based on these reports, the lists of compatible and incompatible MIDI interfaces on the FCB1010-compatible MIDI interfaces page can be expanded, for the benefit of other users.
Reports of MIDI interface compatibility with FCB1010
Tue, 2023-05-23 11:02
#1
Mark van den Berg
Reports of MIDI interface compatibility with FCB1010
Presonus Quantum 26x32 - Works for Sysex
Radial Key Largo - Works for Sysex
TENINYU USB to MIDI Cable Converter (amazon) - works for Sysex
Tested on macOS Monterey 12.6.8
Thanks for the report!
I've updated the compatibiity page accordingly. (In fact the TENINYU was already listed as compatible, but of course it does no harm to receive confirmation.)
Perhaps the tables should state the operating system(s) on which the interfaces mentioned were tested: an interface might be compatible with the FCB1010's SysEx in one operating system and incompatible in another OS (e.g. due to a faulty driver).
To keep things simple, I'll refrain from adding an "operating system" column for now, but perhaps I'll do so one day.
So it will be useful if people reporting their experiences keep mentioning in which operating system(s) they have tested their interfaces.
I had succes sending and receiving MIDI data to and from the FCB1010 using a Presonus io24 interface and a Macbook Pro with M2 chip using Venturia OS.
Thanks! I've added the io24 to the Compatible table.
I’m having good results with the CME U6MIDI Pro interface on a Mac. It can be a bit finicky to set up but it works.
This is on a 2015 Intel MacBook Pro 15” running Mojave.
Thanks! I've added it to the "Compatible" list.
I could send and receive SYSEX on the Motu M4 interface on my Macbook Air M1.
Thanks! I've added it to the "Compatible" list.
Hello,
I have today edited the FCB1010 successfully by using the M-Audio USB To Midisport Uno 1X1 interface hooked up to a Windows 10 PC
Br
Thanks for the report!
However, I'm a bit confused about the actual official name of the device you're referring to:
At the M-Audio website I found the following two devices:
"USB MIDISPORT 1x1": https://www.m-audio.com/products/view/midisport-1x1
"USB Uno": https://m-audio.com/products/view/uno
However, https://www.ebay.com/itm/115272599551 offers a device it calls "M-Audio USB To Midisport Uno 1X1 MIDI Interface Adapter 16 Midi Channel FAST".
The accompanying photo seems to show a "USB Uno" though.
So my guess is that your report is about the "USB Uno", and so I've added this "official" name to the compatibility list.
Let me know if I'm wrong.
Thanks for the excellent software, managing the FCB without it is a complete nightmare!
Confirmed working: M-Audio Air 192|6 - https://m-audio.com/air-192-6
NOT working: Behringer X-Touch Compact - https://www.behringer.com/product.html?modelCode=0808-AAE
Thanks for the report! I've added these devices to the compatibility lists.
I have (couple of years) ESI MIDIMATE eX (USB 2.0 MIDI Interface Cable with 2 I/O ports) which is reported as incompatible. I plan to buy FCB1010 to connect to PC(Win 10 64bit) and work with Bitwig, Kontakt Instruments or various other synths. Stopping, starting recording clips and add expression pedal to playing midi keyboard without expression input. Does it mean, the problem would be only that I will not be able to use FCBMan, because sending data to FBC1010 will fail ? (and I wll have to set FCB1010 manually directly on the unit) Or the incompatibility means, that also there will be problems using FCB1010 to send MIDI data (via ESI Midimate Ex) to PC applications? Thanks in advance for your opinions.
I added the MIDIMATE to the list of incompatible MIDI interfaces based on the SysEx not received by FCB topic: someone couldn't communicate FCB1010 SysEx messages, and ultimately concluded that the MIDIMATE was to blame. On this evidence, it seems indeed likely that the MIDIMATE is incompatible.
The presumed incompatibility between the MIDIMATE and the FCB1010 only concerns the 2352-byte long SysEx message defining the FCB1010's setup. So you can't use the MIDIMATE to transfer FCB1010 setups to/from the computer (using FCB1010 Manager or any other application).
This incompatibility does not concern short MIDI messages (like Control Change and Program Change), so you can use the MIDIMATE to transfer such messages from the FCB1010 to the computer.
However, it is fiendishly difficult and time-consuming to set up an FCB1010 via its own pedals. A setup you can define in FCB1010 Manager in a few minutes may take you several hours on the FCB1010 itself. So I strongly advise you to acquire a MIDI interface that can transfer FCB1010 SysEx messages.
Mark.
Can confirm that it works on Focusrite Scarlett interfaces with a Mac Mini M2 running Sonoma
Thanks! Added.
Successfully tested on the PreSonus Studio 18|10 USB!
All SYSEX SEND/RCV operations worked flawlessly.
Thanks! Added.
Curiously, even though the logo on the front of the device says "18|10", it's called "Studio 1810" in the manual and on the PreSonus website. So my guess is that the "|" in the original name quickly gave PreSonus so many headaches that they dropped it even before they had completed the manual
And the newer "1810c" device (the "c" standing for USB-C) says "1810c" even on the device itself.
Anyway, I've gone for "1810" in the compatibility list.