|
||
Title: Perhaps I'm slow, but Patch Mapping is Not Working Post by ryansupak on Apr 13th, 2004, 4:28pm Hi, I just got MIDIOX yesterday and I'm learning the ropes, but I can't get Patch Mapping to work. Here's the process I'm using: First, I set up my device. It's an Oxygen8 USB and I'm setting the IN port to be its IN port, and its OUT port to be the OUT port. Also, something called "MIDIOX Event" or the like appears to be automatically routed to the OUT port. Next, I set up Data Mapping. I do all my mapping, then save the mapping as a preset. I repeat this process 4 times until I have the four presets I want to toggle between. Within each Data Mapping Preset, four Note On events are translated to Program Change messages 1-4. I go to the Patch Mapping table and set up the paths to my four Data Mapping Presets to Program Changes 1-4. At this point, preset 1 is loaded in Data Mapping and I hit Program Change #2 (hoping to toggle to Preset #2). I see something like "PC#2 - HonkyTonk Piano" in the Output Monitor. However, the preset does not change. According to the documentation, when I hit the PC message I should see a message in the Output Monitor that says something like "switched to c:\midiox\preset2", but I'm not seeing that. Any ideas what I'm doing wrong, or ways to troubleshoot? Thanks in advance!!! rs |
||
Title: Re: Perhaps I'm slow, but Patch Mapping is Not Wor Post by ryansupak on Apr 13th, 2004, 7:53pm I looked at some other forum entries, and it looks like I need to have two instances of MIDIOX running: The first has to convert the note-ons to PC data, and The second has to do all the other data-mapping and patch-swapping. Is this correct? rs |
||
Title: Re: Perhaps I'm slow, but Patch Mapping is Not Wor Post by ryansupak on Apr 14th, 2004, 12:06pm Just writing back to say that using one instance of MIDIOX to change NoteOns to Program Changes, routing that out to the Yoke, then routing that Yoke to another instance of MIDIOX worked just fine... Thanks, rs |
||
Title: Re: Perhaps I'm slow, but Patch Mapping is Not Wor Post by Jamie OConnell on Apr 14th, 2004, 12:20pm I'm glad you figured it out. The reason it is necessary to huse a 2nd instance is because of the way patch mapping works: it only reacts to externally applied data. |
||
Title: Re: Perhaps I'm slow, but Patch Mapping is Not Wor Post by ryansupak on Apr 14th, 2004, 1:20pm Perfect. Thanks for the reply... rs |
||
MIDI-OX User Forum » Powered by YaBB 1 Gold - SP 1.3.1! YaBB © 2000-2003. All Rights Reserved. |