Midi mapping...

[rich_h]

For crying out loud, haven't Mackie already said that more controllers are going to be supported than are in the demo, which makes this argument somewhat moot.

[diverdee]

Have they? - if so that's a righteous move on their part, hope it's true m8.

[DHR53]

Now wait a minute... I already set up my map, I just have to keep redoing it for every edit though... just asking a question... Don't get testy with me My Edirol PCR-30 is pretty popular you know... Reason 3.0 even has a cool picture of it in the midi setup!

[bewing77]

soon as i mentioned that mackie markets it & it suports it ontheir controllers & not on others

Which is simply not true.

The ability to set up controller mappings (wich have to be redone everytime you start a new project) isn't in any way compareable with the ammount of functionality a real control surface like the MCU brings. It does quite litterally control every single aspect of your DAW, including all plugin parameters etc.. And better still, it does it right out of the box without any setup, whatsoever. This is the kind of functionality that should be implemented for other surfaces then the MCU.

And, given that the MCU alredy does it the ONLY thing that would be needed to do for this support is to change what MIDI messages that controls what function in T2.

For BCR owners: it should be possible to make a midi-ox template that translates the midi codes going to and from T2 to you BCR so that T2 thinks it's actually a Mackie C4. But you'll need the midi charts for the C4