| 1 |
MIDI-OX / Mapping Questions / I can't make sense of Program Change Mapping! |
May 12th, 2025, 7:30pm |
| Started by SethPaw | Last post by SethPaw |
Here's the story because that's how I can best explain my needs:
I've got some MIDI compositions made for MT-32 playback. They only use default patches, and contain no special SYSEX for custom instruments. Nice and simple.
I've also got a Roland E-20 keyboard, which contains the same mainboard (therefore default sounds) as the MT-32, but the instruments are all swapped around.
Instead of manually changing the patches around and setting an instrument to Harpsichord 1 when I really want Syn. Brass 1, I turned to my good old friend MIDI-OX. I've only ever used it for basic routing, now I want to use it to map the incorrect patch numbers to the correct ones so that my music sounds right without having to edit each file.
I had an issue. I couldn't make sense of the "Patch map" window! What do I need 128 map files for? I can't just punch in input and output numbers. Then I came across the "Translation map" feature, which was a hell of a lot easier for me to understand. I threw the two patch lists into excel and did some editing to create a TXM, here's a snippet:
Code:
*,ProgChg,0,0,*,*,Y,0,*,ProgChg,64,64,*,*
*,ProgChg,1,1,*,*,Y,0,*,ProgChg,65,65,*,*
*,ProgChg,2,2,*,*,Y,0,*,ProgChg,66,66,*,*
*,ProgChg,3,3,*,*,Y,0,*,ProgChg,0,0,*,*
|
|
When I loaded the file, the parameters came up just fine. When I tested it, nothing changed! What's up with that? clicking "Show Currently Selected MIDI Devices" shows everything I expect:
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
DEVICE INFORMATION
IN: 2) LoopMidi1
OUT: 3) U2MIDI Pro
In: 2) LoopMidi1
Details/Chan: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,CM,RT,Sx
Port Data Map: "MT-E20.OXM"
In: MIDI-OX Events
Details/Chan: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,CM,RT,Sx
Port Data Map: "MT-E20.OXM"
The virtual MIDI cable coming from my MIDI editor, my USB adapter going to my E-20, and the maps applied. What's going on? It's gotta be me, right? |
 Reply  Quote  Notify of replies
