any of you got an ESX and a behringer BCR2000?
coud the BCR be programmed to send NRPN to the one-shot/stretch/slice parts on the ESX to change the parameters on them?
if don´t, do you know a midi controller that could do that?
thanks
sending NRPN to ESX
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
thanks rusoRuso wrote:well if your lap top has a part inside the setup I could show you a world of things.... I'm sure you can do it in berhinger, the only "weird" messages are the part mutes because they are a binary representation...
i don´t have a laptop...i was thinking about buying one but i doubt it would be part of my live rig
i never deal with NRPN before...i just read something about the kind of messages involved but it´s a bit confusing to me...or just an stupid solution
can you send 2 parameter at the same time with NRPN?
-
The Puppeteer
- Junior Member
- Posts: 95
- Joined: Tue Oct 30, 2007 4:04 am
- Location: Perth, Western Australia
- Contact:
MIDI is a serial protocol. You can't send 2 of anything at the same time.
NRPN's are like an extension to the MIDI Controllers and they can support double precision data (ie 2 MIDI bytes).
To use them you need to send the following MIDI Messages
1) MIDI CC 99 with the NRPN MSB
2) MIDI CC 98 with the NRPN LSB
(this basically defines the NRPN parameter number)
3) MIDI CC 6 (DATA MSB) with the parameter value MSB
4) (Optional) MIDI CC 38 (DATA LSB) with the parameter value LSB
according to the MIDI spec you can stop here, and continue to send Data messages to control the NRPN. The NRPN will be left open until you send the null bytes
5) MIDI CC 101 value 127
6) MIDI CC 100 value 127
These last 2 messages ensure that the NRPN is closed. The reason you want to do this is because any DATA control message will continue to modify the NRPN until it is closed. It's a good habit to get into to close the NRPN's after each message.
So each full NRPN double precision message requires 13 bytes (using running status). Single precision (ie just sending the DATA MSB controller uses 11 bytes.
You can find an in depth discussion on NRPN's here
http://www.philrees.co.uk/nrpnq.htm
NRPN's are like an extension to the MIDI Controllers and they can support double precision data (ie 2 MIDI bytes).
To use them you need to send the following MIDI Messages
1) MIDI CC 99 with the NRPN MSB
2) MIDI CC 98 with the NRPN LSB
(this basically defines the NRPN parameter number)
3) MIDI CC 6 (DATA MSB) with the parameter value MSB
4) (Optional) MIDI CC 38 (DATA LSB) with the parameter value LSB
according to the MIDI spec you can stop here, and continue to send Data messages to control the NRPN. The NRPN will be left open until you send the null bytes
5) MIDI CC 101 value 127
6) MIDI CC 100 value 127
These last 2 messages ensure that the NRPN is closed. The reason you want to do this is because any DATA control message will continue to modify the NRPN until it is closed. It's a good habit to get into to close the NRPN's after each message.
So each full NRPN double precision message requires 13 bytes (using running status). Single precision (ie just sending the DATA MSB controller uses 11 bytes.
You can find an in depth discussion on NRPN's here
http://www.philrees.co.uk/nrpnq.htm
The Puppeteer
http://godlike.com.au
http://godlike.com.au