Hi,

I am a complete beginner in using midi.  I bought a Behringer FCB1010 on eBay with the UnO V1.0.3 to use to control Amplitube 5 on my Mac (running Big Sur).  To program the FCB1010, I also purchased the FCB/UnO Control Center version 2.  Prior to purchasing, I ran the trial version of ControlCenter which allowed you to establish a connection with the FCB1010 and upload its setups which was stated to confirm it works with your set-up.  I have the FCB1010 connected to my Mac with a USB/Midi cable  (https://www.amazon.com/gp/product/B08J6XVWFN/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8&psc=1 ) and no interface in between.  However when I try and use the Control Center to send a configuration to the FCB1010, it disconnects and I get the error "Invalid response during patchdump". FCB/UnO referred me to this forum and said to look at the Midi interface.  Since I am not using a midi interface and only a cable between my Mac and the FCB1010, will my configuration work?  Since I could upload a configuration from the FCB1010 to my Mac using the Control Center it would seem this should work.  Any ideas on what may be occurring.  Thanks in advance for any guidance anyone could provide.

Hi there. I’m not sure about Bias, but in S1, when you have the Bias plug-in window open, make sure that your FCB is chosen in the little yellow box in the upper right corner. S1 defaults to your main midi instrument or controller. You have to tie the plug-in with that external midi device through that little box in the corner.
Also, make sure you have setup all the midi message (cc#) info in the external device editor. 

BIAS FX doesn't require toggling CCs, it responds to any value sent on the assigned CC. That's why UNO is basically pointless in terms of having the LEDs track ON/OFF status.
I had a VERY quick look at the S1 manual. It looks like the FCB needs to be set up as a NEW KEYBOARD, then BIAS gets dragged to a blank spot in the ARRANGER view. But that's as far as I got. Presonus gets today's award for AWFUL MIDI documentation. It also could be a problem with the S1 version. IIRC from when I trialed the demo version, some versions don't support MIDI control of VSTs. I could be wrong though, I hated everything about S1. OP - was there a reason that you switched from Reaper? Some feature of S1 that Reaper lacks?

Hi,
I think the issue might be when sending CCs in EurekaProm it only send 127 on press and doesn't send anything on release which is common with guitar effects.  I ran into this problem when trying to get EurekaProm to do a sustain function. It would sustain on but never sustain off.  I ended up going to Uno chip.

Hey y'all. Just starting using Studio One, instead of reaper as my DAW of choice, now I cant seem to get my midi signals through to bias. 

My fcb1010 has eurekaPROM installed, and works great. When I was using Reaper, I used a second track for MIDI inputs, which then were sent to the guitar track/Bias FX.

I cant seem to find how to do that in Studio One.

In Studio One, my board is configured as a MIDI instrument, which in theory should work.

All inputs from my board are being recognized in Studio One's MIDI Monitor. The issue is when I try and assign controls to a footswitch in Bias FX 2, for example, the plugin does not recognize/receive any MIDI inputs or signals. It seems like this is just a simple set up error. Any help would be greatly appreciated!

FYI : FCB/UnOControlCenter doesn't work for the EurekaProm, only for Behringer and UnO firmware

--

Thank you all for the help, I ordered the uno2 chip yesterday, as soon as it arrives I will test it.
Thanks again.

Ah yes, it supports Start, Stop and Continue but it looks like only the TinyBox supports MIDI clock.

I use these messages successfully in UnO2:

• SendRealtime MIDIClock 110 BPM
• SendRealtime MIDIStop
• SendRealtime MIDIStart

Works great!

I don't think even UNO2 can send these messages.  Message that can be sent are
- Note ON Note Off
- CC
- Program Change
- SysEX
The message you are talking about are transport messages. The only pedal I can think of that can do this is the Nektar Pacer. There may be other.
You would need to run your FCB-1010 to some sort of translator to get the messages you want.

I DID put a request in for UNO2 to add "RAW" messages (without the F0 F7).  I would think it wouldn't be too hard but who knows.

On Mon, Mar 1, 2021 at 09:06 PM, <walfried@...> wrote:

System Real-Time Message

MIDI Implementation Version: 1.00
1.Receive Data
■ System Real-Time Message
● Timing ClockStatus     F8H
● StartStatus                  FAH
● ContinueStatus            FBH
● StopStatus                   FCH
● Active SensingStatus   FEH

Yikes!  You said  "any help is appreciated"  ...
In your post I could not read "System Real-Time Message" which for our purposes, and int the manual, are Control Change (CC) Messages.
The values above are hexidecimal  F8H , is the hexidecimal number F8, or 0xf8 if you are a programmer.
In some midi table it would be shown as 1111 1000  the binary codes for F & 8 

I think others will be better able to help you with programming. You could help by letting us know if you have found the manual https://www.behringer.com/downloads.html, and seen the programming video? https://www.youtube.com/watch?v=SYNND5nMWhc

Learning to program this thing can be challenging. I have my pedal connected to my Linux computer, and I have a program "midisnoop"  that can monitor the messages. It made finding my mistakes much easier.

I'm afraid that is not  the quick answer you hoped for, but I hope it helps.

Hi all,
I want to control (Start-Stop)a simple metronome (Boss DB-90) with the FCB1010.
It only has the following mentioned in the manual.

System Real-Time Message

Timing Clock Status    F8H

 

Start Status                  FAH

 

Continue Status           FBH

 

Stop Status                  FCH

 

Active Sensing Status  FEH

How can I program the FCB1010 to do this I'm a newby in midi and FCB1010 any help is appriciated .

Kind regards

Walfried

ok, thanks for the bug report, Christopher. I will look into this as soon as possible, the good thing is that you found a way to work around it for now. 

Hey Christopher,

your answer led me to the solution! It seems like the first Bank must not send any Midi & Wait Controls, because that will somehow put the fcb1010 into a 88-deadlock right after sending the setup, when it tries to initialize Bank 01.
So my walkaround is to simply add an EMPTY first bank without any INIT_BANK, and only start my Bank setup with Bank 02. At least for my needs, this is acceptable. :-)

Thanks a lot for all the quick answers, you guys are awesome!

No, it was just a guess.  I think in the Uno2 manual it says to have MIDI thru disabled when sending a configuration.  Maybe I'm wrong though. I'm not having any issues in programming my FCB1010 and I never have MIDI thru enabled (except when I tested it for compatibility on the web UNO2). In that I had to have MIDI thru set for it to pass the UNO2 test.

This might be the same bug I found a whole back and totally forgot to report.. sorry! I am trying to remember the trigger, but I know it had to do with sends and waits on initialization.