Author |
Topic: mapping affects keyboard notes (Read 979 times) |
|
rattleandhum
New Member
MIDI-OX Rules!
Posts: 2
|
 |
mapping affects keyboard notes
« on: Oct 24th, 2005, 4:39pm » |
 Quote  Modify
|
Hey there,
I'm having an issue currently with Midi-OX. I have mapped out a midibox I have built (midi controller with 64 inputs/cc possibilities), and the box runs fine, though the incomming midi cc numbers are fairly random, as in some come in on channel 9, #92, and others come on 4, #7 or channel 12, #93..you get the picture. Anyhow, I mapped it out to all go to channel 1 and to work with my Native instruments B4 program. It worked great. Then I hooked up my keyboard.
Now there are two notes on the keyboard (D above middle C and G I believe two octaves above middle C) that when you hit the note on the keyboard, out from MIdi-ox (through Midi-yoke out 1) comes an F, or G# or something like that. I changed what channel the keyboard comes in on, and it changes the notes that are incorrect comming out of midi-ox. Finally, I found one channel that fixed one of the notes, but not the other (I think it was channel 7).
Finally, if I turn the mapping function "off" in Midi-ox, everything runs fine! Anyone know whats happening here?
|
|
 IP Logged |
|
|
|
Jamie OConnell
Administrator
 
Gender: 
Posts: 2027
|
|
Re: mapping affects keyboard notes
« Reply #1 on: Oct 24th, 2005, 5:43pm » |
Quote Modify
|
Quote:| Finally, if I turn the mapping function "off" in Midi-ox, everything runs fine! Anyone know whats happening here? |
|
I think you have your answer right there: it must be the particular mapping that you're employing that is changing the notes. If 'everything runs fine', why are you using mapping at all?
Quote:| Now there are two notes on the keyboard (D above middle C and G I believe two octaves above middle C) that when you hit the note on the keyboard, out from MIdi-ox (through Midi-yoke out 1) comes an F, or G# or something like that. |
|
I'm confused here. If you have a Hardware MIDI Keyboard attached to the computer via a hardware MIDI interface, then why and how would you be using MIDI Yoke at all?
|
| « Last Edit: Oct 24th, 2005, 5:47pm by Jamie OConnell » |
IP Logged |
--Jamie
Music is its own reward.
|
|
|
rattleandhum
New Member
MIDI-OX Rules!
Posts: 2
|
|
Re: mapping affects keyboard notes
« Reply #2 on: Oct 24th, 2005, 7:09pm » |
Quote Modify
|
Sorry..when I say that I turn off the midi Mapping and "everything runs fine" I mean that my midi keyboard plays correctly in that every note you play correctly communicates to be the right note comming out of MidiOX.
Here is my setup. I have a Kurtzweil PC88mx keyboard running through a turtlebeach 1x1 into the computer. My midibox merges with the keyboard signal at the keyboard.
I am using both to control VST's in the EnergyXT Host. I am using the MIDI Yoke because I understood you needed that in order to use the mapping function of MidiOX in EnergyXT. (In EnergyXT I could get my midi signals directly from the turtlebeach 1x1 but I wouldnt get the cc re-map from midiOX)
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
Gender:
Posts: 2027
|
|
Re: mapping affects keyboard notes
« Reply #3 on: Oct 24th, 2005, 10:15pm » |
Quote Modify
|
Thanks for the explanation -- it makes sense.
You can see what note are coming into MIDI-OX by using the Input Monitor. You can further see how they are mapped by viewing the Output Monitor (main monitor). If it seems that the mapping does not do what you expect, you can save a text version of the map in the Options | Data Mapping dialog (save as .txm), and then paste it into a message here.
In some odd cases we've seen the SysMap file get corrupted. As a work-around for that you can save your map (.oxm or .txm), exit MIDI-OX, go to the MIDI-OX folder, C:\Program Files\MIDIOX by default, and delete any _MOXSYSMAP*.oxm files. Then relaunch MIDI-OX and re-import your map.
|
|
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