Unwanted midi assignment with FCB1010

[Shin]

Hello,

I'm fairly new to Mainstage, so I apologize if this problem ends up being trivial.

I have a problem that no matter what CC# I assign to my FCB1010 foot pedals, they will also control switching up and down between patches as well as the assigned function I try to give it. For example, I just want CC#105, which is sent from a specific pedal, to control the record button on a looper. However, when I press the pedal, it also shifts down approximately 4-5 patches. This seems to apply to all my other pedals as well.

Is there something I'm doing wrong or missing?

Thanks in advance!

[jsbaker]

A great troubleshooting tool for this sort of thing is a free utility called MIDI Monitor, which you can use to "spy on" the MIDI data being sent between devices. This will help you determine if only CC105 is being sent by your pedal, or that and additional messages.

[Shin]

Thanks, that helped a lot. I figured that the FCB1010 was sending PC signals at the same time. Now to figure out how to null those...

In terms of alternative MIDI solutions, I was also wondering if there be a way to turn off or at least override the default MIDI settings of Mainstage? I notice that when I assign a CC# to something that is already a default MIDI setting, instead of choosing the more recent assignment, it just does both. Thanks again!

[CCTMusic]

Hi

In MS 2 you can choose which device the Concert responds to Program Change messages from. Select the Concert in the Patch List, and in the Inspector change the "Device" to something other than the Port/Channel that you have the FCB attached to.


CCT

[TREATMENT]

Purchase iFCB X for the FCB1010.

It is money well spent, my friend. You can dive deep into all the functionality of your FCB, so that MS gets exactly what you want it to get.
Problem Solved.
TREATMENT

[michaelhuisman]

ditto iFCB, unless you have the UNO chip in your FCB (I do), otherwise this is the best solution. Programming an FCB via the front panel is *painful*.

The UNO chip isn't a must-have, but I wanted "stomp box mode" to be the top row of buttons.

I use the FCB as a replacement for 3 sustain and 3 expression pedals (obviously there are only 2 expression pedals on the FCB), so this is another reason why I wanted the top and bottom rows of pedals to be switched on the FCB. Minor thing, but the chip works fine for my purposes.

still, thumbs up for iFCB - I really wish they supported the UNO chip. As for programming a UNO-equipped FCB from a Mac. I never found a working solution for that and have to have an old Windows notebook just to program the FCB, *although* had I thought about CCTMusic's point, perhaps I wouldn't have needed the UNO chip. Hmmm...

I'm not sure what TREATMENT's approach is, but mine was to setup every patch in the FCB the same in terms of controllers and such, as whatever it sends I can *bend* that in MS to whatever I want it to be. There was some tricky stuff in MS though, in that MS automatically forwards *standard* MIDI CC#s to the channel strips, with multiple controllers I was getting MIDI CC# messages going thru to channel strips even when I didn't want that to happen, so... I changed the FCB to send non-standard messages (not 11, not 64...) and rerouted/repurposed those within MainStage itself and then all works *EXACTLY* as I want it to.

Others probably solved all of this differently - so do what's right for you.