Quote:
Originally Posted by pipelineaudio
so x:y=z
x is channel
y is cc#
and z is cc value?
|
Yep.
And just
x:y
simply means the CC value is 0. This might be useful when triggering actions (as initially requested), as the learning seemingly ignores the CC value.
See above ->
https://forum.cockos.com/showpost.ph...6&postcount=33
Quote:
Originally Posted by mschnell
The file format is:
- Each line is associated with an incoming CC # (similar to LiveConfigs) (0, 1, 2, ...).
- Each line has up to 64 CC definitions which are separated by a blank (a "/" starts a comment up to the end of the line)
- empty lines are allowed, resulting in a nonexistent row that will not respond to it's input CC value.
- a CC definition can have two or three elements:
. - Midi Channel followed by a colon
. - CC #
. - CC value (optionally, if present separated by a "="), otherwise Zero is assumed)
|
This has been enhanced with later versions by allowing a ">" for CCs to be sent when a row is deselectiod in "Configs" mode, and by allowing multiple blanks instaed of a single.
The wording "Each line is associated with an incoming CC # " definitely is misleadiung, as there is a single CC # defined by a slider the pluging listens to. While the CC value of same is associated to the row number. My apologize if that caused confusion
. But this is exactly like LiveCionfigs works.
-Michael