![]() The help is much appreciated regardless of the outcome! I also set the nanoKontrol up as a Mackie HUI, and it functioned more or less as the BabyHUI did. This loss of functionality wasn’t related to the KeyStation though, as I deleted the KeyStation and the nanoKontrol still suffered from the same loss of functionality. Also, I moved the track control, the first 8 always stayed highlighted, making it look like I had control of only the first 8 tracks, although I actually had control of the next 8. Specifically, the ability to set markers, forward or rewind from marker to marker, and turn cycling on and off. Unfortunately however, the nanoKontrol lost some other functionality. Thanks Steinmel - I didn’t notice the subtleties in the nanoKontrol directions regarding which buttons to push and for which DAWs! Anyway, I set the nanoKontrol to HUI per your directions and configured it to be a BabyHUI, and it did in fact allow me to switch control between multiple tracks while the KeyStation was hooked up like I wanted it to. While pressing and holding down the SET MARKER and REW buttons, connect the USB cable from your computer to the nanoKONTROL2. To switch nanoKONTROL2 back in Cubase (Mackie Control) mode:Ģ. While pressing and holding down the SET MARKER and PLAY buttons, connect the USB cable from your computer to the nanoKONTROL2. To put nanoKONTROL2 in ProTools (HUI) mode:Ģ. But if this post helps someone else, that’s a good compromise! Sad that I lost a lot of time trying to figure it out. I’ve worked most of my existence without a transport on my keyboard though, so if I have to ignore it, I’ll ignore it. So, sure, I’d like to keep the M-Audio Keystation’s transport if possible, and if anybody’s aware of how I can configure it so it peacefully coexists with the NanoKontrol, please chime in. And guess what? Yup, the NanoKontrol worked perfectly after the M-Audio transport was deleted. The moment after I wrote the response to Steve above, I remembered that I was going to delete the Mackie Control for the M-Audio’s transport. So today, I thought maybe - just maybe - the two Mackie Controls are bumping heads. There isn’t much to it but it has a small transport section, which, when setup as a Mackie Controller in Cubase, works ok. I’ll spare the specific details of why this occurred to me earlier today at work, but suffice it to say that I in addition to the NanoKontrol, I have an M-Audio Keystation49 that I often use as my keyboard controller. I’ll explain what caused the problem and the easy solution for the sake of future generations. I’m thinking maybe there’s a parameter in Cubase I need to adjust or something. ![]() I still have Sonar, and the the tracks respond perfectly to the device in that application. but as mentioned above, it’s acting as if 9+ are 1+, ignoring the first 8. How I would expect it to work is that by default, the track controls would work with tracks 1-8, and then move up using the track up arrow on the device, and down using the down arrow if the tracks are set for higher tracks. It’s like the device is ignoring Tracks 1-8 entirely. And if I have 17 tracks, the device works as if Track 9 is Track 1 and Track 17 is track 8. However, the track controls only work on tracks 9-16. The transport controls seem to work just find. So, I have the device hooked up and it’s recognized by Cubase. I have Cubase 10 (although 9.5 is also responding this way) with Windows 10. ![]() To be honest, this problem could have also existed then, but I since I haven’t been able to really dig deeper into Cubase until recently, I might not have realized it. I had another Nanokontrol 2 problem back that I resolved with the help of this forum.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |