1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

M32 midi mode

Discussion in 'KOMPLETE KONTROL SERIES' started by tomshyk, 19/2/21.

  1. tomshyk

    tomshyk New Member

    Messages:
    4
    I am often using the M32 keyboard outside of the Komplete Kontrol plugin in Logic. In this case I need to use the 1-8 knobs as standard midi CCs.
    While this is supported and works fine in midi mode, it does not stay in this mode when changing tracks and even pops out of midi mode when using the undo function in Logic. This causes the 1-8 knobs to act as track volume controls instead of midi CCs and placing the unit back into midi mode is a cumbersome, two-handed operation (SHIFT/MIDI buttons). Because changing tracks and using undo are very common operations, I am constantly needing to reach over and put the unit back into midi mode.

    Having the 1-8 knobs revert back to volume controls is a significant problem in that not only do I lose access to my midi CCs, but it is very easy to accidentally change a (carefully set) track volume. As the algorithm is dynamically changing which track volumes are being controlled, the track whose volume is being changed may not even be visible on the screen, which is obviously causes problems.

    Although using the Komplete Kontrol plugin is great when using a product like Massive, I work a lot with orchestral tracks and using the Komplete Kontrol plugin in this case is not helpful (even if the particular lib supports NKS), uses up screen space and I do not want to be forced to use Komplete Kontrol when I need just a standard midi controller.

    To summarize, I would like the M32 to simply stay in midi mode when not using tracks with Komplete Kontrol software.

    My question is simply: When will NI address this issue and provide an update?
     
  2. Jeremy @ NI

    Jeremy @ NI Support Team NI Team

    Messages:
    1.339
    Hey tomshyk,
    The developers are aware that some of our users would like to see that feature implemented. It is in their radar, it's not as simple as it seems so they might address it when they have time and available resource.

    As an alternative, you can try this now. One of my colleagues suggested that you set a key command to "Bypass All Control Surfaces" and use this key command to toggle transport / host integration on and off. In this example I chose letter H (unassigned it from any other parameter) :

    Screen Shot 2021-02-19 at 16.28.18.png

    Screen Shot 2021-02-19 at 16.33.55.png
     
  3. tomshyk

    tomshyk New Member

    Messages:
    4
    Hi,
    I assigned a key command and tried this and it's actually quite helpful for tracks where I'm not using KK to control the plugin. I will definitely use this for now as the M32 stays in midi mode as I change tracks which saves a tremendous amount of button pushing. If I have a synth that I want to use KK with (such as FM8) the key command let's me get back to the M32 default behavior because it is quite nice to have those knobs mapped to interesting parameters when I want that as well.

    The disadvantage is of course I lose the DAW integration for play, rec, etc., when using this Bypass command, but I can use the normal key commands on the Mac keyboard for now. It's a usable work-around.

    Just for information from my perspective the ideal situation would be to have the knobs CCs when not using KK, and parameter controls when using KK. For me, when mixing orchestral libs (including your Symphony Series) track volume is most useful for overall balancing of the instruments (especially with libs from different companies), expression is used to control instrument volume and dynamics controlled (as standard) with the mod wheel (or strip). This is a popular method. I understand there are those who might prefer track volumes for knobs 1-8, but when you have 50-100 tracks it can become a real problem.

    Hope you guys come up with a good solution that keeps everybody happy. Would be nice to have midi mode that stays in midi mode and still have DAW integration (for loop, undo, rec, etc.). Thanks for the help!
     
  4. roblyn

    roblyn NI Product Owner

    Messages:
    3
    Hi any news of this? Using the keyboard now really confuse me since I have the same issues as "tomshyk". When will this be solved? Right now I really want to trash my M32 from frustration because of this annoying think that can't be shut off.
     
  5. safartomascz

    safartomascz New Member

    Messages:
    3
    Hey, I have the same issue here.. Is it please possible to let us stay in plugin mode while switching tracks? It is very annoying when you work in KK plugin, than you switch to other track where I have mapped my midi parametrs but the keyboard keeps switching to track mode.. than you have to press (double handed!!) Shift + plugin button and only than you can continue to use the knobs.. It is very annoying, please do something with this issue..
     
  6. JesterMgee

    JesterMgee Well-Known Member

    Messages:
    3.455
    Not sure that will ever be a thing because of the way a control surface is designed to work with the DAW. Works the same way in Ableton Live and no issues here switching between the mode I need, just a button to press.

    The whole point is so that as you move around, the control surface follows you on each track taking what is there and allowing control. If a KK instance is on the track, it will be picked up by the keyboard, if not, you have track control.

    For users who have an S series it is far easier to use because you have 2 nice big displays showing all the info so you know what mode you are in at a glance. Choosing the cheaper option means you have to live with the lack of features which makes some things a little harder. Having no real-time display is one of the big missing features so something you have to learn to work with.

    If you do not like the keyboard shortcut fix above and do not like how the control surface part works, deactivate the keyboard as a control surface and use it as a MIDI/NKS keyboard. You would then need to manually switch it to NKS when selecting a track tho and would not have any transport or track control at all.
     
  7. safartomascz

    safartomascz New Member

    Messages:
    3
    Hi, we also see clearly which mode we are in, thats not the problem here.. the problem is that the keyboard is simply switching to the track mode everytime the user clicks UNDO or changes track.. which I believe should not work this way from a UX standpoint.. the workflow is super annoying, that everytime you undo something / change track u have to press two buttons simoutaniously to get back to the midi mode.... my recommendation would be simply to leave the user in a mode he chose and not to force him out of it..
     
  8. tomshyk

    tomshyk New Member

    Messages:
    4
    Hi, original poster here..
    "The developers are aware that some of our users would like to see that feature implemented. It is in their radar, it's not as simple as it seems so they might address it when they have time and available resource."

    It's been almost a year and still no update for this. And apparently I'm not alone..

    The problem again: The M32 does not stay in midi mode when one changes tracks and re-assigns the knobs to track faders instead of midi CCs. Not only is it annoying to need to press SHIFT-PLUGIN every time one changes a track, the penalty for not doing that is you will likely change the volume of a track inadvertanly (when you move what you believe is a CC) and the track may not even be in view. One makes a mess of their mix without realizing it.

    We simply want the unit to stay in midi mode (as all the other midi keyboards I have work). Will NI please address this soon?
     
  9. tomshyk

    tomshyk New Member

    Messages:
    4
    Yes, from a UX perspective this issue is awful. The UI should be scalable - it should function well as a standard midi controller first - and then load on the KK features if desired.