Jump to content

Is Github Control Surface SDK still valid


EduCampi

Recommended Posts

11 hours ago, msmcleod said:

Yes, the code is still valid. 

The public repo is missing some of the latest Mackie Control enhancements, but those enhancements are specific to the Mackie Control surface dll.

It will be nice in case you keep updating github... Every time, after reading some fancy Mackie request, I think "well.. may be I should produce MR...", I remember you have not updated repo with current version, so that make no sense ;)

Link to comment
Share on other sites

4 hours ago, msmcleod said:

 

Hello, some time ago I opened a topic of my own and made comments reporting that my PAN controls are sometimes changed.
I use a Nano KOntrol 2 and found that the changes, even without any movement on my part, only happen when the surface is active.

So for me it would be important if there was some way to turn NanoKontrol ON/OFF without having to go to preferences and disconnect.

Do you have any suggestions or tips for this operation to be better performed? Maybe some BUTTON SENSITIVITY command?

Link to comment
Share on other sites

10 hours ago, Milton Sica said:

Hello, some time ago I opened a topic of my own and made comments reporting that my PAN controls are sometimes changed.
I use a Nano KOntrol 2 and found that the changes, even without any movement on my part, only happen when the surface is active.

So for me it would be important if there was some way to turn NanoKontrol ON/OFF without having to go to preferences and disconnect.

Do you have any suggestions or tips for this operation to be better performed? Maybe some BUTTON SENSITIVITY command?

What set up are you using with your nanoKONTROL 2 - i.e. are you using SONAR mode with MackieControl, or some other configuration?

Link to comment
Share on other sites

3 hours ago, msmcleod said:

What set up are you using with your nanoKONTROL 2 - i.e. are you using SONAR mode with MackieControl, or some other configuration?

Hello, I already tried to use your creation, I currently use Cakewalk's own creation and the problems are the same.

I've tried with Mackie Control - 1, Mackie Control XT and they all end up with the same problem.

I have placed the commands for my MASTER,BUS. So I can better visualize when there is any PAN change.

To avoid more problems I leave the PAN controls centered and the volume controls at 0.

Link to comment
Share on other sites

17 hours ago, Milton Sica said:

Hello, some time ago I opened a topic of my own and made comments reporting that my PAN controls are sometimes changed.
I use a Nano KOntrol 2 and found that the changes, even without any movement on my part, only happen when the surface is active.

So for me it would be important if there was some way to turn NanoKontrol ON/OFF without having to go to preferences and disconnect.

Do you have any suggestions or tips for this operation to be better performed? Maybe some BUTTON SENSITIVITY command?

Long time ago I have tried to workaround self-moving faders of my StudioMix. My conclusion: the only good solution is replacing the hardware.

  • Thanks 1
Link to comment
Share on other sites

On 10/25/2022 at 4:55 AM, msmcleod said:

What set up are you using with your nanoKONTROL 2 - i.e. are you using SONAR mode with MackieControl, or some other configuration?

Hello, I'm thinking of putting the Knob of PAN in Nano Kontrol 2 as 0 to 0 instead of 127.

Where are the settings for each Control Surface stored for me to try via Kork Editor?

Link to comment
Share on other sites

3 hours ago, Milton Sica said:

Hello, I'm thinking of putting the Knob of PAN in Nano Kontrol 2 as 0 to 0 instead of 127.

Where are the settings for each Control Surface stored for me to try via Kork Editor?

I don't understand what you're trying to do here.

1. The Korg Editor isn't involved when using the Mackie Control protocol as the protocol is fixed (i.e. prescribed by Mackie and not alterable).
2. All control surface settings are stored in CtrlSurface.dat - this is not human readable, and contains the settings from all control surfaces (not just Mackie).. look at the persistence code to see the implementation.  

Also, be aware that the Pan knobs on the nanoKONTROL 2 are actually potentiometers trying to emulate rotary controllers.  A real rotary controller just sends "turned left" / "turned right" information. A rotary controller also has no position as it can be turned infinitely. 

Link to comment
Share on other sites

2 hours ago, msmcleod said:

I don't understand what you're trying to do here.

1. The Korg Editor isn't involved when using the Mackie Control protocol as the protocol is fixed (i.e. prescribed by Mackie and not alterable).
2. All control surface settings are stored in CtrlSurface.dat - this is not human readable, and contains the settings from all control surfaces (not just Mackie).. look at the persistence code to see the implementation.  

