Jump to content
Sign in to follow this  
DukeOfBoom

Does CC stand for Control Change?

Recommended Posts

It's control change.

 

http://www.midi.org/techspecs/gm.php

 

Control Change Messages (Some Optional)

- Bank Select (cc#0/32)

- Modulation Depth (cc#1)

- Portamento Time (cc#5)

- Channel Volume (cc#7)

- Pan (cc#10)

- Expression (cc#11)

- Hold1 (Damper) (cc#64)

- Portamento ON/OFF (cc#65)

- Sostenuto (cc#66)

- Soft (cc#67)

- Filter Resonance (Timbre/Harmonic Intensity) (cc#71)

- Release Time (cc#72)

- Attack time (cc#73)

- Brightness (cc#74)

- Decay Time (cc#75) (new message)

- Vibrato Rate (cc#76) (new message)

- Vibrato Depth (cc#77) (new message)

- Vibrato Delay (cc#78) (new message)

- Reverb Send Level (cc#91)

- Chorus Send Level (cc#93)

- Data Entry (cc#6/38)

- RPN LSB/MSB (cc#100/101)

Share this post


Link to post
Share on other sites

It's control change.


http://www.midi.org/techspecs/gm.php

 

Well, it would seem that either term is accurate. On the same site, see the MIDI glossary at:

 

http://www.midi.org/aboutmidi/glossary.php

 

"CONTINUOUS CONTROLLER: A MIDI message tailored to parameters that require a range of multiple values such as modulation depth or volume. CCs can be controlled in real time by knobs, sliders, wheels, etc. or can be input as a series of parameter values into a MIDI sequence."

Share this post


Link to post
Share on other sites

A typical device with MIDI has certain "Continuous Controllers".

Examples:

Continuous Controller #1 = Modulation Wheel

Continuous Controller #2 = Breath Control

Continuous Controller #7 = Volume

 

MIDI data that can change the parameter value of those controllers are "Control Change" messages. People tend to refer to either "Continuous Controller" or "Control Change" as "CC".

 

CC messages are of the form "Status Byte - First Data Byte - Second Data Byte". In decimal, the status byte for a CC command can be any one from 176 through 191, with 176 being for MIDI channel 1 and 191 for channel 16. The first data byte is the controller number. The second data byte is the value (which can range from 0 to 127) for that controller.

Examples (in decimal):

176 1 63 ---- For MIDI channel 1, set the modulation wheel value to a mid-point

180 7 127 --- For MIDI channel 5, set volume to maximum

 

Due to all that and for other reasons, I tend to keep my (5-pin) DIN plugged IN (although lately it's also USB, Ethernet, ...). :)

Share this post


Link to post
Share on other sites

A typical device with MIDI has certain "Continuous Controllers".

Examples:

Continuous Controller #1 = Modulation Wheel

Continuous Controller #2 = Breath Control

Continuous Controller #7 = Volume


MIDI data that can
change
the parameter value of those
control
lers are "Control Change" messages. People tend to refer to either "Continuous Controller" or "Control Change" as "CC".


CC messages are of the form "Status Byte - First Data Byte - Second Data Byte". In decimal, the status byte for a CC command can be any one from 176 through 191, with 176 being for MIDI channel 1 and 191 for channel 16. The first data byte is the controller number. The second data byte is the value (which can range from 0 to 127) for that controller.

Examples (in decimal):

176 1 63 ---- For MIDI channel 1, set the modulation wheel value to a mid-point

180 7 127 --- For MIDI channel 5, set volume to maximum


Due to all that and for other reasons, I tend to keep my (5-pin) DIN plugged IN (although lately it's also USB, Ethernet, ...).
:)

 

Could you explain a bit how it works with NRPN values? From what I gather, you use CCs 98 and 99 to tell everyone that you've got some NRPN values coming up, and somehow you use CC's 38 and 6 to represent the data portion...? Thanks.

Share this post


Link to post
Share on other sites

Could you explain a bit how it works with NRPN values? From what I gather, you use CCs 98 and 99 to tell everyone that you've got some NRPN values coming up, and somehow you use CC's 38 and 6 to represent the data portion...? Thanks.

Yes, I could explain it, but a short Google search turned up this:

http://www.cakewalk.com/support/Docs/RPNandNRPN.asp

 

I think that explanation is pretty thorough, but if you still have questions after reading it, just ask.

Share this post


Link to post
Share on other sites

It's control change.

Yes. While MIDI does support continuous controllers, CC messages are Control Change messages. Evidence of the logic of that are

- Hold1 (Damper) (cc#64)

- Portamento ON/OFF (cc#65)

which are control changes for simple on/off functions, and not continuous over a 1-127 range. (I'm talking about the traditional use of #64 for the past 30 years, before the more recent expansion to support of half-pedaling.)

Share this post


Link to post
Share on other sites

- Hold1 (Damper) (cc#64)

- Portamento ON/OFF (cc#65)

which are control changes for simple on/off functions, and not continuous over a 1-127 range. (I'm talking about the traditional use of #64 for the past 30 years, before the more recent expansion to support of half-pedaling.)

Yes, but to clarify this -- the entire range of 0-127 can be used even for those that only have two possible states. The MIDI spec says that a value of 63 or less should be interpreted as "off", while 64 or greater should be "on". More typically, people tend to use 0 (zero) for "off" and 127 for "on", and less often the intermediate values.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...