Tagged: cme uf 80 classic midi problem
December 26, 2015 at 5:08 pm #27523Chua Ah KiangGuest
Recently I bought a xkey-37 for evalution, I will use 8 keyboards for stage performance, I test all the function of Xkey, I hook it to roland sound module, I need to assign a button for program change function, I try to use the “pitch up” button on the left, and set “program 39” , after “save modified to xkey”, yes! it work, but the program number not “39”, but change ramdomly everytime the button pressed, I have tried this for 3 days, at last I notice that the program number will set according to the velocity of the button pressed, Please help! Thanks.December 26, 2015 at 5:45 pm #27524
I only have Xkey (25 keys) in hand, so I tested it with Xkey Plus, I can make the program change to #32, please check attached screen shot. When you assign the Pitch Up button to PC, it will switch to “single” mode automatically, so it won’t be controlled by “velocity” data, I do not know why you had this problem. Or maybe Xkey37 has some issue with its firmware? Please try to do “Reset to factory” in Xkey Plus first.
(If you cannot see the screen shot, please check on Facebook though below link)
December 26, 2015 at 6:27 pm #27528Chua Ak KiangGuest
This feature is very important for live performance, so I try hard to find out the problem, reset to default already done serveral time, I am quiet sure this should be an issue in xkey-37 firmware, anybody who have xkey-37 please have a try.December 27, 2015 at 2:35 am #27529Zhao YitianGuest
Hi, please let us know your firmware version and bootloader version which you can find on the first page of Xkey Plus software.December 27, 2015 at 5:23 am #27530Chua Ah KiangGuest
Yes! the firmware version is 2.0, s/n:1947333330383538003b003f, xkey plus ver2.3.
I have open another xkey37 for test, this time I hook it to a Roland jv-1010, the problem as same as the first xkey37.December 27, 2015 at 8:11 am #27531
It is strange, we tested both Xkey and Xkey37 here and did not find same problem. Can you please update the firmware again and do “reset to factory”, then try it again?December 27, 2015 at 1:22 pm #27533Chua Ah KiangGuest
I press “check new firmware” (see pic1), and allow to upgrade to ver2.1, but screen show as pic2, no action, how? I am using windows XP.December 27, 2015 at 1:54 pm #27534Chua Ah KiangGuest
Yes! now I have upgrade the firmware to version 2.1, and do “reset to factory”, set modulation button for program change 39, test again, problem still remain. can you use “monitor input” to show the code sent by xkey37? I have no such software for monitoring.December 27, 2015 at 2:01 pm #27535December 27, 2015 at 2:47 pm #27536Chua Ah KiangGuest
Thank! This is a useful sofeware for me, now I know the problem, the code sent to usb is correct, but the code sent to midi output cable is not the same, it contains some extra note-on note-off code, this cause the program change error.December 27, 2015 at 2:54 pm #27537
Ok, got it. Already asked our CTO to check this, but he is in holiday now, so it will take few days. Sorry.December 27, 2015 at 3:09 pm #27538Chua Ah KiangGuest
Ok! I am going to use 5 xkey for playing 5 parts score arrangement next week, this time there will be no program change in one song, all play strings only. Thanks.December 27, 2015 at 3:12 pm #27539
Thanks very much! Will try our best.December 28, 2015 at 4:46 am #27540
Hi, we tested both USB and MIDI OUT from our side, we did not get same wrong extra note-on/ note-off code here. We guess maybe one of your Xcable was defective? Could you please change another Xcable to test?December 28, 2015 at 9:02 am #27541Chua Ah KiangGuest
Now thing become interesting, I have used a new xcable for test, same result, I even change a new usb midi interface cable(the one with usb, midi-in, midi-out) to do further test, both generate extra code:
midi interface cable1:
midi interface cable2:
I use a arturia bitstep pad to do program change, using same midi interface cable, never generate extra code, also, roland sound change patch correctly.
- You must be logged in to reply to this topic.