Date   
Re: Apologies for a basic question. Can assign a switch to mute my tuner output and use the other nine to selct patches on my modelling amp?

EJ SHELDON
 

To do what you described, you would have to program pedal 10 to be the switch in EVERY bank, one bank at a time. You would also have to reconfigure the other 9 pedals to select the proper preset. For instance. pedals 1-10 currently select presets 1-10. If pedal 10 is a Switch, then you lose Preset 10. You would need to reconfigure bank 2 so that pedals 1-9 recall presets 10-19 and again configure pedal 10 as your Switch. And so on in each bank.

OR you could use Direct Select Mode, in which the UP/DOWN switches operate the Hardware Switches, and you select presets by pressing one pedal for the "10" and a second pedal for the "1". Example:

Preset 50 - first press pedal 5, then press pedal 10. Preset 38 - press 3 then 8.

To use Direct Select Mode, power on your FCB while holding the DOWN pedal. When the Green Direct Select LED lights, release the DOWN pedal and press pedal 10. It's Red LED will light. Now press and hold the DOWN pedal until the display returns to 00. You are now in Direct Select Mode. The UP pedal is Switch 1 and the DOWN pedal is Switch 2.

Apologies for a basic question. Can assign a switch to mute my tuner output and use the other nine to selct patches on my modelling amp?

DAVID JUTTON
 

I use my FCB1010 to control a Behringer v-Amp pro.  Very simple set up - I programme the patches on the V-amp and use the FCB1010 to select them,via midi, one expression pedal works as a wah and the other as volume.  I'm sure you all know this and this simple configuration is all I need.  Except one thing - I'd like to use the FCB1010 as a switch to mute my tuner output sound - the tuner is a rack-mounted Behringer and the display is on all the time.  The tuner is first in  the signal path and you can plug in a switch to mute it.  Can I programme switch 10 to toggle the mute on/off via a switch ouput and use all the other switches to select nine patches per bank?  If so how?  I did read the manual - but I am out of my depth beyond the power switch with most tech.....Any help gratefully recieved!

Set up Behringer X-Air mixer to be controlled from the X AIR app mobile device

Faith Banini
 

Do you want to set up your Behringer X-Air mixer to be controlled from the X AIR app on you mobile device? Here are simple steps to help you do just that.

https://prezhost.com/2020/04/19/set-up-behringer-x-air-mixer-to-be-controlled-from-the-x-air-app-mobile-device/
 

Re: PROBLEMS WITH POWERING UP THE FCB1010

juan manuel
 

It is version 2.51E
 
 
Another important detail that I missed, and that was where I noticed the malfunction of my unit was when updating the firmware to the EUREKA EPROM V3.2
 
