Setlist and pads

Bertotti · Post by **Bertotti** » Wed Feb 12, 2014 4:20 am

Another question, since the pads only work with the global channel what channel does the midi controller have to send on? The QuNexus only send on channels 1-16 no global channel. Is this a problem? Thanks!

StephenKay · Post by **StephenKay** » Wed Feb 12, 2014 6:26 am

Bertotti wrote:Another question, since the pads only work with the global channel what channel does the midi controller have to send on? The QuNexus only send on channels 1-16 no global channel. Is this a problem? Thanks!

You need to understand: The "global" channel of the Kronos simply means which of the 1-16 MIDI Channels the "Global Channel" is set to in the Global Mode MIDI. In other words, the Kronos's global channel is one of the 16 MIDI channels. Typically, it will be set to Channel 1 (recommended). This therefore means that the Kronos's global channel is "1".

Therefore, you set the QuNexus to transmit on Channel 1.

If the Kronos Global Channel was set to 12 for some reason, then you would set the QuNexus to transmit on 12.

SanderXpander · Post by **SanderXpander** » Wed Feb 12, 2014 6:36 am

Thanks for clearing that up, Stephen. I really ought to read the manual at some point

Bertotti · Post by **Bertotti** » Wed Feb 12, 2014 4:37 pm

Progress, I have to use notes to set the pads for whatever reason. I also note that midi monitor shows my key on the QuNexus sending C4 but I have to set the Kronos to C5 to receive it. Why the difference? This has me stumped. I am going to try and find a note number to use now and am assuming it will be a whole octave higher as well. I am making progress but it is all so confusing! Stephen And SanderXpander thanks for the help! I appreciate it. I really need to know why the disparity between the Kronos note and the QuNexus note.

Bertotti · Post by **Bertotti** » Wed Feb 12, 2014 4:46 pm

Ah a bit more googling shows me that depending on manufacture the note number for C-4 could be 60 or 72. So I can guess that korg uses a note number of 60 and Qunexus obviously uses 72. Is the note number a midiCC#? Could I se the Kronos pad to CC#72 and it would work with the note number of 72 on the QuNexus. I'll try and see. Thanks!

Probably you all get a kick out of this because I get the impression you all know midi pretty well. I hope this trial for me can help another midi newb! Then I won't feel like I am wasting space with this thread!

SanderXpander · Post by **SanderXpander** » Wed Feb 12, 2014 5:40 pm

Don't confuse;
1. Note numbers 1 through 127. These are generally used to reference notes. In case of the K, they can also trigger a chord pad. As you found out, while the note numbers themselves exist on most machines, which note is central C is not set in stone.
2. CC# (continuous controller) numbers 1 through 127 (each with a value of 0 through 127). These can be thought of as 127 virtual sliders or knobs each with a value you can set. They are most often used for things like, volume, fx depth, filter cutoff frequency etc. Anything that needs a variable setting. Some values are more or less standardized, such as 1 (modulation), 7 (volume), 71 (filter resonance) and 74 (filter cutoff). In some cases, like a regular (non half) damper pedal, the value on/off pivots around the center 63/64. As per the Ks manual, the Kronos pads can also respond to CCs in which case the value (not the number) of the used CC determines the velocity with which the pad is played.
3. Pitchbend. Because the human ear is very sensitive to pitch, using a mere 128 steps for pitch bend wasn't enough, so through some primitive computer voodoo pitchbend was taken out of the other CC table and given a resolution of 128*128=16384 steps (if my math serves me right). Therefore it is addressed separately.
4. Program Change/Bank Change numbers. These are mostly used to tell the sound module to switch a sound. 5. SysEx. SysEx is used for any data that the manufacturer wants you to be able to access but which doesn't fit the standard midi spec, for instance because there are not enough CC numbers or it doesn't make sense to use them. The Kronos Editor for instance communicates almost entirely via SysEx with the K. SysEx is not universal between devices like the other midi functions. It consists of string of hex data.

All of these things except SysEx is sent on one of the sixteen midi channels. SysEx, not really being part of the "regular" midi spec, is just sent.

Bertotti · Post by **Bertotti** » Wed Feb 12, 2014 5:57 pm

Cool that makes sense. My problems now all stem from the QuNexus. And they have all but ignored my requests for any assistance. Even the sale manager who set up the return from the first QuNexus hasn't responded to me, the first one wouldn't adjust per key sensitivity correctly. I used midi monitor to show the problem and some pictures. They agreed. Now I have a new issue and until I can get a note number to transmit without the accompanying tilt and pressure cc#s I can't use it. It keeps messing with Karma switches and such. Basically it isn't doing what the manual says it should. Hopefully I will get it sorted soon. Thanks for the help!

trajan · Post by **trajan** » Wed Feb 12, 2014 7:09 pm

I have a question how do kontrol the volum of pad with exp pedal

Bertotti · Post by **Bertotti** » Wed Feb 12, 2014 7:10 pm

Worked it out. Not QuNexus problem but a lack of knowledge on my part. I misunderstood and had different expectations of what the QuNexus could do.

My mistakes were I didn't know Kronos worked with a different set up for note values. Midi monitor helped me find this. I saw C4 on the QuNexus but the pad sounded on C5, So Kronos sees c4 as 60 and QuNexus sees it as 72. First hurdle made.

Next I set up the pads notes on the tab Stephen said. I used to different tabs both referencing pads and obviously they are used for something else. I need to learn what as I still do not know.

Anyway on the global, controllers/scales tab and the controller tab I set the Kronos pads to c9-G9 and on the Qunexus I set up the top 8 keys to not participate in the controller layer and set the note value respectively from 120-127. Pads work great now. No volume control though. I don't know of anyway to adjust that to be honest, except with the master volume. I can not adjust it with velocity since I have to use note numbers and because I used 120-127 I think it is as loud as it can be. Not a problem really.

I will see what I can use for with Karma later right now my mind has absorbed enough knowledge for the day!

Thanks everyone. I will say if the QuNeo allows better midi control where I can assign a cc# to different ads slider and controls I will buy one also. I really do like this little QuNexus and The sale manager has gotten back to me we had some email issues which are totally forgivable. KMI also offers a free half hour phone or Skype training and you can pay for more time if you desire. I may take them up on that later. I also discovered this little board works well with animo. I have not tried to set up andy other controls with it yet but as I learn more I am sure it will work out.

Thanks again everyone I will leave you all alone now, at least for a bit!

edit to add; one nice thing is, I can play more then one pad at the same time from the controller!

Bertotti · Post by **Bertotti** » Wed Feb 12, 2014 7:29 pm

I don't know that as I have no pedals. Maybe I should invest is some?

I also just learned there is a way to disable some of the functions that I didn't think could be shut off. I am going to submit the training request with KMI. I know it will help a lot.

I also have a few more experiments in mind so I might find another way to do this that will allow volume with pressure.

Also this means the KMI QuNexus works as a USB device with the Kronos.

SanderXpander · Post by **SanderXpander** » Wed Feb 12, 2014 10:22 pm

Note numbers are separate from a velocity value. I suppose it can get confusing because each value seemingly goes from 0 to 127, that is just the midi spec. Each key you press on your controller will send a "note on" signal to your K, containing an actual note number and the velocity with which the key was played. Note number 120 can still have a velocity between 1 and 127, depending on how hard you play the key.

Possibly your sound on the K doesn't respond to velocity, or you ticked the "fixed velocity" box on the pads tab? Or you somehow disabled velocity on the controller by mapping those keys to a note number instead of just playing the keyboard?

Bertotti · Post by **Bertotti** » Thu Feb 13, 2014 12:45 am

Yes I had to program the controller to a note number and if I read the Kronos manual right the velocity only works with cc# not note number. I have to read that part again in the manual. Thanks!

SanderXpander · Post by **SanderXpander** » Thu Feb 13, 2014 8:05 am

I'm pretty sure the velocity accompanying the note number is the velocity used for the pad. But it's conceivable that if you program youf QuNexus to send specific note number from specific keys, it stops working as a normal keyboard for those keys and doesn't send velocity. What happens if you don't map them on the QuNexus but simply transpose the keyboard so you can hit those notes?

Bertotti · Post by **Bertotti** » Fri Feb 14, 2014 2:08 am

Found the hold up on velocity. Below the note number assignment box there is the value box. Mine was set to 127, I thought that meant up to but after rereading the manual I see that a value of -1 set the note number velocity to variable! conversely a -1 one on pressure, tilt, toggle, or note number turns that parameter of and the value box a -1 sets the pressure and tilt to latch! Thanks for everyones help and thanks to Dave and the tech at KMI for turning me onto how to turn of the control layer tilt and pressure! Thanks!

Now I am going to go play with karma and see if it make any sense for me to use the controller instead of the kronos for controls.