Also, be aware that the Pan knobs on the nanoKONTROL 2 are actually potentiometers trying to emulate rotary controllers.  A real rotary controller just sends "turned left" / "turned right" information. A rotary controller also has no position as it can be turned infinitely. 

I thought that resetting the knob values such changes would not change the PAN values I've been suffering.

It is quite uncomfortable doing a mix and realizing that the value it should be centered has shifted either to the right or to the left.

That was my attempt as there is no other solution within the DAW to turn on/off CONTROL SURFACE.

I'm lost without knowing where to look for a solution.

 

Link to comment
Share on other sites

2 hours ago, Milton Sica said:

I thought that resetting the knob values such changes would not change the PAN values I've been suffering.

It is quite uncomfortable doing a mix and realizing that the value it should be centered has shifted either to the right or to the left.

That was my attempt as there is no other solution within the DAW to turn on/off CONTROL SURFACE.

I'm lost without knowing where to look for a solution.

 

The bottom line is, the nanoKONTROL 2 is using potentiometers to emulate rotary encoders, and furthermore, they're not motorized.

Decades ago I had a Fostex MixTab / DCM100 that was potentiometer based, and not motorized, but it had a mode that allowed you to adjust the faders & pots to match the current values. Once you'd matched them, you'd exit that mode.  However, this was implemented in the control surface hardware itself - something that the nanoKONTROL 2 doesn't do.

What I tend to do when using the nanoKONTROL is to match the pan knobs within Cakewalk to what the  nanoKONTROL is currently showing, then move the knobs on the nanoKONTROL back to where I think they should be.  You could also temporarily go into preferences, and change the input MIDI device, then move the pan knobs to where you think they should be. However as soon as you shift banks, you're stuck with the same problem.

The only real solution is a controller with motorized faders & rotary encoders.

Link to comment
Share on other sites

9 minutes ago, msmcleod said:

The bottom line is, the nanoKONTROL 2 is using potentiometers to emulate rotary encoders, and furthermore, they're not motorized.

Decades ago I had a Fostex MixTab / DCM100 that was potentiometer based, and not motorized, but it had a mode that allowed you to adjust the faders & pots to match the current values. Once you'd matched them, you'd exit that mode.  However, this was implemented in the control surface hardware itself - something that the nanoKONTROL 2 doesn't do.

What I tend to do when using the nanoKONTROL is to match the pan knobs within Cakewalk to what the  nanoKONTROL is currently showing, then move the knobs on the nanoKONTROL back to where I think they should be.  You could also temporarily go into preferences, and change the input MIDI device, then move the pan knobs to where you think they should be. However as soon as you shift banks, you're stuck with the same problem.

The only real solution is a controller with motorized faders & rotary encoders.

Thanks for the considerations.

Something that came to me as a result of this reflection: Some time ago I had problems on my M-Audio Keyboard that seemed to enter commands as well as if I had moved the keyboard (wheels, volume). The information I got was that the problem could be happening in the cable and its movement in the connection. I switched to new cables and the problem persisted.
Anyway, I think my problem could be overcome if there was a more direct MIDI DEVICE ON/OFF BUTTON in the Panel and, not, having to go into Preferences -> Delete -> Apply Adjustments.

Link to comment
Share on other sites

If some control(s) send value on there own, f.e. when you operate other controls (and that seems like the case), it is better think these controls are broken and don't use them at all. What re-enabling the device as a whole will bring you? You just know "it can randomly modify my mix now...". I don't think its worse to use such controls.

So, knobs are useless. You have a set of transport buttons, tiny faders and strip buttons.

Assuming you for some reason don't want change the controller and still want to use what you have, I think the only reasonable approach is DIY preset. Use the controller in "native" move with AZ Controller plug-in. You can instantiate "Startup" preset https://www.azslow.com/index.php/topic,154.0.html with 3 buttons per strip and assign controls which are still working. There is video how to do this, I think you can manage all that in a half an hour. Initially you will loose LEDs feedback, but that can be added (once you have working preset you can upload it to my forum and ask to add feedback, till you want read and understand https://www.azslow.com/index.php/topic,336.0.html...). Also AZ Controller has several modes for finite controls like your faders: jump (what you have now), catch, instant (with curves) and endless imitation. It can happened you like some of them. 

Link to comment
Share on other sites

Quote

Yes, the code is still valid. 

The public repo is missing some of the latest Mackie Control enhancements, but those enhancements are specific to the Mackie Control surface dll.


Thanks for confirming!

Edited by EduCampi
  • Like 1
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...