Q Light Controller+

Ok I just got a new Korg Nano Pad and it is all installed with updated drivers; and the Kontrol software. The Nano pad is recognized in QLC without issue using universe 1. To test; I have set up a simple scene in QLC and mapped it to Button 1 Scene 1 on the Nano but nothing happens. The button in the QLC is set up as follows:

Input Universe: 1 Korg nanoPAD
Input Channel: 168 :Button 1 - Scene 1

In Korg Kontrol it is set up like this:

Trigger Pad - 1
Assign type: Note
CC/Note Number: 1 D#2
Midi Channel: 1
Pad Behavior: Toggle
Roll/Flam Enable: disbled

I then saved it and wrote it to the Nano Pad. Went live with QLC and hit the first pad and nothing....any suggestions?

I've been working on this piece of s*** all friggin day and have nothing to show for it. There must be someone here who is familiar with the Nano pad and QLC+!? I have read the QLC+ maual from cover to cover as well as reading the manual for the Nano Pad. Arggggg!

What OS are you running?
What version of QLC+?

One thing I dont think is correct in your config is pad behavior.

Windows 7 and QLC+ version 4.10.2b

mumbles wrote:What OS are you running?
What version of QLC+?

One thing I dont think is correct in your config is pad behavior.

Are you using nanopad or nanopad 2

nanopad

mumbles wrote:Are you using nanopad or nanopad 2

Check these settings in QLC+
Inputs/Outputs> Mapping: nanoPAD input (checked)
Inputs/Outputs> Profile: KORG nanoPAD (checked)

Check these settins in Korg Editor (default)
Scene 1
MIDI Channel: Global
Assign Type: Note
Pad Behavior: Momentary
Gate Arp Enable: Enable
Touch Scale Gate Arp Enable: Disable
Note/CC/Prog Number: Trigger Pad--
Pad 1: C#2
Pad 2: D#2
Pad 3: F2
Pad 4: G2
Pad 5: A2
Pad 6: B2
Pad 7: C#3
Pad 8: D#3
Pad 9: C2
Pad 10: D2
Pad 11: E2
Pad 12: F#2
Pad 13: G#2
Pad 14: A#2
Pad 15: C3
Pad 16: D3


Then map button
1)Goto Virtual Console double click the scene button you want to map nanoPAD to. This opens up button properties.

2) Click Auto Detect (under external inputs)

3) Make sure nanoPAD is set on scene 1 (you can change this later)

3) Press the button on nanoPAD you want

4) Click OK

5) Press play button in QLC to switch operate mode

6) test your nanoPAD button

I'll give it a shot and get back within the hour.

mumbles wrote:Check these settings in QLC+
Inputs/Outputs> Mapping: nanoPAD input (checked)
Inputs/Outputs> Profile: KORG nanoPAD (checked)

Check these settins in Korg Editor (default)
Scene 1
MIDI Channel: Global
Assign Type: Note
Pad Behavior: Momentary
Gate Arp Enable: Enable
Touch Scale Gate Arp Enable: Disable
Note/CC/Prog Number: Trigger Pad--
Pad 1: C#2
Pad 2: D#2
Pad 3: F2
Pad 4: G2
Pad 5: A2
Pad 6: B2
Pad 7: C#3
Pad 8: D#3
Pad 9: C2
Pad 10: D2
Pad 11: E2
Pad 12: F#2
Pad 13: G#2
Pad 14: A#2
Pad 15: C3
Pad 16: D3


Then map button
1)Goto Virtual Console double click the scene button you want to map nanoPAD to. This opens up button properties.

2) Click Auto Detect (under external inputs)

3) Make sure nanoPAD is set on scene 1 (you can change this later)

3) Press the button on nanoPAD you want

4) Click OK

5) Press play button in QLC to switch operate mode

6) test your nanoPAD button

mumbles wrote:Check these settings in QLC+
Inputs/Outputs> Mapping: nanoPAD input (checked)
Inputs/Outputs> Profile: KORG nanoPAD (checked)

Check these settins in Korg Editor (default)
Scene 1
MIDI Channel: Global
Assign Type: Note
Pad Behavior: Momentary
Gate Arp Enable: Enable
Touch Scale Gate Arp Enable: Disable
Note/CC/Prog Number: Trigger Pad--
Pad 1: C#2
Pad 2: D#2
Pad 3: F2
Pad 4: G2
Pad 5: A2
Pad 6: B2
Pad 7: C#3
Pad 8: D#3
Pad 9: C2
Pad 10: D2
Pad 11: E2
Pad 12: F#2
Pad 13: G#2
Pad 14: A#2
Pad 15: C3
Pad 16: D3


Then map button
1)Goto Virtual Console double click the scene button you want to map nanoPAD to. This opens up button properties.

2) Click Auto Detect (under external inputs)

3) Make sure nanoPAD is set on scene 1 (you can change this later)

3) Press the button on nanoPAD you want

4) Click OK

5) Press play button in QLC to switch operate mode

6) test your nanoPAD button

[/quote]

Sounds good

OK ... nothing..here are screen shots of my screens. And I also tried to use "global channel" and still nothing. And there are 12 pads not 16.

mumbles wrote:Sounds good

Would you mind shairing shairing your QLC file

Which ones...all 3?

mumbles wrote:Would you mind shairing shairing your QLC file

Your *.qwx QLC workspace file

Sound Choice wrote:Which ones...all 3?

https://www.dropbox.com/s/kmtvul4voaa6j2n/2016.qxw?dl=0

BTW thanks for your help! I am usually the one helping people on other forums but midi is kinda new to me.

Your welcome

Sound Choice wrote:https://www.dropbox.com/s/kmtvul4voaa6j2n/2016.qxw?dl=0

BTW thanks for your help! I am usually the one helping people on other forums but midi is kinda new to me.

Pad Behavior should be momentary if you are using True scene function button in virtual console QLC will handle the toggleing not nanoPAD.

Global MDI Channel: 1
Velocity Curve: Nornal
BPM: 120
Midi Clock: Auto

mumbles wrote:Pad Behavior should be momentary if you are using True scene function button in virtual console QLC will handle the toggleing not nanoPAD.

Global MDI Channel: 1
Velocity Curve: Nornal
BPM: 120
Midi Clock: Auto

changed Pad Behavior to "Momentry". saved it to the nano and still nothing.

Im looking over your VC right now

Do you see a joystick in universe settings when you press nanoPAD buttons?

like the one on the right side of pic?