Assigning two parameters in one encoder (left\right)

3 posts / 0 new
Last post
Cthulhu
Cthulhu's picture
Assigning two parameters in one encoder (left\right)

Thanks for the great software!! I have a noob question. Can I assign two parameters in one encoder so using generic remote in Cubase i would be able to zoom in  and zoom out with the same encoder while turning it clockwise and counter-clockwise?So, basically assign 103 for positve numbers and 104 for negative or something like that? If yes, please be a liitle bit specific as to the steps required as I'm new to this.

Thanks!

Mark van den Berg
Mark van den Berg's picture

You can define two types of output for a single encoder:

1. What BC Manager calls "standard output". (Internally the BCF/BCR themselves call this ".easypar".) This involves a single type of MIDI message, so for instance a MIDI Control Change message using a particular controller on a particular channel.

2. What BC Manager  calls "custom output". (Internally: ".tx".) This can involve almost anything you like, such as multiple MIDI messages.
One of the special tricks this offers is a split between output generated when the encoder is turned clockwise and output generated when the encoder is turned counter-clockwise. See section 14.6.4 of BC MIDI Implementation.pdf for all the details.
To set this up in BC Manager, open the "Custom output" tab of the encoder dialog box and click on the "+" icon.
A dialog box pops up, where you can enter the elements of the definition individually (via another "+" icon), or you can click the "T" icon to enter any number of elements as text.
You'll want to enter something like "ifp $B0 103 val ifn $B0 104 val".
(For clarity you may want to put the two directions on separate lines, so "ifp $B0 103 val" and "ifn $B0 104 val". IIRC it doesn't change the semantics in this case.)
Custom output has one important limitation though. Quoting from section 14.6 of BCMI (p. 49):

... the BC interprets incoming parameter feedback via MIDI only according to the element’s standard output definition; the BC does not use any custom output definitions to synchronize the element’s current Value. In other words, custom output definitions are ‘deaf’.

I'm not sure how this limitation plays out in your Cubase setup.

Hope this helps,
Mark.

Anonymous (not verified)
Anonymous's picture

Thank you Mark for your help!! Much appreciated!! Gonna try it with Cubase and see what happens