|
| 2 |
MIDI-OX / Mapping Questions / Re: Remaping CC controles in old ProjectMix |
May 4th, 2025, 1:05pm |
| Started by Waxko | Last post by Waxko |
Hi Royce!!
Once again thank you so much for your answer.
Sorry for the confussion about CC00. I wished to say CC01 really.
Anyway your wide answer is enough for me. I thought MIDI-OX could change the original mapping and I can get the CC01 control on #3 fader permanently.
But you have showed the way to get the ProjectMix faders connected to Cubase with CCxx I want.
Thanks you again.
Jorge
|
|
Reply Quote Notify of replies
|
| 4 |
MIDI-OX / Questions and Discussion / Re: Midi-OX on W11 |
Apr 5th, 2025, 6:19am |
| Started by Mattia | Last post by ric1234 |
Confirmed, MIDI-OX on W11 works fine.
Another virtual cable option is LoopBe1/30 depending on the MIDI client(s) you're using. See my post were I've tested many combinations. |
|
Reply Quote Notify of replies
|
| 5 |
MIDI-OX / Questions and Discussion / Re: Configuration between Starrypad and FreeStyler |
Apr 5th, 2025, 6:13am |
| Started by ric1234 | Last post by ric1234 |
Quick update - I've finally managed to make this work!
The solution for FreeStyleDMX was to use MIDI-Yoke as a virtual MIDI cable. This one seem to work great with MIDI-OX (no surprise  ).
I was just facing difficulties installing it under Windows 11. I've managed to install it running the installer in Compatibility mode "with previous Windows versions"...
I am not 100% sure this is stable, since sometimes my FreeStyler just hangs for a few seconds after sending him MIDI commands...
I guess I will have to test longer now.
It also work because FreeStyler is a 32bits app that MIDI-Yoke can talk to.
For Rekordbox, since this is a (quite picky probably) 64bits app, it simply does not see MIDI-Yoke ports as MIDI inputs. For this one, I had to use LoopBe1, a more recent virtual MIDI cable, and the only one that RekordBox is willing to see as an additional MIDI input!
Therefore, my final configuration is :
StarryPAD => MIDI-OX => MIDI-Yoke1 => FreeStylerDMX (on one side), and MIDI-OX => LoopBe1 => Rekordbox (as second MIDI-OX output)
No Filtering, no mapping in MIDI-OX, just a simple 1 input to 2 outputs attachement.
Next step is to test for much longer now!
I hope this might be useful to someone else maybe.
Thanks again for these great MIDI software  |
|
Reply Quote Notify of replies
|
| 6 |
MIDI-OX / Map Exchange / Re: Dynamic velocity mapping |
Mar 31st, 2025, 7:12pm |
| Started by Wlodzislaw | Last post by Breath |
Hi
you can create data maps to map, say CC7 to a different CC7
You can do it by blocks of ranges of values... each block needs a line in the datamap.
Any number of blocks - 128 blocks would be mapping each possible value, but you could use just one block 1 to 127 to compress to 80 to 127 - leaving 0 to pass though as off
Here a simple but slightly crazy example
Line1 ...
Input CC7 0 to 40 Output CC7 0 to 80 this will expand input of values between 0 to 40 to fit into 0 to 80 ( it will skip some values) and pass 41 to 127
Line2 ...
Input CC7 41 to 67 Output CC7 67 to 41 this will reverse the 41 to 67 providing weirdness - 41 to 67 have been used so it will pass on 68 to 127
Line3 ...
Input CC7 68 to 127 Output CC7 100 to 127 this will give a boost to the start of the loud block and reduce the boost to 0 by the time you get to 127
Hope that helps
All the best
Royce |
|
Reply Quote Notify of replies
|
| 8 |
MIDI-OX / Questions and Discussion / Re: F2 pointeur de position , F3 song select RS700 |
Mar 24th, 2025, 8:46pm |
| Started by percepsion | Last post by Breath |
Hi,
A Sysex message always starts with F0 then any amount of data (although MicroSoft says is should be no greater than 256 bytes and their drivers must break it up) then finishes with F7
Data bytes are always between 00 and 7F (that is less than 80 )
F3 is Song Select message and has one byte of data.
That is F3 00 to F3 7F (Song 0 to Song 127)
If you are wrapping that message inside a sysex message ie F0 F3 01 F7 you can see the first data byte is greater than 7F which is generally an error.
So your file just needs to have F3 song#.
I looked at the manual for the RS7000 but I could not see a sysex parameter for Style that could be sent separately.
It was only a quick look and I think I would need the unit to work it out.
Hope this helps. If not post again.
All the best
Royce |
|
Reply Quote Notify of replies
|
| 9 |
MIDI-OX / Questions and Discussion / Just thanks |
Mar 22nd, 2025, 4:46pm |
| Started by hello_again | Last post by hello_again |
Returning here, to download MIDIOX again after decades. I remember Midimon.
Thank you . I think I even paypaled once. (and now twice.)
I used the FM driver and some other driver by a russian fellow that exposed the DSP and had two SBlive cards in some kind of a cross-loop. |
|
Reply Quote Notify of replies
|
| 10 |
MIDI-OX / Mapping Questions / Re: Mapping Velocity |
Mar 20th, 2025, 7:09pm |
| Started by edimarcristo | Last post by Breath |
There is really only one way to do this and that is to use the Scripting function.
You need to write a script that ...
Selects an incoming black note by comparing the incoming MidiOn key to a list of possible black key numbers
Read the Velocity and subtract 15.
Output the changed message.
The trick here is that you need to do some coding.
Check the Help menu option to read about Scripting
Jamie has provided some examples and were installed in your MidioOx program location subdirectory '/WHS'
Here is an answer to a similar problem that contains a script example by me that you can download and edit...
http://www.midiox.com/cgi-bin/yabb/YaBB.pl?board=MOXScript;action=displa y;num=1657511134;start=0#0
All the best
Royce |
|
Reply Quote Notify of replies
|
Return to the board index.
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register