CC #123 and Mainstage 2.1 - If it wasn't a bug before, it is now

2.01 is still on your drive.

There is always the chance you can configure your MIDI device to not send this bogus CC#123

In a perfect world, that might be fine. However, in the real world, applications need to work with whatever hardware is out there....it's pity that this mechanism (which I have used to block other MIDI messages) is apparently not working now.

I know we've been through this before, but I forget....what controller is sending a MIDI All Notes Off event unintentionally? CC#123 is usually part of a "panic" mechanism and shouldn't normally be sent.

Blueberry wrote:
There is always the chance you can configure your MIDI device to not send this bogus CC#123

Not the Roland D-50.


pancenter-

So let me see if I understand what has happened....it used to be the case that MainStage allowed everything to go through (which was often a problem) and the work around was to create a dummy MIDI device to block it.

Is it now the case with the latest version that that workaround has gone away? In which case I dare not upgrade to the new version as I will get screwed up with other MIDI events coming through that I needed to block.

Not related to the original topic: What do you mean with "aftertouch"? Monophonic or polyphonic. Monophonic aftertouch can be found in many of todays keyboards, while polyphonic is extremely rare and usually not supported by software anyway (MS 2.1 fixed some bugs regarding polyphonic aftertouch)

BTW, I've played with it and found out, that if you map it to a read-only action, like "Concert", CC#123 will be blocked. That should help you, till Apple releases a fix for the "Blocked" mapping

Let me make sure I understand this. Are you saying that one should create a device such as a footpedal, assign 123 (All Notes Off to it) in Layout mode, then in the top level folder of the Edit view, one should map it to "Actions->Concert"?

If so, then a couple of questions:
1) I've no idea what it means to map anything to the action called "Concert". What is that used for?

2) How will this mechanism work for blocking an entire MIDI port? For example, I have been having a problem with MIDI Feedback messages which I solved by creating a MIDI Activity device, associating it with the IAC port in question, and then setting MIDI thru to "Do not pass through". If that process will not work with MainStage 2.1, then how do I prevent that feedback since it's not possible to associate a MIDI Activity device with an action

True, but they're out there. The Roland A90, one of my favorites, has an interesting implementation that supports (sortof) polyphonic aftertouch on the last note played...

Mapping to 'concert' simply puts the name of the concert into the object that's mapped to it. Maybe best used with a Parameter Text object.

And it's not just that mapping that should work, but any mapping that can't be adjusted (read only), which the mapping to the concert action is. Since these actions are read only, the MIDI data will hit it and not go any further. You can then set the Text Label of the object to display 'Nothing' and you won't see the MIDI data that it's blocking.

Excellent --- as soon as I'm done with rehearsal tonight, I'm going to try the update.

Blueberry, just out of curiosity, you seem to know a tremendous amount about this stuff very early on --- are you by any chance associated with the dev team behind MainStage?

D