Author |
Topic: DX7 multiple function mapping (Read 1957 times) |
|
Nanoboss
New Member
MIDI-OX Rules!
Posts: 4
|
 |
DX7 multiple function mapping
« on: Jul 1st, 2019, 6:34pm » |
 Quote  Modify
|
Hi,
I have a Yamaha DX7II FD, and as it is already known, it and the original DX7 as well has upper velocity limitation problems being difficult to reach more than 99 unless you hit it with a hammer. Not problems while I use VST utilities to scale/transform the velocity input in real time, but it requires the use of a vst host and sometimes I just need to connect my DX7 to an external module without any intermediaries except Midi-ox.
The problem is I have not been able to create a data translation map that allows me to scale the velocity to a certain percentage and at the same time get two octaves low in order to access my GM drum kits from starting at C3 key of my DX7instead the default C1. (I also set the map to midi channel 10 (GM) in output, since I have my dx7 usually in ch.1 as transmit channel.)
I used some maps included in m-ox as starting point, but when combining octaves and velocity up, weird things happen as the sounds are hold as if the sustain pedal were on. Also when I hit a velocity value greater than 4 the midi note number get changed, for example a snare become in cymbal.
What should I do? I am not yet proficient in the use of mapping variables, sorry.
|
| « Last Edit: Jul 1st, 2019, 6:37pm by Nanoboss » |
 IP Logged |
Midi-ox, the TOOL!!
|
|
|
Breath
Administrator
Gender: 
Posts: 1030
|
|
Re: DX7 multiple function mapping
« Reply #1 on: Jul 2nd, 2019, 3:09am » |
Quote Modify
|
Hi
I tried this - transpose down 2 octaves (24 semitones)
Input
Channel Any(?), Event Type=NoteOn, (Min= 36 Note# Max=96) (Min=0 Velocity Max=99)
Output
Channel Match Input, Event type=Match Input, (Min= 12 Note# Max=72) (Min=0 Velocity Max=127)
But, as you point out, you get the translation of the velocity changing the Note number (a MidiOx bug I would say)
To get around this you need MidiYoke (or loopMidi).
Connect in MidiOx
DX7 -> MidiYoke1
MidiYoke1 -> Drum
You also need two data maps - first the note change (-1 means any value)
Input
Channel Any(?), Event Type=NoteOn, (Min= 36 Note# Max=96) (Min=-1 Velocity Max=-1)
Output
Channel Match Input, Event type=Match Input, (Min= 12 Note# Max=72) (Min=-1 Velocity Max=-1)
Save the DataMap as DX7toDrum Note.oxm
Next the velocity...
Input
Channel Any(?), Event Type=NoteOn, (Min=-1 Note# Max=-1) (Min=0 Velocity Max=99)
Output
Channel Match Input, Event type=Match Input, (Min=-1 Note# Max=-1) (Min=0 Velocity Max=127)
Save it as DX7toDrum Vel.oxm
On the MIDI Port Routing window...
where you connected the DX7 -> MidiYoke1 click the small square on the line joining and in the Map File box select DX7toDrum Note.oxm
where you connected the MifiYoke1 -> Drum select the map DX7toDrum Vel.oxm
The DX7 note number is changed first and sent to MidiYoke1 which returns it to MidiOx where the velocity is scaled and sent to the Drum.
Sorry it is a bit complex, but it works
All the best
Royce
|
|
IP Logged |
|
|
|
Nanoboss
New Member
MIDI-OX Rules!
Posts: 4
|
|
Re: DX7 multiple function mapping
« Reply #2 on: Jul 2nd, 2019, 6:22am » |
Quote Modify
|
Thank so much! it worked like a champ! maybe a bit more time consuming than complex since both maps must to be kinda "hardcoded" in the MIDI Port Routing because of double routing, them could not be edit/modified but in the Translation Map.
Luckily in this case I could simplify a little by a change in the chain. I did put only the map 'DX7toDrum Note.oxm' in DX7 -> MidiYoke1 in the MIDI Port Routing and opened the map 'DX7toDrum Vel.oxm' in the Translation Map window and it work without problem!
I did it this way because while I don't need to change octaves frequently, I usually have drum kits with different sensitivity settings, so it is convenient for me to be able to modify the values of the velocity curve "on the fly" in the map.
As a side note, before you post this I tried again and I got velocity scale and transpose right and the Note Number unaltered when hit different velocity values (then maybe not bug there) but the sustain problem remained the same. Useless.
Thankful again for your quick and effective help! I would like there to be a more detailed guide to the different functions of the mapping and its possible pros and cons.. I imagine that browsing the forum is the key to learn a lot about it and other areas.
Nice regards
Carlos
|
| « Last Edit: Jul 2nd, 2019, 6:44am by Nanoboss » |
IP Logged |
Midi-ox, the TOOL!!
|
|
|
Nanoboss
New Member
MIDI-OX Rules!
Posts: 4
|
|
Re: DX7 multiple function mapping
« Reply #3 on: Jul 2nd, 2019, 6:59am » |
Quote Modify
|
Last minute update:
I just realized that by setting in the MIDI Port Routing a normal interface connection (no transformer chains) IN (Dx7) and OUT (to ext module) and placing there the 'DX7toDrum Note.oxm' map and the 'DX7toDrum Vel.oxm' map in the Translation Map window, just like I did, it does not need to use MIDIYoke/loopmidi. It work flawless.
|
| « Last Edit: Jul 2nd, 2019, 7:07am by Nanoboss » |
IP Logged |
Midi-ox, the TOOL!!
|
|
|
Breath
Administrator
Gender:
Posts: 1030
|
|
Re: DX7 multiple function mapping
« Reply #4 on: Jul 3rd, 2019, 12:29am » |
Quote Modify
|
Well done.
You are quite correct about using the Global Data Map as one of the 'translations', but if you do, you then can't use any other connections in MidOx without MidiOx also translating it that new Midi stream.
In your case it isn't important, but if you need to expand your Midi mapping you'll have a solution.
All the best
Royce
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print