padKONTROL Knobs - How to switch from Pad Preset to CC# ?

[Yikes]

I finally understand how to assign the preset MIDI messages on Pads 9 -16 to Knobs 1 and 2.
(Thanks to Metastatik's explanations in a prior thread)

I have also assigned a CC# to each Knob by using SETUP Mode,
in addition to the 8 assignable preset values from Pads 9 - 16.


SITUATION: Assume I'm using Knob1 to control a fader in my DAW.
The knob is transmitting MAIN VOLUME assigned from Pad 10.

QUESTION 1: How do I switch Knob1 to send the CC# that I assigned to it,
instead of sending the MIDI Message preset from Pad 10?

QUESTION 2: OR am I wrong again? Does the CC# I assigned to Knob1 get wiped out
as soon as I switch Knob1 to any of the presets on Pads 9 -16?

[justsa]

Unfortunately, yes it get wiped out.
However, if You already saved the scene on your padKONTROL, in order to go back to the previously assigned ccs, just reset the scene by [SCENE]+ [PAD #].
For example :
In Scene 2, Knob 1 had cc53 assigned and your needed to adjust the Main Volume on your DAW so u Did [Knob1 ASSIGN] + [PAD 10].
In order to reset Knob 1 to cc53 as you previously configured in the scene, just recall the scene settings : [SCENE]+ [PAD 2].
If it doesn't work ( I doubt it but never know ) change scene and come back to the one u were on.

Caution : The Whole scene will be reset so keep track of what you are changing.

[Yikes]

Thanks, Justsa

I didn't think anybody would ever answer this old thread.

I appreciate the solution you outlined, and since I wrote my question, I've learned a bit about using padKONTROL. As you suggest, the Scenes are a tremendous help.

I'm disappointed in the limited programmability of the two knobs (and in how all midi ON/OFF notes appear to software as being "off by one"). But overall, I like the pK. It's just quirky, like most "creative types"...

Thanks

[philsaudio]

Justsa:

I am re-posting this here since there is recent knowledgeable life here.

Hello I am new here but no nob.

I just got the trio of NANO usb midi controllers and have been working on getting it to play with PT 8 LE on a brand new Mac Book (osx snow leopard 10.6.3)

1. In the Kontrol Editor splash screen I do see the three keyboards. If I disconnect one and re open it is gone. Plug it back in and re open the editor it is detected. When I select one and press ok.

2. Once into the editor I can load (looks like it anyhow) the .set files to the individual kontrollers. No indication it isn't working from errors etc.

2. I do not see any activity on the keys or sliders in the individual editor screens when I depress or move an input element on the controller.
Should I see movement here? Is something wrong when I dont?

3. Moving on to applications/utilities/audio midi setup
With the driver V 1.07 I do not see the kontrollers
With the driver V 1.09 I do see the kontrollers in the MIDI Studio2 they are online and appear to be working. The only parameter I can edit here is the name of the device, ports and connectors are not editable.

4. Inside of protools I can see that two of the buttons on the Kontrol are mapped to the first two sliders in the mixer window. Pressing one alternates the slider from 0 to 127. Pressing the other momentarialy moves the second channel slider from 0 to 127.

I have tried to follow all the above information and perhaps I am almost there.

Should I see movement in the korg editor?
Is there a way to hover over a button in PT,and move a button on the kontrol and attach it to the button?
_________________
Brand New Macbook pro 2.4 duo 4GB ram 250 GB
Snow Leopard OSx 10.6.3

Thanks in advance

[Yikes]

phil ==

I can't advise you re Mac. In addition to padKontrol, I also have the nanoKontrol. In both cases, the Korg scene editor apps do NOT show any sort of response to knob, fader or button manipulations. The UI for each app is really just a *still photo image* of the hardware with "hot spot" areas over each controller in the picture (button, knob or fader) that receive your mouse-click inputs.

If your apps and your system recognize your Korg stuff, you seem to be up and running. In the case of Win XP, I have to assign each Korg tool its own, specific USB hardware port. The nanoK only works when plugged into its specific USB port. Weird, but that's how the manuals say it works...

I'm glad to know you're not a 'nob'. Heh Heh

[philsaudio]

Thanks so much for the prompt response. Nice to know I can stop looking for the picture to follow the movements. Kinda seems it should show you something, but the people who make this stuff don't need any feedback on their software, cause they don't have to use it or expend profits supporting us.

Thanks again.
Peace
Phil