Author Topic: FCBFF -- an iOS programmer for the FCB1010  (Read 757 times)

0 Members and 1 Guest are viewing this topic.

Offline Elantric

FCBFF -- an iOS programmer for the FCB1010
« on: September 09, 2015, 11:23:59 PM »
FCBFF -- an iOS programmer for the FCB1010



I've wrapped up my FCB1010 programmer; the FCB1010 is a MIDI foot pedal from Behringer.   The app works with the stock Behringer firmware (no Uno chips, or any of that jazz).  We're making it free for a few days, so if this is something you'd be interested, now would be a good time to grab it.  Many thanks to the folks  (particularly Mel from Wabbit Wanch, who's behind the excellent iFCB for the Mac).


We've also put our pitch-to-MIDI app MIDImorphosis on sale:


And we're the same folks behind Apollo MIDI over Bluetooth, which we've made free:


I do much of my guitar playing through iOS apps (some very nice amp simulators are available), and I generally use Apollo on my phone to set up a wireless MIDI connection from the FCB.  This leaves the dock port on my iPad open for the guitar interface (Apogee FTW!), and I can use the FCB to switch patches, control Loopy, and so on.


Give me a should if you've got questions!





Offline jem7sk

Re: FCBFF -- an iOS programmer for the FCB1010
« Reply #1 on: September 10, 2015, 05:09:45 AM »
Wow.. this sounds awesome!  Thanks for sharing.

Offline whippinpost91850

Re: FCBFF -- an iOS programmer for the FCB1010
« Reply #2 on: September 10, 2015, 11:06:04 AM »
Just saw the Email looks very interesting

Offline sixeight

Re: FCBFF -- an iOS programmer for the FCB1010
« Reply #3 on: September 10, 2015, 11:59:20 AM »
I did grab a copy, but I have the uno chip, so I don't think I can use it...
I haven't used the fcb1010 for a long time anyway. The V-Controller does so much more...

Offline Elantric

Re: FCBFF -- an iOS programmer for the FCB1010
« Reply #4 on: September 10, 2015, 12:09:13 PM »
But I think it's important they specify the minimum "Stock Behringer FCB-1010 firmware revision" version which is compatible with  FCBFF
The very early 1998 era FCB-1010 firmware was very crippled and nothing like the current stock firmware in a 2015 Behringer FCB-1010 - thus the reason UNO ROM became so popular

Offline Elantric

Re: FCBFF -- an iOS programmer for the FCB1010
« Reply #5 on: September 11, 2015, 12:09:51 PM »
FWIW - for those who do not own the latest official Behringer 2.5.1E EPROM for FCB-1010 - they can be ordered here for $10.95

I admit Ive never used the current "Stock" FCB-1010 EPROM  - they have added many features over the years  - like a MIDI merge function

FCB1010 User Group at Yahoo

« Last Edit: September 11, 2015, 12:28:30 PM by Elantric »

Offline whippinpost91850

Re: FCBFF -- an iOS programmer for the FCB1010
« Reply #6 on: September 11, 2015, 12:42:36 PM »
Don't forget this programmer for stock chip is still free for the moment

get it here

Offline Elantric

Re: FCBFF -- an iOS programmer for the FCB1010
« Reply #7 on: September 11, 2017, 05:58:21 PM »


Focusrite and many other brand name companies sell a number of audio interfaces with MIDI tacked on. If you read all the tech specs for the MIDI portion, you'll find there isn't any. There's no reference that the interface meets any MIDI specification.

Let's start with MIDI itself.

There's two kinds of MIDI. The simple "dumb" kind that consists of 3 byte commands. Like "program change", "controller change" and "note". Almost every interface, even the off shore junk ones will work with this type of MIDI in and out. Of course, there will probably be some latency and jitter, but unless you know how to measure it, you'll just assume there's something wrong with your software from time to time. However, it's not your software.

