- #ALESIS Q49 NOT WORKING HOW TO#
- #ALESIS Q49 NOT WORKING DRIVERS#
- #ALESIS Q49 NOT WORKING SOFTWARE#
- #ALESIS Q49 NOT WORKING PC#
#ALESIS Q49 NOT WORKING DRIVERS#
Once you've configured it, it should just work from then Mar - up until recently, the Korg USB MIDI driver was not compatible with Win/ 20H2, which meant the editor wouldn't work properly (you'd make edits, but they wouldn't be saved to the device). I believe they've now got updated drivers on the Korg website. The settings are sored in flash memory in the nanoKONTROL 2, and no, they don't need any button dance when starting up. They probably have a battery inside that keeps the settings saved, so maybe the battery is bad. I haven't gotten past the transport 'n' faders stage with my nanoKONTROL2, but I can tell you that mine doesn't require any sort of button dance when rebooting my computer or starting the unit. That is unfortunate since I spent several hours fabricating a nice bracket to mount the nano over my main MIDI keyboard controller (a Native Instruments Kontrol S49, which doesn't have any faders). I requested tech support from Korg a week ago and haven't heard back since.
#ALESIS Q49 NOT WORKING SOFTWARE#
Although the unit is clearly connected and controlling transport and console faders the supplied Editor software indicates that the unit is not connected when the app is launched and therefore cannot be used to program the unit. I wanted to program it to send selected MIDI CC's with the faders. However, I did not purchase the unit to control the mixer console.
#ALESIS Q49 NOT WORKING PC#
Note: Every time you reboot your PC you must reconnect the nano as if it were for the first time (holding buttons when connecting USB). When set up as described for SONAR it does work out-of-the-box to control transport and mixer console faders. I recently purchased a nanoKontrol2 for use with Cakewalk.
*By independent I mean controllers that are not running as an integrated group - the ones in the picture above are NOT running independently, but as a group. The nanoKONTROL is designed to emulate the MCU - it won't work as a C4 as the C4 is a completely different device.Īlso, you shouldn't need to use the MMcL version of the Mackie Control any more (unless you want to run several independent Mackie Controllers*) - all my changes are now in the official Cakewalk version. The Mackie Extender ( Mackie Control XT ) The Mackie Control Universal ( MackieControl ) Mackie produced 3 control surface products as part of the MCU range:
#ALESIS Q49 NOT WORKING HOW TO#
On VST Plugins MIDI-Learn CC with faders, etc, works with NK2, but how to assign transport Button, Play, Record, Stop, Marker Left, Right, etc.
I have "MMcLMackieControlSetup.zip" installed. Is there any step-by-step guide or video tutorial. Hi there, i have also Nano Kontrol 2 in CC-Mode. Although you won't be able to use both rotaries and faders, you can easily switch to each bank of 8 parameters. An option to force flip mode might be the answer for those who want to use the faders rather than the rotaries. If you're using the synth edit shortcuts below, it already forces it into "edit" mode.
I'll have a think about how best to address this. I've recently got a Presonus Faderport 16, which has similar issues as there's only one VPot which acts on the currently selected channel. The Mackie does have a "flip" mode that allows you to use the faders instead, but there's no button on the nanoKONTROL 2 to enter this mode. However, by default the Mackie uses the rotary pots for VST parameters, while leaving the faders controlling the track volume. Not only do you need to change the nanoKONTROL 2 into CC mode, you also have to remove the Mackie Control surface in Preferences->Control Surfaces, then replace it with an ACT one.Ĭ4Mapper will partially help, as it will allow you to order the VST parameters.
Is this the answer? Thanks for any help.Ĭakewalk doesn't easily support swapping between Mackie and ACT mode on the same device. Anyone got any infomation that might help? I've even had one fader controlling 5 parameters even though they have different CC numbers. Sometimes it works and other times it dosen't. I have been using the Act controller and can assign all Rotary's and faders (8 of each) in Learn mode but the trouble starts when I try to use Act Learn to assign Vst functions to Nano Sliders and Rotaries. I have no trouble with using it with CbB but as soon as I go into CC mode I start to pull what's left of my hair out. Hi Everyone.I am a very long time user of Cakewalk/Sonar but have only just started trying to use the NanoKontrol2 to control various VST's.