FCB1010 MIDI CC wrongly registering as latching

[freerobby]

I'm having the same problem described here: http://forum.ableton.com/viewtopic.php? ... 76&start=0

I've verified that my FCB1010 switches are not set up in latching mode. Any idea why the "Undo" command is getting triggered after two seconds as if it were a latching switch?

The original text describing the problem:

Whilst using Looper with a Behringer FCB1010 pedal, I try to overdub sounds on the original recording but Ableton automatically hits the "Undo" button after about a second of trying to overdub.

The FCB button is sending out 2 MIDI CC values, both number 8, one with value 0-127, the other with 127-0.
I use this MIDI CC configuration to control my Roland VG-99. It would be very convenient if I could also control Looper effectively whilst sending out MIDI CC information and not note information.

This behaviour is not recreated whilst using Looper with MIDI Note information, or whilst using a mouse.

I wanted to just top that thread, but it appears to be locked. Any help is much appreciated.

[freerobby]

Anybody have any ideas? Frustrating that this has come up multiple times by multiple people and nobody has ever gotten a response. If there's no solution, does anybody know if Ableton has acknowledged this as a bug?

[yur2die4]

It reacts best to midi notes instead of cc values. That is about all the advice I know of. And is already stated on that thread. I am pretty sure you can program the foot switches to midi notes.

[regretfullySaid]

It sounds like the 2nd cc is triggering the Undo but the delay is because of a quantization setting...maybe...

[freerobby]

It reacts best to midi notes instead of cc values. That is about all the advice I know of. And is already stated on that thread. I am pretty sure you can program the foot switches to midi notes.

I did see that, was hoping for a better answer. I was nervous about setting up MIDI notes because I also use a MIDI keyboard and I wanted to avoid mixing them up. Maybe I will just buy a cheap second MIDI controller and run it on a different channel to avoid any potential collisions. Thanks.

It sounds like the 2nd cc is triggering the Undo but the delay is because of a quantization setting...maybe...

Hmm. I think the delay is because the all-purpose button triggers undo if you do a push-and-hold for two seconds.

[yur2die4]

I'm assuming that the way Live interprets assigned parameters is mostly what is getting in the way. The manual mentions how Live reacts to qwerty, midi note, and cc assignments. Depending on the behavior of a cc, that type of button could have many odd reactions. For instance, from 0 to 127, then back to 0, in theory Always switches between two specific parameters. You have OFF, then ON. And you either stay ON which could be confused as being held, or you go back to OFF. With qwerty and midi note, the assigned parameter toggles between functions. Just as the synced time increments do when assigned with Simple Delay. As the primary goal of the looper is probably intended to emulate the 'one pedal does all' style of looping pedals, they probably stuck to programming that favored toggling mediums. I can't speak FOR them of course :p

Having a separate midi channel should easily resolve the issue you refer to. Or using a note in an extremely high or low register which you can never imagine yourself using. If it is assigned, you won't be able to 'play' that note. Unfortunately, if you do strike that note while playing, you'll not only not hear it, but mess with your looper :/

[freerobby]

I'm assuming that the way Live interprets assigned parameters is mostly what is getting in the way. The manual mentions how Live reacts to qwerty, midi note, and cc assignments. Depending on the behavior of a cc, that type of button could have many odd reactions. For instance, from 0 to 127, then back to 0, in theory Always switches between two specific parameters. You have OFF, then ON. And you either stay ON which could be confused as being held, or you go back to OFF. With qwerty and midi note, the assigned parameter toggles between functions. Just as the synced time increments do when assigned with Simple Delay. As the primary goal of the looper is probably intended to emulate the 'one pedal does all' style of looping pedals, they probably stuck to programming that favored toggling mediums. I can't speak FOR them of course :p

Having a separate midi channel should easily resolve the issue you refer to. Or using a note in an extremely high or low register which you can never imagine yourself using. If it is assigned, you won't be able to 'play' that note. Unfortunately, if you do strike that note while playing, you'll not only not hear it, but mess with your looper :/

Just tried using MIDI notes on a separate channel, worked like a charm. This was super helpful, thank you so much.