2014-08-25 by rpcfender@...
You way you use the Values (and how many there Values there are) depends on what the Type is (these are all Mark's terms in his fantastic "BC Midi Implimentation.pdf" from his website)
But in also depends on if it is for the encoder or the button.
If you want an encoder to go backwards (decreases as you go clockwise) you swap the values.
When you want a button to step backwards you make the step size negative.
$encoder 1 ; normal
.easypar CC 1 7 0 127 absolute
$encoder 2 ; backward
.easypar CC 1 7 127 0 absolute
$button 1 ; normal
.easypar CC 1 7 127 0 increment 1
$button 2 ; backward
.easypar CC 1 7 127 0 increment -1
This is also confusing when you want to match the .showvalue on the BC to the actual value you put out.
$button 3 ; On = 127 , Off = 0
.easypar CC 1 7 127 0 toggleon
$button 4 ; On = 0 , Off = 127
.easypar CC 1 7 0 127 toggleon
Why? Just the designers view of how it should be.
It seems like we were never meant to see any of this stuff anyway.
Glad to hear you got is sorted.
All the best
Royce
---In bc2000@yahoogroups.com, <dbranche1030@gmail.com> wrote :
Thanks for pointing that out Royce.. problem solved!! YOU’RE THE MAN! Quick question though.. what is it about swapping the min max that makes this possible? Also, when looking at a button in BCMan I noticed that the increment values also go to the (-) negative.. Might you be able to put that into context for me as well? Thanks again!
dB
From: bc2000@yahoogroups.com [mailto:bc2000@yahoogroups.com]
Sent: Sunday, August 24, 2014 7:17 PM
To: bc2000@yahoogroups.com
Subject: [bc2000] Re: Assigning BCR2000 buttons to control VST function with more than 3 or more values??
A common mistake when using increment on a button is to have the max min values reversed.
The max value comes first.
.easypar CC channel CCtype max min increment stepsize
.easypar CC 1 7 120 0 increment 10 ;this is a 12 step volume control on channel 1