Author |
Topic: Problem Mapping MIDI Program Change to Note On (Read 2543 times) |
|
Sined
New Member
MIDI-OX Rules!
Gender: 
Posts: 2
|
 |
Problem Mapping MIDI Program Change to Note On
« on: Sep 29th, 2020, 11:15am » |
 Quote  Modify
|
Hi, I’m new to MIDI-OX, I’m running the MIDI-OX latest version 7.0.2 on WINDOWS 10 ( 64 bits ).
Here is my problem :
I have to translate a MIDI Program Change message into a Note On message.
After reading the MIDI-OX help, I created a Data Mapping to translate incoming MIDI Program Change messages into Note On message. But, the output I get is a Note Off message.
I tried to modify the Data Mapping parameters for different translations :
Ex: Changing Program Change message into Key Aftertouch
EX: Changing Program Change message into Pitch Bend
and for all the above examples I always get the expected result.
And more, if I create a Data Mapping to translate an incoming Control Change message into a Note On message, I get a Note On message on output as expected,
I only get a wrong result ( Note Off ) when I’m trying to translate a Program Change message into a Note On message.
Very odd !!! Could there be a bug or is it me ?
Tks for your help.
|
|
 IP Logged |
|
|
|
Breath
Administrator
Gender:
Posts: 1030
|
|
Re: Problem Mapping MIDI Program Change to Note On
« Reply #1 on: Sep 29th, 2020, 8:18pm » |
Quote Modify
|
Hi
This should be straight forward especially as you have the other mappings working
Program Change only has one data byte where as Note on has key and velocity
Press 'Clear' then 'Insert' buttons
'When Input Matches'
Channel 1, Event Ctrl, CTRL# min=1 max=1 (Modwheel) Amount -1 -1
'Set Output to'
Channel Match output, Event Note on -1-1 -1-1
This does change CC 1 to Note on
If you want the PC data (patch number) to do something then check 'Use Input value 2 (Pull)'
This puts the patch number into Key and Velocity
Set a value (eg Velocity 64 64) and the patch number will only appear in the other data area.
Now, if the velocity is set to 0 in a Note On message then it is treated as Note Off.
The hex number for note on starts with 9 .e.g 90= note on, channel 1, 96 = Note on channel 7
(Right click on the Input Monitor window and select 'display hex' if your numbers are decimal)
The hex number for note off starts with 8 .e.g 80= note off, channel 1, 86 = Note off channel 7
Let me know if this helps
Royce
|
|
IP Logged |
|
|
|
Sined
New Member
MIDI-OX Rules!
Gender:
Posts: 2
|
|
Re: Problem Mapping MIDI Program Change to Note On
« Reply #2 on: Sep 30th, 2020, 9:28am » |
Quote Modify
|
Hi Royce,
Tks a lot for your very fast reply, I really appreciate !!!
After reading your reply I modified my Data Mapping parameters as follows :
=====================================
When Input matches :
Channel = 3, Event Type = ProgChg, -1, -1, -1, -1
Set Output to :
Channel = Match Input, Event Type = NoteOn, -1, -1, 1, 1
=====================================
Now the Data Mapping works very well and every Program Change message received on channel 3 is translated into a NoteOn message.
The problem I had in my previous attempt was caused by setting all 4 boxes of the « Set Output to » section to -1 value, then resulting in a NoteOff message instead of a NoteOn message.
Setting the velocity values ( min and max ) to 1 resolved my problem because I only use the NoteOn message to trigger programmed scenes on a little DMX console ( Model OBEY 40 by Chauvet ) which works this way :
- NoteOn MIDI 00-07 trigger scene 1 to 8 from Bank 1
- NoteOn MIDI 08-15 trigger scene 1 to 8 from Bank 2
etc... etc... the velocity value is not important in my case.
Once again, tks a lot Royce for your help was very helpful and appreciated !!!
Denis.
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print