Expression pedal behaviour not definable per MIDI channel?

[ensho]

Hi folks,

 

I'm having trouble assigning an expression pedal to work on just one MIDI channel.

 

The layout is two keyboards, each with expression pedal and sustain pedal, one is MIDI channel 1, the other MIDI channel 9.

 

Expr. pedal for channel 1 works fine and doesn't interfere with any channel strips of channel 9. The expr. pedal of channel 9, however, involuntarily controls expression of channel strips from channel 1, as well.

 

I'm aware of the MIDI thru function in layout mode - both pedals are set to their respective channels. Also, the block function in the screen control inspector and the transform function in the channel strip inspector are not assigned throughout the concert.

 

Logic tells me they should behave identical, so it seems I'm overlooking something. Would anyone of you have an idea what?

 

Thanks in advance & Cheers from the Netherlands!

Ensho

[marcperi]

to solve your issue,

 

the pedal is assigned in layout mode...

 

You can then bypass the pedal signal filtering it....

 

check page 56 of mainstage manual, filtering midi message

[ensho]

Hi Mark,

 

thanks for your response. My question is not so much how I can work around it as why it's happening in the first place. I suppose it's a fault on my part (if not it would have to be a bug but let's not go there yet..).

 

So any suggestions what I must have done wrong are welcome.

 

Cheers,

Ensho

[marcperi]

I got similar issue with a volume pedal, that I wanted to use as volume, but sometimes also only as Wah foot controller.

Leaving his setting in layout out mode ad volume, was always controlling the general volume and the volume of each sound of the channel strips.

 

I was solving in this way:

 

1 - make a copy of your concert to make all sort of experiment

2 - with your copy concert open, remove all pedals from keyboard

3 - in layout mode disable the "learned" parameter

4 - connect only pedal 1 into the keyboard

5 - check into your phisical keyboard parameter the setting of the pedal inserted in the proper slot

6 - learn a new map

7 - check if is working properly at concert level and in every patch level

8 - now connect also pedal 2 and repeat procedure from 5 to 7

9 - If you have same problem, try to invert the two pedals in order to see if one of them is giving the problem, if not, probably you should control better the parameter inside your phisical keyboard

 

I solved my problem of volume removing the volume mapping, inside my keyboard also, and adding only a general effect control mapping. Doing this I decide time by time what I want my pedal doing and is not giving problems to concert or patches strip at all

[ensho]

Thanks for the step by step guide to this workaround. I'll try it out.

 

One always hopes not having to do it the complicated way...

 

I'm constantly saving my concerts with continuous dates and numbering as I program so I'm able to go back if something goes wrong or if Mainstage decides to be stubborn.

 

Thanks for the input.

Cheers,

Ensho

[JayBird]

Ensho, this behavior is a flaw in the design of Mainstage. No other explanation is plausible, since the purpose of MS is refining the interaction between performer and machine, and there has been a revealing silence from developers, Apple, and Logic trainers regarding this well-bemoaned problem. Workarounds for now.

 

Cheers,

Jay d'Bird

[ensho]

The 'bug' thought had crossed my mind before. The good news to me is the re-assurance of my ability to think. The bad news is having to think around one more corner in order to get stuff done in Mainstage. (And I consider getting Mainstage tame to be a big enough challenge already.)

 

Oh well, imagine us 10 years from now telling bonfire stories about the ol' Mainstage days back when you had to know the program inside-out to be able to program around it's flaws. Aaah.......

 

 

Thanks for the post, Jay.

 

Cheers from the Netherlands.

Ensho.