9/1/2023 0 Comments Cubase mackie control![]() ![]() Um, this is not even possible as far as I am aware. Now there may be some clever way to get around this, if I recall correctly there is no Mackie traffic above channel 9, so if you used higher channels 10-16 and recorded only those you MIGHT have a workaround - anyway, start thinking about workarounds of this type and you may find a solution. Both issues don’t occur while in Mackie mode, maybe some other nanokontrol user can shed some light on this one.Īny ideas? Thanks alot and happy new year! Also the “play” button led stays on even after the “stop” button gets pressed which is problematic. ![]() It then seems that Cubase loses the ability to send midi messages back to nanokontrol2 which is probably why changes in solo/mute and transport buttons in Cubase don’t reflect into those in the nanokontrol2 leds. Ditching Mackie Control completely and add nanokontroler2 as a “generic remote control” which simply doesn’t work as good as the Mackie Control and seems to have a problem of its own. I see custom scripts for Reaper and Live which actually improve nano’s functionality but none for Cubase so if any kind soul kind point me out to the right direction, please do so.ģ. A nanokontrol2 template for Cubase that acts like the Mackie Control minus its issues. A modified Mackie Control xml which somehow keeps the control messages but excludes the others (“note on” etc.). I mean, how other people who work with nanokontrol2/other controllers using Mackie control protocol cope with this?Īll I can think of as possible solutions are:ġ. Naturally, doing that every 2 mins can’t be an option so there must be an alternative I am missing. And to make things worse, it means that after you’re done and you want to turn into “daw/Mackie mode” again you have to change settings AGAIN. ![]() But that means it will not be able to pick notes from my midi keyboard then. When you change into nanokontrol’s “midi cc” mode in order to control a plugin you have to either enable “include in all midi inputs” again or change the midi input for the midi track in question to nanokontrol exclusively. This solves the issue but as you can imagine it creates another: I guess this is the way the Mackie Control protocol works in general? This makes no sense but it seems this is the case since Nanokontrol2 manual advices to clear the “Include in All MIDI Inputs” check box for Nanokontrol2 within Cubase options. So, I am using the Mackie Control protocol with my Korg’s Nanokontrol 2 in Cubase 5 in order to control the transport buttons and mixer as it is officially suggested.Įverything works great except the fact that when in “Mackie mode”, apart from the control messages sent when I press a transport button, I also get “note on” and other controller messages resulting in notes getting played or vst synths getting detuned If a midi track is selected which causes a highly undesirable mess. I apologize in advance for creating a topic which isn’t strictly about Reaper (which I mean to check out, for the time being I am a Cubase 5 user and this community seems friendly enough so hopefully I won’t be told to GTFO) but the Mackie Control protocol is common ground for all DAWS and since it is widely known that the Reaper users know nanokontrol2 better than any other (as it can be seen from all the related posts) if anyone can help me, they reside here (Korg forums are pretty dead so…). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |