Author |
Topic: Data-Mapping only for some In/Out-relations PLEASE (Read 1830 times) |
|
sequencer
New Member


Posts: 5
|
 |
Data-Mapping only for some In/Out-relations PLEASE
« on: Sep 15th, 2001, 10:11am » |
Quote Modify
|
Hi, great program so far. What I would really like to see is, that in the Data-Mapping the port would be an parameter. Now, I can only say that Data from channel 1 should be mapped to channel 2 for example. This affects ALL input ports. It would be great if I could do Data-mapping separately for every In/Out-relation I had defined in the MIDI-Devices-Dialog. I have a 8-Port Midi-Interface with several Keyboards and Synthezisers connected. This feature would give me total control in the data-flow for a live-session. Thank you in advance! Thomas
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2027
|
 |
Re: Data-Mapping only for some In/Out-relations PL
« Reply #1 on: Sep 15th, 2001, 1:12pm » |
Quote Modify
|
Thanks for the suggestions. A viable work-around is to use more than one MIDI-OX instance: you can setup a different mapping for each running instance.
|
« Last Edit: Sep 15th, 2001, 6:42pm by Jamie OConnell » |
IP Logged |
--Jamie Music is its own reward.
|
|
|
sequencer
New Member


Posts: 5
|
 |
Re: Data-Mapping only for some In/Out-relations PL
« Reply #2 on: Sep 15th, 2001, 4:36pm » |
Quote Modify
|
Thank you for quick answer. I tried this already, but then I can't use the same In/Out twice. In the Device-dialog I get only a small popup ('! Midex4: OK') and the relation is not active (already in use). I have the new Steinberg Midex8-Interface and I fear it's driver is not multiclient-capable Do you think it's generally possible to implement this "Free Data Mapping"? Many Thanks! Thomas P.S: What do other users think about this? Thanks to all replies!
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2027
|
 |
Re: Data-Mapping only for some In/Out-relations PL
« Reply #3 on: Sep 15th, 2001, 6:03pm » |
Quote Modify
|
That's too bad that the Midex does not seem to be multi-client. I continue to be astounded that newly released drivers remain single-client. A work-around for single-client output drivers is to use several instances of MIDI-OX attached together via MIDI Yoke ports (MIDI Yoke is multi-client). For instance, say you have 2 input ports that you want to use with different maps, and you want to send them both out of a single-client output port: 1) Open the 1st MIDI-OX instance and configure Hardware MIDI Input 1 and MIDI Yoke Out 1, enable your custom Map 1. 2) Open the 2nd MIDI-OX instance and configure Hardware MIDI Input 2 and MIDI Yoke Out 1, enable your custom Map 2. 3) Open the 3rd MIDI-OX instance and configure MIDI Yoke In 1 and your single-client Hardware MIDI Output. If you envision this, there are two parallel MIDI-OX instances 'Y'ing into another MIDI-OX instance further downstream. Of course it is possible to make data-mapping work at the port level, but it is a fairly large undertaking, that would entail redesign of the entire data-mapping feature and the port mapping feature. Still, I am inclined to consider this for a future version of the program.
|
« Last Edit: Sep 15th, 2001, 6:42pm by Jamie OConnell » |
IP Logged |
--Jamie Music is its own reward.
|
|
|
sequencer
New Member


Posts: 5
|
 |
Re: Data-Mapping only for some In/Out-relations PL
« Reply #4 on: Sep 16th, 2001, 4:38pm » |
Quote Modify
|
Thank you, I'll try this!
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
    


Gender: 
Posts: 2027
|
 |
Re: Data-Mapping only for some In/Out-relations PL
« Reply #5 on: May 21st, 2002, 3:58am » |
Quote Modify
|
The next version of MIDI-OX will allow you to attach individual translation maps between each Inport - Outport connection.
|
|
IP Logged |
--Jamie Music is its own reward.
|
|
|
sequencer
New Member


Posts: 5
|
 |
Re: Data-Mapping only for some In/Out-relations PL
« Reply #6 on: May 21st, 2002, 7:05am » |
Quote Modify
|
Thank you very much! You have by far the greatest customer-support I've ever seen!
|
|
IP Logged |
|
|
|
|