Author |
Topic: Mapping questioon (Read 1326 times) |
|
pyth2
New Member
MIDI-OX Rules!
Posts: 3
|
 |
Mapping questioon
« on: Jul 15th, 2002, 12:35am » |
 Quote  Modify
|
I am building an instrument with the softsynth Reaktor to use in controlling my external synth.
Here is an example of a SYSEX parameter on my synth that I am not having to good of luck creating a mapping for. F0 42 30 5D 41 00 00 09 00 00 (00) (00) F7 The parameter works like this.., the byte next to F7 ranges from 00-7F each time it reaches 7F the byte next to it increases by one on upto 0B which is the max point of the parameter. Another one I'm having a problem with mapping is an EQ parameter that works like this, using the same sysex example from above, when the EQ is moving in a +db range the byte next to F7 ranges from 00-7F but when the EQ is changed in a -db range the other byte changes to 7F and the one next to F7 ranges once again from 00-7F. Any help would be greatly appreciated.
Thanks 
|
|
 IP Logged |
|
|
|
Jamie OConnell
Administrator
 
Gender: 
Posts: 2027
|
|
Re: Mapping questioon
« Reply #1 on: Jul 15th, 2002, 2:02am » |
Quote Modify
|
The first example sounds like a typical 14 bit MIDI value split into two 7 bit bytes. Well, actually not a full 14 bits since the maximum value is 0B 7F (which would be 1535 decimal). The only built-in controller that always uses 14 bits is PitchBend.
You could use the value Byte from any controller to fill either field, but there is no support right now for performing interpolation mapping for SysEx values. You could assign a controller to map the 0 - B field, but this would give you a coarse mapping which would then max out after a short travel.
|
|
IP Logged |
--Jamie
Music is its own reward.
|
|
|
pyth2
New Member
MIDI-OX Rules!
Posts: 3
|
|
Re: Mapping questioon
« Reply #2 on: Jul 16th, 2002, 12:05am » |
Quote Modify
|
Jamie,
Thanks for the reply, oh and by the way I just wanted to tell you your program ROCKS !!!
It's really helping me out on my quest for complete control of my midi hardware and software.
Just a couple of thoughts: In the data mapping section it would be nice if one could copy and paste multiple mappings at once or maybe an .oxm merge function. What would be really cool for sysex editing would be an editing matrix sort-of like the one you have for CCs'. A person could select a row and click recieve and then that row would fill its cells with each byte on up to the sysex end message, select a new row and repeat, then the cool part is one could select a colume at the top and each colume would have a little dialog window or a properties popup where one could select a hex range, lets say 00-0A then click change and each cell in that colume would be filled like this; colume D row 1:00, colume D row 2:01, etc... Sysex editing and creation of mappings that used sysex could be done much faster this way, anyway just thought I would send the idea your way and maybe get your thoughts on it
Thanks,
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
Gender:
Posts: 2027
|
|
Re: Mapping questioon
« Reply #3 on: Jul 17th, 2002, 1:04am » |
Quote Modify
|
There are some good ideas here, we'll have to think about them some more.
Quote:
In the data mapping section it would be nice if one could copy and paste multiple mappings at once or maybe an .oxm merge function.
|
|
Actually, this capability sort of exists. When you Load... a Map (.oxm), there is an option to [x] Append to existing Map. When this is selected, the loading map is added to, rather than replacing what's in the list.
|
|
IP Logged |
--Jamie
Music is its own reward.
|
|
|
pyth2
New Member
MIDI-OX Rules!
Posts: 3
|
|
Re: Mapping questioon
« Reply #4 on: Jul 17th, 2002, 3:52am » |
Quote Modify
|
Quote:Actually, this capability sort of exists. When you Load... a Map
(.oxm), there is an option to [x] Append to existing Map. When
this is selected, the loading map is added to, rather than replacing
what's in the list |
|
 Right in front of my eyes the whole time. Hey thanks, you just saved me a bunch of time.
I just thought of sometihing else that might be kinda neat. The ability in data mapping to have whatever is being mapped to, have one or more of it's parameters changed to a random value within the selected range. An example might be: Controller in to sysex out.., in the sysex string where you can substitute for FA,FB,FC, maybe FD which would flag that field for random.
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print