Mackie Control

I'm looking at adding Mackie Control functionality to the plugin, but I have no device myself and need to get in contact with someone that has.

I need more details on how certain buttons on a real device work -  if the are toggle buttons or push buttons. I also need to understand better how the DAW overlays work.

If you have a Mackie Control and want to help me with some answers, please contact me.

Hi Gunnar

I dont know if this is any use to you....
It's an explanation of assignments for each of the 8 channel decoders
They can be assigned to I/O, Sends, Cue Sends, Routings, Strip, EQ etc. etc.

Don't know if its them that you're after, or the RH side stuff [Transport/Functions etc.]

Presume you have these....
https://mackie.com/sites/default/files/PRODUCT%20RESOURCES/MANUALS/Owners_Manuals/MCU_Pro-XT_Pro_OM.pdf

https://download.steinberg.net/downloads_software/documentation/Remote_Control_Devices.pdf

Let me know what else you might be looking for, and I might be able to help [I do use the MCU PRO on Nuendo]
Andy

I had the user manual but by some reason I hadn't thought of looking into the Cubase manual, thanks.

But I start to realize that it might be over complicated, and I really don't know what I'm aiming at. I've got some questions if my plugin can act as an MCU, and I thought would be fairly simple to combine the code components I already have (button types, midi protocol and so on) and get an action that could trigger MCU commands.

But I realize that I totally lack experience on how an MCU is used, and have a hard time determine what an MCU plugin action would look like. What would an MCU user expect to find in the plugin?

The channel strips are quite straight forward, but there is so much else that I don't know what to do with...and if it's even required.

But the first question to you as an MCU user: given the existing functionality in the Cubase/Midi plugins, do you see any use for a MCU based plugin?

Few more:

http://atmanactive.me.uk/temp/Mackie_Control_MIDI_Map.pdf

http://www.midibox.org/dokuwiki/doku.php?id=mc_protocol_mappings

I do use Mackie Universal Control in Reaper, but only for basic transport stuff: stop, play, rec, rewind.

I had the midi map but not the protocol mappings - that was brilliant, thank you.

Some questions:

• Some buttons have built-in light and LEDs assigned to the - who is controlling those lights and LEDs, is it the MCU or the daw/device it is connected to?  (if you aren't connected to anything and press e.g. Solo for a channel, does the button light up?)
  
• I can't tell from the documents how buttons are acting regarding Push/Toggle/Hold functionality or if some buttons are grouped (i.e. a press of one button will disable the others in the group). I'm probably asking for a massive amount of information here so I fully understand if I don't get it  
  

If I decide to go forward with an MCU action in the plugin I'll probably start small with just the strips and the transport area.

The MCU action is starting to look OK now.

A question for someone with a Mackie Control Pro and Cubase/Nuendo:

The Shift button (when using a Cubase/Nuendo overlay) - is that a shift or toggle button? Is it like Shift on a computer keyboard where you need to keep it pressed while pressing another button or like Caps Lock where you toggle the shift state on and off?

When I send the code for the Shift key to Cubase I can see that I get a number of LED states in return. Do you get any visual feedback on the Mackie when the Shift state is active?

Hi Gunnar
Shift on MCU PRO works as PRESS + OTHER KEY rather than TOGGLE
No visual confirmation of when Shift is Active on MCU PRO

Regarding LEDs.... I presume that CUBENDO runs these...
Only some of the LEDs work under CUBENDO. I imagine their functionality varies with the attached DAW
Have you access to the Overlay for Cubendo? [Page 7 in the CUBENDO MACKIE CONTROL pdf]
Andy

Great, thanks.

I have an image of the overlay for Cubendo along with a number of overlays for other Daws. They are vastly different which indicate that everything is controlled by the Daw.

Version 2.0.0 including Mackie Control is released now.

I have successfully made a Mackie Controller fader for Cubase and works in any DAW as well. Thanks for this plugin. 

Cool

Thanks for sharing.

I was just curious if its possible to add to the Fader state display the Name of the track?

You mean to automatically pick up the track name from the DAW and display it together with the value?

I don't know if the Mackie protocol has an explicit definition for track names, I don't think so but I'll have to investigate that. Track names can be displayed in the LCD strip but so can a lot of other information so I don't know if I can see if the information is track names or something else.

Do you have the xml for Reaper? I cant seem to find it in the lists.

No I don't have any xml for Reaper...

There has been bug.. Is it with Streamdeck or the plugin. Especially if I press a key fast the plugin would crash.

If you send a log file I could have a look and see if I can see the cause of the crash.

Here's the log file

Thanks. Interesting...

I haven't seen that problem before. "Object is currently in use elsewhere" when it creates the default white background for a fader button. There is no "elsewhere" since that small piece of code is the only place that uses the object, so it must be some concurrency problem when multiple buttons access the same code at the same time. It may be as you say when you press keys fast.

Thanks for the report, I'll see if I can handle that situation in a safer way.

This is my working Mackie Controller for Reaper using the Generic xml.

arbibarbarona wrote:This is my working Mackie Controller for Reaper using the Generic xml.

How did you get the return to start button working? I'm a little confused on that one, since it's not in the mackie control transport section.