While the Mackie Control is supported by Cubase, the Mackie C4 is sadly not. Your program is the only tool, that can help me to solve my problem. Your video here: https://www.youtube.com/watch?v=yjgmIUIS0SI explains my problem. If i turn on the C4, the encoders behave like in your video (2´s complement example). This behaviour is useless in Cubase, as it does not offer any options for the encoders of a C4, even if they are the same, like the Vpots of a Mackie Control (shame on Steinberg). Cubase does not know, how to treat "2´s complement" encoders. The C4 also comes with a software called C4 Commander, which is normally used primaly for controlling hardware synths. I abused this program with a Bome virtual cable. I can use this cable in Cubase and have working encoders. My problem is, that the C4 Commander program only allows me to setup a Midi-out for the encoders, but no Midi-In and therefore i do not have feedback/bi-directional encoders. Anything i do with a mouse in Cubase, is not reflected on the LED rings of the C4 encoders. I try my best to explain it well enough. The C4 Commander program has of course global midi-settings (in and out), so that the program knows, how the C4 is connected. But the definitions for the encoders (you create in the program) allows only midi-out. If i use the midi-out of the virtual cable to go back into the C4, the Commander program complains that the incoming midi is not from a C4 and stop the midi-stream. I really hope you understand my problem and if not, feel free to ask :) . I do not know how other DAW controllers work, but i think that all DAW controllers, have passive encoders. You (or DAW) need to mask/define the encoders initially, to get them work properly (like you do in the video). This is one of my main reasons, why i need to use the C4 commander program. As soon as i defined the encoders, i can start to use them in Cubase. I would like to remove this necessary step, but the program also defines the LCD labels for the encoders. In fact, i am very close to be satisfied, except i do not have feedback from the DAW. My biggest hope, is that you might have a solution for me. I guess that i need to do something with the virtual midi-out, so that the C4 commander program does not complain about the midi-in (from the virtual out). Thanks in advance

Oh yea of little faith. Yes, I pretty much know what I'm doing as I've been at this stuff for a long while. ;-) Well what you ask now is not as easy as you might think. MT Pro determines the start of a message by the status byte (high bit set) and cannot break up SysEx into different pieces. I've added translators in case Cubase always sends the full 56 text bytes (plus the header and end of SysEx bytes) for each message but my guess is the length of the messages from Cubase might actually be shorter. It requires LOTS of global variables. So what you will need to do is see how long the messages are, that are coming from Cubase and take off the extra bytes from the end (but not the F7) . My guess is the messages will likely be much shorter than 56 bytes. Also, I assume we are always starting at the first byte of each line which may not be the case. The variable rr is the start byte of the line and should translate correctly if left untouched. The variable qq is the C4 display number 0x30 to 0x34 for displays 1-4. Bottom line is for every virtual Mackie device, you need to put in translators like this for every possible length of bytes that Cubase might send as the pattern and number of bytes will need to match exactly. See translaters 4.4 through 4.7 for 56 data byte data messages. We use all global variables from ya-yz y0-y1 and za-zz z0-z1. DO NOT USE THESE GLOBAL VARIABLES ANYWHERE ELSE IN YOUR PROJECT. I would suggest monitoring Cubase and see if it is sending a consistent length of bytes and you might not need 56 combinations of byte lengths for every virtual Mackie devices. You might be able to get away with just shortening the existing patterns to something much smaller. Remember the pattern length must match and the variables within them must also match. Steve Caldwell Bome Q and A Moderator and Independent Bome Consultant/Specialist bome@sniz.biz (This is my paypal account) Attachments: 1590465168011_V02_C4-2020-05-25-text.bmtp

Hello Steve, I think i understand what you are saying. That is indeed a little sad, so what is easy to see for us humans, is not easy for MTP. Damn. The next problem and that is kinda big is, i can not catch any sysex coming out from Cubase/MCU protocol. This problem is what lead me to believe, your approach will not work in first case. So first i need to know, what i am doing so fundamental wrong here. I see sysex when i turn on the C4 or the Commander software for example. I see sysex if i choose \"MCU\" from the Studio Setup preferences in Cubase and click ok. But i do not see any other sysex coming out from Cubase/protocol, once the setup is made :/ and i seriously do not know why. From what other Cubase forum members told me, this is not right. They receive outgoing sysex, each time they enter a different mode. The only difference i see is, they have a real MCU unit. Could it be that we need the stuff that is described on page 240 of the Logic manual: https://usermanual.wiki/Apple/Logic.1909626546 Since this is not really happening on my side here. This is only happening with the Commander software, but not with Cubase/MCU protocol. Since we both work pretty much handicapped: You, for not having a C4 unit and i for having only a C4 unit and by far not your experience. I have some suggestions: I have a friend, who can borrow me a MCU. I think that will help us a lot, because i can better understand the protocol and i do not work completely blind with this protocol. I mean if we are seriously need to catch any case where a sysex is send by the protocol and have a rule/translator for that case, we simply can not do this completely blind. If that makes a sense for you. So for now, i think it is better to wait until i have such a MCU unit and then continue with this project. I only have the fear, that once i have that MCU unit, you will have no time to help me further. The last thing would be, please contact me privately via e-mail, unless you have no problems with discussing fees here. I have no clue, what you would normally get for such help. Please consider that i am just a normal person with high ambitions. Covid-19 has ruined my financial situation. I have plenty of time, but nearly no income as a freelancer. Still i pretty much know, that your work should be valued, but i need to have some clue, lead, indication what would be ok for you. I hope we can find a solution that is good for both of us. If my missus would know this, she would turn the living room into a war-room... i do not care :D If this project lead to a success, i can convince other people that wants to use their C4 with Cubase to either buy MTP or collect some money from anybody who wants to use the final MTP project (like a small kickstarter project) that in the end belongs all to you. I stand to my word, just make me some offerings, that are ok for you. I also stand to my word, that i want to help you anywhere i can in this project. I feel really dumb or lik…

Hi, I do not have your email but you have mine so reach out to me there for further discussion. Yes 0x30-0x33 not 0x34.

Hi, I did a little testing this morning. It seems that Cubase likes to put out text of length 55, 3, 2 and 1 (not including Header and trailing F7) So I created 4 additional translators (for Mackie 1 only) with these lenghts and am posting it here. I also added a generic Mackie handshake answer which I use and works. I actually have a APC40 MKII Mackie emulation. I modified the incoming text Sysex from Cubase for the new device ID of 14H instead of 10H. Again, No way to completely test without an actual C4. I hope it works! Steve Caldwell Bome Q and A Moderator and Independent Bome Consultant/Specialist bome@sniz.biz I'm also attaching a text log file of the example capture I used. I was merely turning V-Pots to get updated display. This whole project should work only in Mackie Mode only (Not generic mode). Attachments: 1590518631869_cubase-output-mackie-text-2020-04-26.txt 1590518652548_V03_C4-2020-05-26-text.bmtp

I\'m so glad you guys are looking at this problem. I\'m having the same problem with my Mackie C4 and Presonus Studio One 5. I had been working with Bome MTP trying to develop presets that would help me integrate these via C4Commander software -- and then I discovered this thread! I will follow your progress with interest.. Richard.

Yes Richard, I think you mean thread and not threat but you might be right on both counts :wink: Steve

But of course! Lol. (I just corrected the typo)..

Hi! I’m an ableton and mackie MCU user, and got a C4 as part of the bargain when I bought the MCU, but later realized that Ableton does not support C4. Was about to give up when I stumbled upon this thread. My thinking is that, if you can get this to work in Cubase, its probably not unlikely that this can work in Ableton as well. Lots of frustrated Ableton users with a C4 out there who would love this to happen. Have you made any progress? All the best Jørgen

HI, I did some work for a user that has some limited functionality using the Mackie MCU protocol. In general, I can get one row of V-POTs to behave like Mackie MCU V-POT and then maybe use some of the other encoders to do stuff like faders and misc programmable CC functions. It isn’t pretty but it kinda works. The big difficulty is getting the scribble strips working like you would like. The reason is the the text length of a scribble strip on a C4 is shorter than a MCU so you need to strip a few characters. Also it is next to impossible to update all 4 rows of scribble strips (unless you hand code things in MT Pro) since Mackie MCU has no knowledge of more than 8 scribble strips. If you want, you can contact me via email and if you give me an idea of what controls you want to perform a given functionality, I can give you an estimate. The other option is to write your own MIDI remote script for the C4. It would be written in Python and be quite involved and expensive unless you wanted to just have some basic functionality. With that, basic functionality is probably more easily achieved with MT Pro anyway. Steve Caldwell Bome Customer Care Also available for paid consulting services: bome@sniz.biz

Thank you for the quick replay! I’ve come to realize that I make better mixing decisions with the computer screen off. So dream scenario would be if I could select a channel with the MCU, and the plug-in parameters of the first plugins would pop up on the C4 with scribble text. It’s possible to control plug-in parameters from the MCU with pressing some buttons, so I thought maybe it could be possible from the C4 as well if Ableton recognizes it as a MCU. However I understand that it is not so straight forward and the sollution probably will be very hacky since the MCU don’t have any awareness of more than eight text boxes. How do you go about using python to write a new controller script? Do you have anything I can read to get me started maybe? :thinking: Could possibly also try to check the interest on ableton forums to collect money to hire you to do it. Jørgen Jørgen

Mackie C4 and Cubase. How to make the encoders work?

Bome Products

FlorianBome (Florian Bome) May 1, 2021, 1:17pm 70

Just in case, there is a new solution for C4 owners, targeted at Studio One, but might also work with other DAWs: