Author |
Topic: Mapping Buttons KorgNanoKontrol 2 (Read 1981 times) |
|
jcw68
New Member
MIDI-OX Rules!
Posts: 3
|
 |
Mapping Buttons KorgNanoKontrol 2
« on: May 18th, 2018, 7:30pm » |
 Quote  Modify
|
Hi,
I am mapping using MIDIOX my NanoKontrol 2 to my Korg Krome.
I have managed to get the sliders to work and ONE solo button. When I try adding a second button strange things begin to happen. On the midi input panel, Solo 1 button has sysex code for on and off. Strangely the code changes to the next button when off is pressed eg from '0C' to 'OD'. This is not how it is mapped. Also for the second button, even though it is mapped exactly the same way as button 1 (except for CC number), the midi input doesn't show the same sysex code as button 1, but control change.
Here is the code from the MIDI input (pressing controller solo 1 on and off, and then solo 1 on and off.
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00205317 1 3 F0 Buffer: 18 Bytes System Exclusive
SYSX: F0 42 30 00 01 15 41 00 00 0C 00 29 00 00 00 00 00 F7
00205524 1 3 F0 Buffer: 18 Bytes System Exclusive
SYSX: F0 42 30 00 01 15 41 00 00 0D 00 29 00 00 00 00 01 F7
00205926 1 3 B0 67 01 1 --- Control Change
00205AAC 1 3 B0 67 00 1 --- Control Change
I have a word document with images and descriptions, but I cannot see how to attach that to this post.
Thanks for your help!!
John
|
|
 IP Logged |
|
|
|
Breath
Administrator
Gender: 
Posts: 1030
|
 |
Re: Mapping Buttons KorgNanoKontrol 2
« Reply #1 on: May 19th, 2018, 11:09pm » |
Quote Modify
|
A quick search found this www.kromeheaven.com/data/tips/korg-krome-midi-control.pdf
Is this of any use.
If not, let me know and I will get the Krome manual to have a look.0
In the Data Map you use non-sysex data numbers to be the varying data bytes in the sysex message
For example if you are using CC messages to control
FC is the Channel from you input message
FA is the first data byte (in CC it is CC type)
FB is the second data byte
So to change the last data byte in the sysex your message should be
F0 42 30 00 01 15 41 00 00 0C 00 29 00 00 00 00 FB F7
For programming reasons, this sysex message comes from the MIDI-OX Event Port.
So on the MIDI Port Routing window you need to connect the MIDI-OX Event Port to the Krome output on the right side.
As you probably also want to send other Midi messages to the Krome (Note On etc) you should also connect the Nano input on the left side to the Krome on the right.
All the best
Royce
|
| « Last Edit: May 19th, 2018, 11:24pm by Breath » |
IP Logged |
|
|
|
jcw68
New Member
MIDI-OX Rules!
Posts: 3
|
|
Re: Mapping Buttons KorgNanoKontrol 2
« Reply #2 on: May 20th, 2018, 1:11am » |
Quote Modify
|
Hi,
Thank you for your reply.
The document you referred to, I used it to set this all up.
The sliders was pretty straightforward.
Where I came stuck was with the buttons. I could not get them to work. I tried as the document suggested to use cc 102, but was not successful. Then i wondered since it was toggle button, that i might need the sysex code cor on and off...
I got a bit lost when the document started talking about msb and lsb on page 6.
I will start the button bit again, using the FB variable and see what happens.
Will let you know how I go..
|
|
IP Logged |
|
|
|
jcw68
New Member
MIDI-OX Rules!
Posts: 3
|
|
Re: Mapping Buttons KorgNanoKontrol 2
« Reply #3 on: May 20th, 2018, 4:38am » |
Quote Modify
|
Hi,
I think I have got it working. Simple omission...I had not changed to the correct data mapping file in the port routing section.
Thanks for the advice
John
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print