Mackie control protocol support

I found very nice instructions for using the Grid controllers with various DAWs. I also found some passing comments of support for the Mackie control protocol, but I cannot find any details. I would like to use the Grid controllers with Adobe Audition and Premiere Pro. Unfortunately, Adobe programs only recognise the Mackie control protocol for control surfaces. Is there some readily available configuration, or library for the Grid editor, or some other simple instructions on how to configure the Grid controllers as a Mackie control surface that would be recognised by the Adobe programs?

/Karol

Welcome to the forum!

The Grid documentation is hosted here online:

I do not see any references to the Mackie Control Protocol.

I also don’t specifically see Mackie Control Protocol here under 'What protocols are the modules compatible with?":

https://intech.studio/common/product-features

There is the VSN1 module that’s in development and I it mentions “Native Adobe Photoshop and Adobe Lightroom software integration” though I can’t speak to how that’s achieved. It also mentions that more integrations are on the way:

https://intech.studio/discover/vsn1

However, I’ll let the devs speak to any of the above. :slight_smile:

We have working implementation of the Mackie protocol, yes.

We have not tested it in either Audition or Premiere to confirm it’s working. We have tested it in DAWs like Ableton or Logic and Davinci Resolve as well. The protocol works well in the tested applications, but it’s not easy to configure.

Depending on your willingness to work with the Grid system, I can offer you the framework of the Mackie protocol through an EF44 configuration, that you’d then have to customize to your own needs.

In case you’d want a more ready-made solution, I can only echo what @_d4ydream above have already said. Wait for the software integration with Adobe, because as of now Grid is in no way easy to program for a beginner for use in Premiere or Audition.

2 Likes

No problem, I can play a little bit with the configuration. If it already works in some DAWs it should not be too complicated to customise it for Adobe applications. Now, I just need to buy two EF44, but I am having some problems with the VAT for my company. I sent a separate support request for that.

Now I have my two EF44. Please, let me know where to start with the Mackie protocol configuration.

Hi there!

Sorry for the late answer, had a hectic week.
I have a complete MCU configuration for Logic control, using two EF44s and a couple of other modules. What functions are you looking for in your 2 EF44 setup? 8channel mixer is an obvious one, but which parameters would you like to utilitze and control using the encoders and encoder buttons?

Based on your reply I can modify the Logic controllers and upload the setup for you.

First my initial idea for a simple 2x EF44 setup: 8 mixer channels (ideally one master, the right-most one) with the encoders for panning and click for mute. If this works then we can see what to add to other pages.

What modules do you have in the more complete DAW control setup?

Here’s how it works right now. Although there are still a couple of workflow quirks to iron out, it does a whole lot already:

The configs in Profile Cloud are called: Logic Control MCU (no description yet).

When the setup is used with only 2 EF44s, the top pots work as a way to switch between modes of the Vpots. In order from left to right these are:

  • IO
  • Sends
  • Pan
  • Plugin
  • EQ
  • Dyn
  • Fader Bank Left
  • Fader Bank Right

I cannot see this profile in the Profile Cloud. Do I need to enable some special settings to see it.

Profile Cloud did a funny and never made the configs public even though I’m sure I clicked the option.
You should be able to see them there now!

Very good news from my side on using my two EF44 in Adobe Audition. The faders work nicely in the mixer and the encoders do panning. The encoder buttons do not seem to do anything.

I have also tested in RME TotalMix FX. It nicely recognises (and displays) that there are 8 faders and they work as expected. The encoders also work as panning. However, the encoder buttons seem to perform various “random” actions.

This is a great first step. What would you recommed as the next step? Is the idea to have two EF44 and one BU16 for a more complete MCU setup, or will you, for example, add new “pages” that will modify the functionality (it looks like there only a single page)?

Also, looking at the new LUA code, I cannot find documentation for some of the new functions, for example tracks(num, val) or the test for tm~=nil.

1 Like

Well as a next step, it would be really nice if we could tailor the setups to these use-cases.

For example, what kind of actions would you expect from the encoder buttons? Currently they switch between the above described modes. They could also act as Vpot presses, if you set the BU16 variable to 1 in System Setup.

I think, I need some time to play with Audition and RME TotalMix to see what is the best setup for them. My current feeling is that I will need to buy the BU16 to get a more practical solution. I will get back.

1 Like

This does not work with Logic 12.2 and Grid Editor 1.6.5 with firmware 1.5.1
Fader and poti both change track volume. Pressing poti does not change anything. From time to time I get a panning change with the poti and when I press it then it gets back to change track volume and stays there even if I press poti again.

Pretty sure that’s because the controller started up in Flip Mode.

You should be able to adjust that under Control Surface settings within Logic.

Flip mode is off. But now I understand your upper description. You don’t step through the assignement list but select the controller destination for all channels with the pressing of the different potis.

You can learn a lot from the Logic Pro Controller Assignment view. But it is still confusing how the controller setup switches with each press on a poti.

It is still unclear why the destination of control switches when I select a different track by mouseclick in the mixer view. also pressing one poti seems to toggle between two setups of destination. very confusing! not usable from my point of view. is there any documentation around?

I use two EF44 and one EN16.

This is because we’re trying to fit the MCU+Logic Control script into a controller with much less feedback and control options.

I feel your pain. The Logic Control configuration for Grid was made a long time ago as a proof of concept and then streamlined, but is old and is not correct compared to an actual Mackie Control.

I want to remake it from scratch, but had no real access to Logic for a while. I’m on a script making binge at the moment, just finishing up Ableton Last Touched/Hover mode, so I could move onto Logic next and tackling this.

What is your use-case for Logic Control? An 8 track mixer with pan?

Good question. 8 tracks is not enough. It would beawesome to step through the channels by pressing one of the EN16 potis (or a bbutton on a VSN1) to jump to the next group of 4/8 channels (depending on if you have one or two EF44 connected)?
visual feedback would be very helpful, if possible. I will add a VSN1 to the setup so there would be a jogwheel and a display, too. this would be a very compact Logic controller!

| EF44 | EF44 |
| VSN1 | EN16 |

Is it best to use the Mackie compatibility or is there an alternative option?

Now for example the Mackie protocol doesn’t support controlling more than 8(+1) tracks at the time. You are only allowed to change between banks of 8 faders — nothing else.

In my view the best way to go about this would be to just abandon the Mackie protocol altogether. In 2026 it feels like a sacred cow for big corporations with fixed products, afraid of dropping compatibility with old software. And it’s wholly different in its design compared to our modular, completely customizable system.

But of course, it’s that compatibility of the Mackie that a lot of people appreciate in MIDI controllers. So this is a hard nut to crack.

I will make an update post here about this next week when I had the time to look into it.