ferryb ·
Ok,
My first component. It allows you to extract NRPN messages from MIDI data.
You can download it here http://www.chinaski.org/synthmaker/Midi_NRPN.osm
Please let me know if you have any comments.
From the original SynthMaker forum (2004–2014), with its members’ names and dates.
ferryb ·
Ok,
My first component. It allows you to extract NRPN messages from MIDI data.
You can download it here http://www.chinaski.org/synthmaker/Midi_NRPN.osm
Please let me know if you have any comments.
rl ·
this looks pretty useful, thanks. Q: how does the component handle consecutive NRPN messages?
ferryb ·
rl,
Your comment initiated a brain wave 😉 that lead to this extention:
download: http://www.chinaski.org/synthmaker/Midi_NRPNv2.osm
And to anwser you question: For consecutive NRPN messages, that meet the NRPN MSB and LSB criteria set on the input, first the MSB and LSB data values are set and hold on the output and second the trigger is set on the output.
husker ·
Great!
Now I have to think about NRPN out 🙂
Ruso ·
hmm one flaw with the newer diagram..... NRPN's do NOT have to use all four parameters. They only have to send MSB, LSB, and first dataentry....
so in your example if the NRPM does NOT use a fourth parameter, it will not catch it. This can be fixed by causing the third trigger to cause an update rather then the fourth.
oddson ·
This can be fixed by causing the third trigger to cause an update rather then the fourth.
That will cause it to fire before it's processed the LSB.
You could connect from the MIDI in to the Trigger Switch.
As the fifth output from MIDI it would send a trigger after the other outputs had calculated.
ferryb ·
thanks for the update.
merqlove ·
My NRPN OUT like easy cc
http://www.minimal.su/prv/NOUT.osm
Not seen here. A very important part of any constructor!
Kenshiro ·
merqlove wrote: My NRPN OUT like easy cc
http://www.minimal.su/prv/NOUT.osm
Not seen here. A very important part of any constructor!
Awesome, this is just what I've been looking for!!! The link is dead, but does anyone have this NRPN Out module? (sorry to dig up this old thread...)
oddson ·
I don't have that module... but I think it would just be this:
I assume the LSB should be sent after the MSB.
Klentock1 ·
using your above example oddson, I can't seem to send any data to my synth, it only works if I set the data1 of the midi event module to 6, but when i do this, it transmits to all nrpn parameters in my synth.
any ideas?
trogluddite ·
From what the definition here says http://en.wikipedia.org/wiki/NRPN, these two modules ought to send the data that you need for NRPNs and RPNs. The order of the connections (ticks on the links) inside the modules is important, as the messages must be sent in the order MSB, LSB, Data. They are set up so that a change on the data input will trigger all 3 messages in the correct order.
Not had time to test these fully (I don't have any devices that use NRPNs), so let us know how you get on - it may be that some older devices need a short time delay seperating the three messages, at the moment they get sent as quickly as possilbe.
trogluddite ·
Here's an update to the NRPN receiver module to go with the send module posted above. This better reflects the spec. of the MIDI standard - there is not a requirement to send all 3 (or 4) controllers at once; once CC 98 and 99 are set, data can be continuously sent on CC6, and will carry on changing the same NRPN until there is another CC98 message. There's also no restriction on the order that CC6 and CC38 should be sent - either can be changed at any time.
Note that changing the CC numbers 98,99 to 100,101 will make this work for RPNs - but you have to be careful here; CC6 (and 38) can only function with the most recent RPN or NRPN address received, but not both at once - so you'd need to disable any NRPN receivers if an RPN address was detected (and vice versa).
Klentock1 ·
Thats great thanks Trogludite. I realised I didn't include a third midi event module for CC6. Time to go and kick myself! 😝
Wrote something here? To have a post removed or your name hidden, write to [email protected].