Because when I put the EUREKA EPROM V3.2 and turned it on for the first time, it kept all the lights on and did not recognize the EUREKA
I turned the unit on and off several times and just recognized it, I thought it was already solved, turn off THE UNIT and when I turned it on again the same error, I had to turn the unit on and off to recognize the EUREKA EPROM V3.2, and reach the conclusion that the eureka eprom was wasted call the seller to reimburse me the money but prior to that we tried the same CHIP in his unit and oh surprise I recognized it at first, we turned off his unit and turned it on again and he always recognized it, the CHIP was fine! And I could also notice that when you turned on your unit, only the lights on the screen turned on (unlike mine, all of them turn on even the patchs.
 
It is as if it delivered more voltage or amps to turn on, I do not know, I have explored the power source and apparently everything is fine, the regulator is delivering 5v when turning on, which is what the circuit needs to work, the error comes after That may be a Condenser or a power supply supervisor, OR Maybe a bootloader for the system. I do not know, also my unit is out of warranty and I have no choice but to fix it since I need to use it with the eureka prom for its stomp box mode since I am working with ableton live and the original firmware cc does not have those qualities
 
 
 
 
Thanks to everyone for your replies
Cheers

Re: PROBLEMS WITH POWERING UP THE FCB1010

ossandust
 

Indeed, this is nothing firmware related, so changing or refitting the firmware PROM won't do anything, and it's definitely not setup related, so a reset won't change anything neither. 
The FCB1010 simply doesn't have any electronics to keep the LEDs off during startup. As soon as the microcontroller chip goes out of reset the LEDs start working normally. According to the schematics the FCB1010 has some power-on reset circuitry which keeps the controller in reset until supply voltage has a sufficient level. Apparently in your unit this takes longer than normal. That shouldn't be a problem for now, unless it gets worse (due to dried out power capacitors for instance). Then at a certain point voltage level will no longer reach a sufficient level and the unit will stop working. I personally wouldn't worry now - unless your income depends on a reliable FCB1010.    

Re: PROBLEMS WITH POWERING UP THE FCB1010

chrisw_63
 

That is not a great idea.  First, we are not in the UnO forum, and the O.P. didn't say the chip has ever been replaced.  Next, the chip is an EEPROM, and has no way of holding a charge that would need two hours to dissipate.  Finally, you run the risk of damaging the chip with static.

Has it always done this?  And, if you have the FCB1010 open to check voltage, you should be able to tell us the firmware version.  It should be printed on a sticker on the largest chip in there, which is the EEPROM. 

Re: PROBLEMS WITH POWERING UP THE FCB1010

Juan Pablo Mora Ibarra
 

Try taking the chip out for at least 2 hours, then put it back and start by resetting the FCB, and/or autotest,
Please let us know if works


Juan Pablo Mora Ibarra



El 16 abr 2020, a las 13:06, jmanuelcapchaflores@... escribió:


greetings to all
 
When you turn on the unit, all the LEDs on both the pedals and the display automatically light up and after a moment it starts normally
 
I would like to know if anyone knows how to solve this detail?
 
I have checked the transformer and it is delivering 9v ac and the regulator (T805) is delivering 5v dc, apparently the source is fine.
 
 
What could it be?
 
 
 
I attach a photo



<WhatsApp Image 2020-04-07 at 9.38.23 AM.jpeg>

Re: PROBLEMS WITH POWERING UP THE FCB1010

juan manuel
 

if I have already reset it several times but continue with the same behavior
 
Any other recommendation ?
 
 
Cheers

si ya lo reinicié varias veces pero continúo con el mismo comportamiento
 
Cualquier otra recomendación
 
 
Salud

[Note: some edits and message merging made by Moderator]

Re: PROBLEMS WITH POWERING UP THE FCB1010

EJ SHELDON
 

Whenever the FCB begins to behave weirdly, the first thing to do is a 1+6 factory reset.
If that doesn't fix it you've probably got a serious hardware issue.

PROBLEMS WITH POWERING UP THE FCB1010

juan manuel
 

greetings to all
 
When you turn on the unit, all the LEDs on both the pedals and the display automatically light up and after a moment it starts normally
 
I would like to know if anyone knows how to solve this detail?
 
I have checked the transformer and it is delivering 9v ac and the regulator (T805) is delivering 5v dc, apparently the source is fine.
 
 
What could it be?
 
 
 
I attach a photo



Re: Conflict with controllers in Ableton? FCB1010 midi mapping works then fails

EJ SHELDON
 

On Fri, Apr 3, 2020 at 05:32 PM, <lenbrowncce@...> wrote:

So this thread went above my head a few posts ago.  But I am still left with the same problem:

 

I would like to use button 6 to arm a track, button 1 to start recording a clip, and do the same thing with the other tracks to build clips in a scene.

 

Can anyone help? 


This is how I'm using what I've learned so far:
 
Attached there's a sysex, a ControlCenter sysex, and screenshots of the sysex in ControlCenter and Ableton's MIDI configuration.
 
Here's how it works:
 
FCB Banks:
 
00 = Pedals 1-4 select Tracks 1-4 in Scene 1
01 = Pedals 1-4 select Tracks 5-8 in Scene 1
02 = Pedals 1-4 select Tracks 1-4 in Scene 2
03 = Pedals 1-4 select Tracks 5-8 in Scene 2
04 = Pedals 1-4 select Tracks 1-4 in Scene 3
05 = Pedals 1-4 select Tracks 5-8 in Scene 3
06 = Pedals 1-4 select Tracks 1-4 in Scene 4
07 = Pedals 1-4 select Tracks 5-8 in Scene 4
08 = Pedals 1-4 select Tracks 1-4 in Scene 5
09 = Pedals 1-4 select Tracks 5-8 in Scene 5
 
Pedals 1-4 select a Blank slot, or start playing a slot with a recorded clip.
Pedals 6-9 ARM whichever four tracks are active.
Pedal 5 Starts the active Scene, which will commence recording on whatever tracks are ARMed.
Pedal 5 (second press) Stops recording on ALL Clips and goes immediately into Playback mode.
Pedal 10 Stops everything.
.
 
Exp Pedal A is Master Volume.
 
The biggest drawbacks (to me) are:
 
Only 5 Scenes - 40 clips - accessible. I can work with that!
Starting a Scene starts the Transport, but Stopping All Clips does not stop it. It doesn't affect anything, it just runs on and on until you manually stop it. I use a Korg nanoKontrol2 for a control surface (along with my APC mini), so I just hit the STOP button on that, no mouse required.
 
The whole thing runs on NOTEs. The Notes I used roughly correspond to the Grid Buttons on my APC mini. No idea how that relates to your controller.
 
IMPORTANT! (maybe)
Go into the FCB GLOBAL Settings and set the NOTE ON Value to 127.
I've been hacking at this for two days, and I THINK the NOTEs started working properly when I set the Value to 127.
 
DIRECTIONS:
 
Go to a Blank Slot. For instance, Bank 03 Pedal 3 selects Track 7 Slot 2.
Arm the track - Pedal 8.
Start recording by pressing Pedal 6.
Stop Recording and immediately start playback by pressing Pedal 6 again.
Press Pedal 10 to Stop Everything.
 
Sounds complicated, but it's essentially what you asked for, just more. Print out these directions and you shouldn't have a problem.

This is a project I've been meaning to do for a long time, but looping was never a major thing for me. Mostly I use LIVE to load up a bunch of commercial clips that I like to jam to, then reaRoute the audio to Reaper, where I have all my instruments set up. Now that I've got this working it should be fun to fool around with!


 

 

Re: Conflict with controllers in Ableton? FCB1010 midi mapping works then fails

Len Brown
 

So this thread went above my head a few posts ago.  But I am still left with the same problem:

 

I would like to use button 6 to arm a track, button 1 to start recording a clip, and do the same thing with the other tracks to build clips in a scene.

 

Can anyone help? 

 

 

Thanks,

 

Len

 

 

From: main@fcb1010.groups.io <main@fcb1010.groups.io> On Behalf Of EJ SHELDON
Sent: Friday, April 3, 2020 1:07 PM
To: main@fcb1010.groups.io
Subject: Re: [fcb1010] Conflict with controllers in Ableton? FCB1010 midi mapping works then fails

 

On Fri, Apr 3, 2020 at 09:52 AM, <jack_fenton@...> wrote:

Ableton Live I believe prefers only:

9x nn 00
8x nn 00

Unless progrrammed differently in a MIDI remote script (which is what is done  for the APC MINI which sends 8x nn 7F.

If Ableton Live does not allow for what you are sending (I believe FCB 1010 sends the first form) you can write a script as was done with the APC MINI.
There is a site 

http://www.remotify.io

that you can use to write simple MIDI remote scripts for Ableton Live.


Now that I've spent some time on this, I've managed to get it all working with NOTES from the FCB. Changing the FCB's GLOBAL NOTE ON VELOCITY setting to 127 seems to have helped.

Re: Conflict with controllers in Ableton? FCB1010 midi mapping works then fails

EJ SHELDON
 

On Fri, Apr 3, 2020 at 09:52 AM, <jack_fenton@...> wrote:
Ableton Live I believe prefers only:

9x nn 00
8x nn 00

Unless progrrammed differently in a MIDI remote script (which is what is done  for the APC MINI which sends 8x nn 7F.

If Ableton Live does not allow for what you are sending (I believe FCB 1010 sends the first form) you can write a script as was done with the APC MINI.
There is a site 

http://www.remotify.io

that you can use to write simple MIDI remote scripts for Ableton Live.

Now that I've spent some time on this, I've managed to get it all working with NOTES from the FCB. Changing the FCB's GLOBAL NOTE ON VELOCITY setting to 127 seems to have helped.

Re: Conflict with controllers in Ableton? FCB1010 midi mapping works then fails

Jack Fenton
 

The MIDI Spec allows for the following forms of Note-Off. Technically they are all Note-Off message, These are all represented in HEX.

9x nn 00 
8x nn vv

nn is the note number and vv=value The x is the MIDI channel number -1. so MIDI channel 1 note off 1 velocity 0 would be:

90 nn 00
or
80 nn 00





Ableton Live I believe prefers only:

9x nn 00
8x nn 00

Unless progrrammed differently in a MIDI remote script (which is what is done  for the APC MINI which sends 8x nn 7F.

If Ableton Live does not allow for what you are sending (I believe FCB 1010 sends the first form) you can write a script as was done with the APC MINI.
There is a site 

http://www.remotify.io

that you can use to write simple MIDI remote scripts for Ableton Live.




Re: Conflict with controllers in Ableton? FCB1010 midi mapping works then fails

Todd Marshall
 

from the peanut gallery: My compliments for your reply to this message.

/Todd

On 4/2/2020 10:53 AM, ossandust wrote:
On Thu, Apr 2, 2020 at 03:00 PM, EJ SHELDON wrote:
Are you saying that in MIDIOX, the HEX message correctly shows NOTE ON while the translation shows NOTE OFF, and HEX also shows a correct VELOCITY value of 0 while the translation shows an incorrect value of 64?
Hi EJ,

indeed, the HEX messages shown in MIDI-OX are correct, there are no bugs. It's not difficult to speak HEX, and it's good to learn those details if you want to monitor MIDI messages, MIDI-OX is the perfect tool for that : 
there's an overview table of all MIDI status messages here : https://www.cs.cmu.edu/~music/cmsip/readings/davids-midi-spec.htm 
NoteOn = 0x90 , NoteOff = 0x80, ControlChange = 0xB0, ProgChange = 0xC0   (0x... means HEX)
The lowest number of the status message byte contains the MIDI channel, which can go from 0x00 to 0x0F  (= 0 to 15), therefore a NoteOn status message can be 0x90 (for MIDI channel 1) to 0x9F (for MIDI channel 16)
NoteOn and NoteOff are 3-byte messages (status, data1 = NoteNumber, data2 = velocity). The date values are between 0 and 127, or 0x00 and 0x7F in HEX.
That's what you see in the MIDI-OX screenshot I posted :
90 64 7F = NoteOn notenumber 100 Velocity 127  (0x64 HEX = 6 x 16 + 4 = 100 decimal) 
80 64 7F = NoteOff notenumber 100 Velocity 127
90 64 00 = NoteOn notenumber 100 Velocity 0, which is correctly "translated" by MIDI-OX as a NoteOff event. 
Your MIDI-OX screenshot shows the same thing, but in decimal : 
144 1 100 = NoteOn notenumber 1 velocity 100
144 1 0 = NoteOn notenumber 1 velocity 0, correctly translated to "NoteOff"
144 56 127 = NoteOn notenumber 56 velocity 127
128 56 127 = NoteOff notenumber 56 velocity 127
The incorrect value of 64 is not in the MIDI-OX screenshot, but in the Ableton MIDI monitor. Since the alternative NoteOff representation uses "velocity=0" to determine that it's a NoteOff, there is no actual key velocity available, and Ableton just displays a random "64" value. (the value is not relevant, I think not many synths take into account how fast you raise your fingers from the keyboard...)

Some more side info about these alternative NoteOff representations :  MIDI1.0 dates from the eighties, where bandwidth was much more of an issue than today. Therefore the MIDI spec added the concept of "running status" in order to decrease the serial data traffic where possible : when sending a large number of MIDI messages of the same type on the same channel (= same status message), it is not necessary to add the status byte to each message. When the status byte is missing, the receiver will just reuse the last status byte it received. This is typically used for expression pedals or pitchbend wheels, which indeed send a continuous stream of messages with varying value but identical status message. The number of transmitted bytes is decreased with 33% by using the "running status" concept. In order to have the same advantage when playing a synth, it was possible (and preferred) to use "NoteOn velocity 0" messages on key release, instead of real "NoteOff" messages. This way you got a message stream with identical status messages and the "running status" system could do its job.  Of course all this is completely irrelevant nowadays, but that's where it comes from.  
I happen to know all about Running Status because you need to take this into account when merging 2 MIDI streams (re-insert the missing status bytes where needed). Behringer failed to do that correctly in the FCB1010, resulting in lots of hanging notes when you route a synth through the MIDI IN of the FCB1010. This bug was the trigger for me to start working on the UnO firmware, since Behringer customer support just suggested me to buy an external MIDI merge device to solve the issue. 

Re: Conflict with controllers in Ableton? FCB1010 midi mapping works then fails

EJ SHELDON
 

On Thu, Apr 2, 2020 at 09:53 AM, ossandust wrote:
It's not difficult to speak HEX, and it's good to learn those details if you want to monitor MIDI messages,

OK, I accepted the challenge and looked up how to speak HEX (math was not my favorite subject in school).
Thanks. Now I have a headache.
But I can speak HEX!
On this dismal, rainy Denver Coronavirus lockdown day I learned something!

Now I'll play my guitar.

Thanks again!

Re: Conflict with controllers in Ableton? FCB1010 midi mapping works then fails

ossandust
 

On Thu, Apr 2, 2020 at 03:00 PM, EJ SHELDON wrote:
Are you saying that in MIDIOX, the HEX message correctly shows NOTE ON while the translation shows NOTE OFF, and HEX also shows a correct VELOCITY value of 0 while the translation shows an incorrect value of 64?
Hi EJ,

indeed, the HEX messages shown in MIDI-OX are correct, there are no bugs. It's not difficult to speak HEX, and it's good to learn those details if you want to monitor MIDI messages, MIDI-OX is the perfect tool for that : 
there's an overview table of all MIDI status messages here : https://www.cs.cmu.edu/~music/cmsip/readings/davids-midi-spec.htm 
NoteOn = 0x90 , NoteOff = 0x80, ControlChange = 0xB0, ProgChange = 0xC0   (0x... means HEX)
The lowest number of the status message byte contains the MIDI channel, which can go from 0x00 to 0x0F  (= 0 to 15), therefore a NoteOn status message can be 0x90 (for MIDI channel 1) to 0x9F (for MIDI channel 16)
NoteOn and NoteOff are 3-byte messages (status, data1 = NoteNumber, data2 = velocity). The date values are between 0 and 127, or 0x00 and 0x7F in HEX.
That's what you see in the MIDI-OX screenshot I posted :
90 64 7F = NoteOn notenumber 100 Velocity 127  (0x64 HEX = 6 x 16 + 4 = 100 decimal) 
80 64 7F = NoteOff notenumber 100 Velocity 127
90 64 00 = NoteOn notenumber 100 Velocity 0, which is correctly "translated" by MIDI-OX as a NoteOff event. 
Your MIDI-OX screenshot shows the same thing, but in decimal : 
144 1 100 = NoteOn notenumber 1 velocity 100
144 1 0 = NoteOn notenumber 1 velocity 0, correctly translated to "NoteOff"
144 56 127 = NoteOn notenumber 56 velocity 127
128 56 127 = NoteOff notenumber 56 velocity 127
The incorrect value of 64 is not in the MIDI-OX screenshot, but in the Ableton MIDI monitor. Since the alternative NoteOff representation uses "velocity=0" to determine that it's a NoteOff, there is no actual key velocity available, and Ableton just displays a random "64" value. (the value is not relevant, I think not many synths take into account how fast you raise your fingers from the keyboard...)

Some more side info about these alternative NoteOff representations :  MIDI1.0 dates from the eighties, where bandwidth was much more of an issue than today. Therefore the MIDI spec added the concept of "running status" in order to decrease the serial data traffic where possible : when sending a large number of MIDI messages of the same type on the same channel (= same status message), it is not necessary to add the status byte to each message. When the status byte is missing, the receiver will just reuse the last status byte it received. This is typically used for expression pedals or pitchbend wheels, which indeed send a continuous stream of messages with varying value but identical status message. The number of transmitted bytes is decreased with 33% by using the "running status" concept. In order to have the same advantage when playing a synth, it was possible (and preferred) to use "NoteOn velocity 0" messages on key release, instead of real "NoteOff" messages. This way you got a message stream with identical status messages and the "running status" system could do its job.  Of course all this is completely irrelevant nowadays, but that's where it comes from.  
I happen to know all about Running Status because you need to take this into account when merging 2 MIDI streams (re-insert the missing status bytes where needed). Behringer failed to do that correctly in the FCB1010, resulting in lots of hanging notes when you route a synth through the MIDI IN of the FCB1010. This bug was the trigger for me to start working on the UnO firmware, since Behringer customer support just suggested me to buy an external MIDI merge device to solve the issue. 

Re: Conflict with controllers in Ableton? FCB1010 midi mapping works then fails

EJ SHELDON
 

On Thu, Apr 2, 2020 at 01:13 AM, ossandust wrote:
As all MIDI-OX screenshots show, you know exactly what's really coming out of a given device by looking at the status/data1/data2 values in the MIDI-OX monitor screen. Apparently you are confused by the fact that MIDI-OX calls the "90 xx 00" messages "Note Off", while the status message is 90, not 80, but still that is correct. The only error I see is in the Midi Monitor plugin screenshot, which shows an incorrect velocity value of 64 for the "90 01 00" message.
OK, you're getting a bit beyond me now. I don't speak HEX. Are you saying that in MIDIOX, the HEX message correctly shows NOTE ON while the translation shows NOTE OFF, and HEX also shows a correct VELOCITY value of 0 while the translation shows an incorrect value of 64? That would be two bugs in a utility that will, unfortunately, never be updated.

The very foundations of my MIDI belief system are shaken! :-)

As always, thanks for taking the time to reply. Your knowledge of this arcane subject is always enlightening! 

As it was the only one of the three MIDI monitors that I used when tracking down this problem that reported correctly, I don't suppose there's any chance that you might take the MIDI Monitor part of ControlCenter and release it as a general purpose standalone utility?

Re: Conflict with controllers in Ableton? FCB1010 midi mapping works then fails

ossandust
 

As all MIDI-OX screenshots show, you know exactly what's really coming out of a given device by looking at the status/data1/data2 values in the MIDI-OX monitor screen. Apparently you are confused by the fact that MIDI-OX calls the "90 xx 00" messages "Note Off", while the status message is 90, not 80, but still that is correct. The only error I see is in the Midi Monitor plugin screenshot, which shows an incorrect velocity value of 64 for the "90 01 00" message.

Re: Conflict with controllers in Ableton? FCB1010 midi mapping works then fails

Jack Fenton
 

The APC MINI will respond with colors to note-on messages only. Off color is note on with velocity of zero. But as you showed, when SENDING note off it sends velocity 127 (7FH).

If you need to convert messages, you might need a piece of software like Bome MIDI Translator. I use it a lot for many of my controllers and applications.