DESCRIPTION
With OS 1.10, stock BCR2000 accept setups where buttons, including Push-encoders, can be configured to generate incremental Program change, something highly practical to safely explore sound banks of any sound module.

Example of a 2-buttons setup that I am using to explore up and down a sound bank on channel 1 (could be any valid MIDI channel), and that works just fine (fields 1 to 8):

- To increment the actual program number : [$button 17]  (TYPE: "PC") (CH: "1") (PAR: "Off") (VAL1: "Off") (VAL2: "0" ) (MODE: "Inc" ) ("1")  ("On")

- To decrement the actual program number: [$button 25]  (TYPE: "PC") (CH: "1") (PAR: "Off") (VAL1: "Off") (VAL2: "0" ) (MODE: "Inc" ) ("-1") ("On")

Pushing the button 17 increments the actual program number on channel 1 (assuming there is a valid program on that number)

Pushing the button 25 decrements the actual program number on channel 1 (assuming there is a valid program on that number)

PROBLEMS (using BCManager 4.1.0 64 bits)

1. Using BCManager to receive that particular configuration from the B-Control truncates the data (the "increment" parameter disappears)
2. Forcing the right configuration by manually editing the bcr file in order to restore the "increment" parameter results in the following error when loading the edited file with BCManager (with the goal to forward it to B-Control) :

Line xxx : .easypar PC 1 off off 0 increment 1

Error 14 : Invalid number of arguments

I believe 1) and 2) are shorcomings in the actual version of BCManager's BCL implementation.

Other than that, beautiful work :)

Cheers,

DrBlue
--
PhD in Computer Science