Hello,
Anyone using NanoKontrol in Cubase 5? (Win7 pro 64)? How is it?
I have installed the device OK and using 'Generic' remote device with Cubase control set loaded, and it works, but the function is erratic. I use it for 1-8 channels which I assign into submix buses, so I can make quick 8-channel mixes and changes to overall mix.
Right now it doesn't respond at all for some reason; maybe I need to reinstall again. Or maybe it's because I switched the USB port.
When it does work, there is a big delay for mute/solo buttons, I mean, seconds. Same for transport control, which really doesn't seem to work properly at all...it's nigh impossible to hit the buttons just right so it'd actually start playback and not do a double hit. ffw/rwd doesn't work.
Funny enough, there is very slight delay only with the fader controls, and those would suffice for my use too (I also have a Shuttle jog wheel w/five buttons and it works real well and is what I mainly use for moving around/transport control), only I get bored of tackling with the Nano nearly every time I try to use it.
So...any other users here, any comments?
Also, is there any way/mod to let the red knob lights stay on when in mute/solo because I get mixed up with which is on and which not when I use 'em...it's really annoying to have to keep track of what is on and what not without the lights.
nanoKontrol Cubase issues
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
nanoKontrol Cubase issues
--
Who, me?
Who, me?
-
- Posts: 1
- Joined: Thu Feb 11, 2010 10:35 pm
nanokontrol
well there is a latency because this is a midi controller not a standalone mixer so you need a good external sound card, and yes changing the usb ports will mean you have to re install the drives on that port
Bump....I have exactly the same problems and i haven't changed the usb ports. The button on the nano kontrol is soloing the track instantly on the GUI instantly however the other tracks aren't muting on the GUI or on the audio for a few seconds. And the transport controls are being slow at responding, by a couple of seconds, as well. Has anyone else had this problem or found a solution at all? 
