any chance you could do some Jiggery-Pokery for the Mackie C4.
Would love to be able to map it to the pro-channel eq and comp etc.
 

azslow3
Do you mean you see 5 MIDI messages every time you move fader on Nano Kontrol:
(Note: touch on, Note: select pressed, Note: select released, PitchBend: value, Note: touch released) ?
I can not find any information in the Internet about the topic, except for Logic Control.
Good to know.

Its more like 3 messages if the track you're on isn't the "active" track :
 
90 18 7F  Note On (Track Select button press)
90 18 00  Note Off (Track Select release)
E0 62 62  Pitchbend (Fader move)
 
...and only one if it's already the active track:
E0 60 60
 
Each corresponding fader move on the active track sends out single pitchbend messages.
 
The select buttons themselves send out the same first two messages as the fader:
90 18 7F  Note On (Track Select button press)
90 18 00  Note Off (Track Select release)
 
Before I look at this I just assumed the Mackie was sending out cc#7 on 8 channels... I was wrong!
 
FYI - there's links to more info on the spec here: https://forum.cockos.com/showthread.php?t=101328
Although the docs are for the HUI, the protocol hasn't changed much.
 

Freex
any chance you could do some Jiggery-Pokery for the Mackie C4.
Would love to be able to map it to the pro-channel eq and comp etc.
 

As the Cakewalk Surface SDK is published openly, they've been pretty strict in limiting the scope of what it can change in Sonar. As far as I can see, it's limited to the WAI interface and that's it. You'll notice that the ACT checkbox is disabled when you add the MackieControl in control surfaces, so it's not even as flexible as ACT.
 
There's an earlier thread that explains how someone is doing this via MIDI learn:
http://forum.cakewalk.com/How-do-I-use-ACT-with-Mackie-Control-Pro-Channel-modules-m3029290.aspx
 

Freex
any chance you could do some Jiggery-Pokery for the Mackie C4.
Would love to be able to map it to the pro-channel eq and comp etc.

Where you was before? I have started my Mackie mod long time ago, asked what people want, got silence... stopped the development. You can control ProCh EQ/Comp with MCU: http://www.azslow.com/index.php/topic,341.0.html
I remember someone with C4, but there was no cooperation in testing and I do not have C4.
WARINING: without my mod, attempts to control ProChannel Comp will crash Sonar (there is a bug in this module, it is workarounded in the mod)
 

msmcleod
90 18 7F  Note On (Track Select button press)
90 18 00  Note Off (Track Select release)
E0 62 62  Pitchbend (Fader move)

There must be "Touch" events around... I mean in case they are "before" Select, that fact can be used to filter out select only when the fader is touched, so "Select" button can be used without double clicking.
 

FYI - there's links to more info on the spec here: https://forum.cockos.com/showthread.php?t=101328
Although the docs are for the HUI, the protocol hasn't changed much.

HUI is significantly different from LC/MC protocols. The different in LC vs MC is unclear for me, LC specification you can find there: https://images.thomann.de/pics/prod/151261_manual.pdf
In short: http://www.azslow.com/files/mcu.png
 

This was the output from my Korg nanoKontrol Studio, which has standard sliders (so I guess that's why there's no touch message). My real Mackie probably sends out fader touch events in addition to the track select, but I'd need to check. I've got the touch option unchecked within Sonar, so I guess it's just ignoring it anyhow.
 
Presumably the touch is sent everytime you touch the fader. The track select however is only sent when you swap from one fader too another, and I couldn't find any way of stopping the track select being sent.
 
It's a real pain that they use EXACTLY the same note-on message as the select button - even if they had got it to send a different velocity, at least it would be possible to distinguish between a "real" select button press, and the one sent by the fader.
 
The mod works well for me in any case. I find it most useful when writing & recording, as it allows me to adjust the other instruments when I'm auditioning/recording another track without it changing the active track with Sonar, however if I want to swap tracks I can do so with a double-click of select button.
 

azslow3

Freex
any chance you could do some Jiggery-Pokery for the Mackie C4.
Would love to be able to map it to the pro-channel eq and comp etc.

Where you was before? I have started my Mackie mod long time ago, asked what people want, got silence... stopped the development. You can control ProCh EQ/Comp with MCU: http://www.azslow.com/index.php/topic,341.0.html
I remember someone with C4, but there was no cooperation in testing and I do not have C4.
WARINING: without my mod, attempts to control ProChannel Comp will crash Sonar (there is a bug in this module, it is workarounded in the mod)
 

 
What can I say...sorry!!!!
I'd love to get it working, but I guess with current events...
Have you looked at Studio One? I think it's really the next closest (yet still far) contender to SONAR.

msmcleod
This was the output from my Korg nanoKontrol Studio, which has standard sliders (so I guess that's why there's no touch message). My real Mackie probably sends out fader touch events in addition to the track select, but I'd need to check. I've got the touch option unchecked within Sonar, so I guess it's just ignoring it anyhow.

For nanoKontrol Studio: "As a default in SONAR, the Select button does not function" means they have not went throw Sonar documentation for MackieControl (do not understand how it works). Have you tried to switch it to other DAWs modes? It can be you see different messages (while all that modes are Mackie).
 
Sonar use touch events for automation overwrite. The option is to use it for selection, in addition to usual functionality.
 

Freex
I'd love to get it working, but I guess with current events...

Have you actually tried my mod? I do not remember, but since C4 and MCU codes are shared, there is high probability it already works.
 

Have you looked at Studio One? I think it's really the next closest (yet still far) contender to SONAR.

No API means no AZ Controller means "no go"... I have switch to Reaper.

I had a chance to check out what the Mackie Control is sending out.
 
Firstly, I was mistaken in thinking I'd set it to "Sonar" mode - it's running the standard Mackie Control mode. There's only three modes on the MCU: Mackie Control, Logic and HUI.... I remember doing something to set it to "sonar" at some-point, but it was obviously me just sticking the sonar overlay on!
 
Secondly, no touch events are being sent. From what I can tell, the faders are not touch sensitive - maybe this is because I've got the Mackie Control Universal (the original MIDI one), and not the newer Pro version.
 
One thing that did stump me though was the master fader "appeared" to be acting like a pan.
 
It turns out I had the master fader set to "Master" in Sonar's Mackie Control dialog, which meant it was only controlling the Left volume channel of my Focusrite 18i20. Changing this to "Bus" solved everything - so something to watch out for if anyone has a similar issue.
 
Mark.
 

msmcleod
Secondly, no touch events are being sent. From what I can tell, the faders are not touch sensitive - maybe this is because I've got the Mackie Control Universal (the original MIDI one), and not the newer Pro version.

That is strange. In any documents, for any MCU/LC/MC units (which are physically the same, https://www.soundonsound.com/reviews/mackie-control-universal ), faders are mentioned as touch sensitive.

The ‘Mackie ‘ mode is the correct mode for Sonar. When I bought my unit , that was the first thing I had to set on the MCU. If I understand part of the conversation, the ‘select’ mode works at least for the first 8 tracks in Cubase. Touch a fader and the appropriate track is selected on the GUI. I will have to test to see if it works for more than 8 tracks.