Author |
Topic: Mapping Controller #38 to Sysex (Read 1653 times) |
|
Bagpuss
New Member

 I love YaBB 1 Gold!

Posts: 2
|
 |
Mapping Controller #38 to Sysex
« on: Feb 11th, 2002, 2:19pm » |
Quote Modify
|
I must admit to being a Midi-Ox newbie. I'm having trouble sucessfuly mapping controller #38 to a sysex message using the 'FA' or 'FB' parameters. The scenario is as follows: I wish to merge the controller outputs from a Johnson J-Station with the midi notes from a Roland PC200 master KB and perform real time filter adjustments on a Yamaha MU10 XG module. I'm 'cheating' by using XG-Edit into Midi-Ox to determine the appropriate sysex message (and this process is helping me to decypher the Yamaha Midi Data Format section of the MU10 manual). Controller to contoller re-mapping works OK as I have been able to get an 'easy' one working (controller #38 on the J-Station to Midi Volume controller #7 on the MU10). However, the controller to Sysex seems to be inadvertently filtering the data stream. I can view the input and output monitors changing as predicted with CC to CC mapping but no sysex messages output at all. Finally, I'm indebted to GaryPR in the general discussion for the inspired idea of using the J-Station for external controllers. Kind Regards, Pete Springfield
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2027
|
 |
Re: Mapping Controller #38 to Sysex
« Reply #1 on: Feb 11th, 2002, 8:32pm » |
Quote Modify
|
CC:38 is a 'special' controller as it is usually used as part of the NRPN group. I believe that this controller was not fully available in 6.4.1, but is fixed in the 6.4.2 beta. The beta should be available soon.
|
|
IP Logged |
--Jamie Music is its own reward.
|
|
|
Bagpuss
New Member

 I love YaBB 1 Gold!

Posts: 2
|
 |
Re: Mapping Controller #38 to Sysex
« Reply #2 on: Feb 13th, 2002, 7:26am » |
Quote Modify
|
Using controllers other than #38 worked fine. I should have tried this before. Many thanks for advice. Pete
|
|
IP Logged |
|
|
|
|