Author |
Topic: Problem understanding (Read 1231 times) |
|
gabriel
Member
MIDI-OX Rules!
Posts: 14
|
 |
Problem understanding
« on: Oct 16th, 2002, 6:27pm » |
 Quote  Modify
|
I don't quite understand the concept of Program Change Mapping. Or maybe I do, but don't know that I do. Is this the gist of it?
If I just use a map so that some program change numbers get translated to other program numbers as they pass through MidiOx, that's considered to be patch mapping. I could have many such maps, one for each channel.
I get the feeling that something different is at play in the Program Change Mapping facility. Does this add the functionality of being able to exchange one entire set of maps (as described in the previous paragraph), for another entire set of maps (including the port assignments)? Or is there more involved?
|
|
 IP Logged |
|
|
|
Jamie OConnell
Administrator
 
Gender: 
Posts: 2027
|
|
Re: Problem understanding
« Reply #1 on: Oct 16th, 2002, 8:51pm » |
Quote Modify
|
What we call Patch Mapping in MIDI-OX is more extensive than just mapping program changes. The facility is a result of user requests for a feature that would load a new map triggered by a program change message. Patch Mapping is configured in Options | Patch Mapping..., as opposed to regular data mapping, which is defined in Options | Data Mapping...
|
| « Last Edit: Oct 18th, 2002, 9:49am by Jamie OConnell » |
IP Logged |
--Jamie
Music is its own reward.
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print