hi,
is there any way to switch Local controls on and off via a remote MIDI command?
thanks
d
Local on/off via MIDI
- RL
- Posts: 760
- Joined: Wed May 19, 2004 4:17 am
- Location: http://www.moogmusic.de/
- Contact:
Re: Local on/off via MIDI
Yes:
hex:
B0, c = 7A, v = 0: Local Control Off
B0, c = 7A, v = 7F: Local Control On
decimal:
176, c = 122, v = 0: Local Control Off
176, c = 122, v = 127: Local Control On
hex:
B0, c = 7A, v = 0: Local Control Off
B0, c = 7A, v = 7F: Local Control On
decimal:
176, c = 122, v = 0: Local Control Off
176, c = 122, v = 127: Local Control On
http://www.moogmusic.de/index2
-
- Posts: 8
- Joined: Thu Jan 16, 2014 9:14 pm
Re: Local on/off via MIDI
thanks!
need a little deciphering i'm afraid: for decimal, c is Controller number, v is Value, but what's 176?
d
need a little deciphering i'm afraid: for decimal, c is Controller number, v is Value, but what's 176?
d
Re: Local on/off via MIDI
176 is the "status byte" for control change (cc) sometimes call continuous controller or other things
But decimal 176 represents channel 0, 177 would be channel 1.
A complete midi message has the first four bits set to the status byte which is really a 1/2 of a byte (4 bits), the next 4 bits is reserved for the Midi channel number 0 to 15 (1..16).
The 2nd byte is the controller number or cc#, typically from 0 to 119 (the top 8 are reserved)
The 3rd byte is the parameter value from 0..127 (unless it's 14 bit midi in which case two message are required but this is a binary type of setting so not applicable).
if you are programming this from a Midi keyboard, you merely need to know the cc# (0x7a or 122 decimal) and the value (either 0 or 127). The midi channel is typically identified on a menu somewhere within your keyboard.
Make sense?
But decimal 176 represents channel 0, 177 would be channel 1.
A complete midi message has the first four bits set to the status byte which is really a 1/2 of a byte (4 bits), the next 4 bits is reserved for the Midi channel number 0 to 15 (1..16).
The 2nd byte is the controller number or cc#, typically from 0 to 119 (the top 8 are reserved)
The 3rd byte is the parameter value from 0..127 (unless it's 14 bit midi in which case two message are required but this is a binary type of setting so not applicable).
if you are programming this from a Midi keyboard, you merely need to know the cc# (0x7a or 122 decimal) and the value (either 0 or 127). The midi channel is typically identified on a menu somewhere within your keyboard.
Make sense?
'76 Minimoog, Taurus 3, Oberheim FVS + Son of 2-voice; Sequential ProOne; Juno 106; Moog Model 15; Kurzweil 250; Hammond M3; and a handful of Fender Basses Flickr!
-
- Posts: 8
- Joined: Thu Jan 16, 2014 9:14 pm
Re: Local on/off via MIDI
thanks for that!
i'm programming this in Ableton—if my channel numbers are 1 thru 16, does 176 represent channel 1?
d
i'm programming this in Ableton—if my channel numbers are 1 thru 16, does 176 represent channel 1?
d
Re: Local on/off via MIDI
Sorry, yes. 176+0 = channel 1. I even confuse myself counting from 0 sometimes!
Have a look at the midi specification; v1.0 will suffice. It's here: http://www.midi.org/techspecs/midimessages.php
"122" is a standard, reserved command for Local; there is a note in the specification specifically for it.
Have a look at the midi specification; v1.0 will suffice. It's here: http://www.midi.org/techspecs/midimessages.php
"122" is a standard, reserved command for Local; there is a note in the specification specifically for it.
'76 Minimoog, Taurus 3, Oberheim FVS + Son of 2-voice; Sequential ProOne; Juno 106; Moog Model 15; Kurzweil 250; Hammond M3; and a handful of Fender Basses Flickr!
-
- Posts: 69
- Joined: Wed May 09, 2012 9:13 am
Re: Local on/off via MIDI
In Ableton Live , just use CC 122. Live can't send raw MIDI msgs anyway.