The second kind of MIDI is the portion of the specification that deals with SYSEX. SYSEX is a manufacturer designated data block. It can be literally any size and contain any data the company wants. So presets, voices or other things that like that can't be programmed or described in three bytes are handled by these SYSEX data blocks.

Now we move on to the Interface.

There's two kinds of MIDI interfaces. The first type is the one that comes with a software driver you install to take advantage of whatever the interface has to offer. Be that audio, MIDI or some combination thereof.

The second kind is commonly called a "class compliant" interface and advertised that no drivers are needed. This type of interface uses the routines that are embedded in the OS (Windows or Mac) to handle all the input and output. If the OS doesn't handle a particular type of data, to bad for you.

If you download manuals for audio interfaces with add-on MIDI and read the fine print, you can normally find a section that says something to the effect that "This interface is class compliant and no drivers are needed to use basic MIDI commands. If you require SYSEX or long SYSEX messages you will need to install the Windows driver." Specifically Windows is mentioned because the OS drivers don't have SYSEX capabilities. Mac is never mentioned because...well...I suspect the companies assume that Apple has some sort of SYSEX capability. Which, as it turns out, is partially true.

On the Mac, the COREMIDI routines will handle SYSEX, to a certain size. Once that size is exceeded the interface has to handle the data stream quickly and efficiently. Or data will be lost, corrupted or quite simply, ignored.

The FCB1010 uses SYSEX and requires 2,352 bytes in a single block for programming. MIDI interfaces, the not so stellar ones, can handle, maybe, up to 255 bytes. Anything beyond that is a recipe for failure.

If you look at our working/non-working MIDI interface section here, you'll find a LOT of audio interfaces with MIDI are, MIDI SYSEX challenged. Or to put it bluntly, junk. At least when it comes to MIDI.

I recently got a Focusrite Pro 24 interface and found, like many others, MIDI SYSEX isn't handled. No amount of coding could make it work. So I emailed Focusrite tech support. Who seem to be rather slow in responding. I estimate if I paid them at the same speed as they provide support, they'd be out of business tomorrow. However, they did answer. Even if it took over a week.

If you're thinking Tech support has all the answers, ah, no. I've gotten the SAME LIP SERVICE from M-Audio, PreSonus and now Focusrite. This is the diaper policy reply from Focusrite support:

There is a known problem with sending large amounts of MIDI data from the unit's output and it is something we are looking at fixing. In the meantime I would advise you to carry on using one of your dedicated MIDI interfaces until this has been fixed.

Last time I got a message like that was from M-Audio. Took them almost two years to fix it and before they did fix the driver, they discontinued the interface. The Pro 24 isn't a new interface, it's been around a while. But, suddenly, NOW, they are looking at fixing it? No time line given. I should trust them. Because they didn't get it right the first time.

I was once under the wrong impression that if no one bought an interface, they would fix it quickly. No, what they do is discontinue it, redesign it slightly, repackage it, and use the same buggy hardware/software that never worked before to attract new buyers who, like me, assume they finally fixed the issues.

So what can you do? Well, you can email tech support and tell them. Maybe if enough people do that it "might" make a difference. I'm still guessing no because my experience is once they have your money they don't want to see you again until you have more money to donate to them.

Or you can simply assume, and in most cases you'd be right, that the MIDI interface on your audio interface is MIDI challenged and ignore it completely. By not expecting anything of it, you'll never be disappointed.

If you're in the market for a NEW MIDI interface, a dedicated one is the best solution AND, I can't stress this enough, do one of two things:

1. Buy the interface locally so you can return it if it doesn't work with SYSEX.
2. eMail the company and specifically ask if the interface has the ability to handle 2,352 byte SYSEX messages in a single block.

By doing one of those two things you'll save yourself a lot of time and aggravation in the present and future.

Oh, and if you're interested, I returned the Pro 24. I don't buy interfaces on speculation and promises.