Author |
Topic: converting NRPN's to CC's in 7.0 (RFE / bugfix) (Read 2974 times) |
|
chris_pickett
New Member
MIDI-OX Rules!
Posts: 2
|
 |
converting NRPN's to CC's in 7.0 (RFE / bugfix)
« on: Dec 15th, 2003, 10:11am » |
 Quote  Modify
|
Hi,
Jamie already posted about this in another thread, but I'm starting a new one because that was kind of old.
=============================================
OK. I'll try to explain how I go about setting this up so next time it's not too hard.
We want to map the nrpn with MSB = 0, LSB = 1 to cc = 3.
First we open the nrpn calculator to get the full nrpn parameter number (View | nrpn Calculator...):
MSB LSB nrpn
0 1 1
In this case the parameter still equals 1.
Now we open the Options | Data Mapping... dialog to enter a Mapping, and press [Insert]
we enter the following:
When input matches:
Channel Event Min Value1 Max | Min Value2 Max
Any nrpn 1 1 0 16383
Set Output to:
Channel Event Min Value1 Max | Min Value2 Max
Match Ctrl 3 3 0 127
Notes: The full nrpn parameter is 1 as we calculated earlier. The nrpn value to be mapped is between 0 and 16383 because it can be a 14 bit value when both MSB and LSB of the Data entry controller are supplied (even though we are only receiving the MSB in this case). The target is cc 3 which can have a range of between 0 and 127.
After Pressing OK this all looks like:
* nrpn 1 1 0 16383 | * Ctrl 3 3 0 127
And we check none of the check boxes in the bottom of the translation map.
===============================================
I have a mapping set up like this, and my synth's front panel is sending NRPN's.
However, CC#6 doesn't range all the way from 0 - 127, it only goes up to 31 (it's the A6 Andromeda). When the NRPN value gets converted to my new CC (in the example CC#3), it only ranges from 0 - 31 when I turn the knob.
Is it possible to fix this?
What I would actually like is the following behaviour:
The min NRPN value gets mapped to the min CC value, and the max NRPN value gets mapped to the max CC value. All intermediate NRPN values are scaled appropriately (divide NRPN range by CC range to get the NRPN "step size"). Note that I would like MIDI-OX to take the full 14 bits of the NRPN data value when doing the calculation so that my CC hits every position between 0 and 127, and not just 0,4,8,12, ... 120,124.
I think this would allow for users to do everything that they already do, plus allow for neat MIDI compression and expansion tricks, like I need.
Cheers,
Chris
|
|
 IP Logged |
|
|
|
chris_pickett
New Member
MIDI-OX Rules!
Posts: 2
|
|
Re: converting NRPN's to CC's in 7.0 (RFE / bugfix
« Reply #1 on: Dec 15th, 2003, 10:20am » |
Quote Modify
|
um, sorry.
I fixed my problem by adjusting the max NRPN value to 4095.
MIDI-OX already does what I suggested.
Sorry again! Nice program!
Chris
|
| « Last Edit: Dec 15th, 2003, 10:35am by chris_pickett » |
IP Logged |
|
|
|
Jamie OConnell
Administrator
 
Gender: 
Posts: 2027
|
|
Re: converting NRPN's to CC's in 7.0 (RFE / bugfix
« Reply #2 on: Dec 15th, 2003, 10:39am » |
Quote Modify
|
on Dec 15th, 2003, 10:11am, chris_pickett wrote:
Note that I would like MIDI-OX to take the full 14 bits of the NRPN data value when doing the calculation so that my CC hits every position between 0 and 127, and not just 0,4,8,12, ... 120,124.
I think this would allow for users to do everything that they already do, plus allow for neat MIDI compression and expansion tricks, like I need.
|
|
MIDI-OX does take the full 14 bits into consideration, but will only translate actual messages: it won't generate messages that haven't been issued. This is important as we don't want to clog the data stream. So if your NRPN data entry values sequence as (example) 1, 4, 7, 10; then you will also have 4 CC values after translation.
|
|
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
