![]() 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. Am I doing something wrong? Also, how can I make it so when I press the “stop” button in the nanokontrol2 the “play” button led goes off (as it happens in the Mackie mode/ as it should be). Going the add nanokontrol2 as a “generic remote control” route it seems that Cubase is unable to send midi data to the nanokontrol2 which results in wrong led positions. Is there any way I can prevent Mackie Control protocol from sending “note on” and other midi messages apart from the “control” (transport/faders/pan pots etc.) ones when I use it with my Nanokontrol2 in Cubase 5? Disabling “Include in All MIDI Inputs” checkbox for Nanokontrol2 can’t be a valid, handy option (see detailed version). Posted: Mon 1:30 am Post subject: Mackie Control Protocol problem with nanokontrol2ġ. > Korg Kontrol49, microKontrol, padKontrol, nano and K series controllers Mackie Control Protocol problem with nanokontrol2 Profile Log in to check your private messages Log in ![]() Owned by Irish Acts Recording Studio & hosted by KORG USAįAQ Search Memberlist Usergroups Register That said, I already did tests converting the pitchbend to a 14-bit midi message, and that’s easily done, and would work directly in Cubase.Korg Forums :: View topic - Mackie Control Protocol problem with nanokontrol2Ī forum for Korg product users and musicians around the world. Going full midi mode on the X-Touch One isn’t a real option I feel, as that will make resolution of the faders too low (0-127 instead of 0-16383). One is to just write it entirely with the Cubase controller API, or make a hybrid of the two, where one part speaks mackie to get names and other information not available, and the other part works with a cubase remote controller. So while I’m still working on this, considering a few different strategies next, I got my eyes open a bit for possibly foregoing the python part entirely and working in the MIDI Api in Cubase.ĭepending on the replies I get for some questions regarding track name retrieval and the display update of the track time/beats, I might consider the option of writing a script that solves it entirely within cubase.ĭepending on the possibilities, and learning curve, I might take 1 or 2 paths.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |