Why is Mainstage not filtering out unassigned midi CC

Question

torsig1967 Author

Level 1

8 points

Why is Mainstage not filtering out unassigned midi CC

Just curious.
Does anybody have a clue on why Mainstage will route unassigned Midi CC messages (on unassigned midi channels) to ALL mixerchannels?

To me it seems like an extremely stupid thing to do. There's even an option called "send to all" for the rare occasions where you WANT to send a particuilar midi CC to all channels.

But having this as the default behavior is incredibly strange. Why would anybody want this?

MacBook Pro, Mac OS X (10.4.11)

Posted on May 28, 2010 7:19 AM

Reply

Answer 1

May 30, 2010 12:30 AM in response to torsig1967

bump. i'm feeling you, torsig~> seems to be a commonly 'not answered' question. i haven't even seen the 'dummy object/instrument' workaround discussed, perhaps obliquely, except by you. The manual.... hmf. They must be working very hard on Mainstage 3 so as to make our questions moot.

Reply

Answer 2

Jul 26, 2010 11:19 PM in response to torsig1967

pffffff... meh. any answer so far? okay, okay, apple.. i get the message, i just didn't want to believe that's the intended message, but the lack responsiveness leaves no other option.. USE DIFFERENT SOFTWARE!

Reply

Answer 3

dhjdhj

Level 2

174 points

Jul 29, 2010 11:09 AM in response to jay like birds

This issue has been driving me nuts for months --- I think I might have been one of the first to discover this issue and/or post work around but I can't stand having to have a bunch of objects in my window whose sole purpose is to stop unwanted CC data from contaminating everything.

As for the comment "USE DIFFERENT SOFTWARE", there isn't anything else out that really comes close in terms of comprehensive capabilities. There are a couple of neat programs that do pieces of what MainStage can do but none of them really support large live environments and integrate a lot of external MIDI equipment well.

Reply