To get the values of only one particular continuous controller, use the ctlin object, or use the route object to parse the controller data coming out of midiparse. To change one range of values into another, use simple math (usually one multiplication and one addition will be enough), or use the scale object.
To create an inlet for a subpatch that accepts both signals and data, try using t signal. See the patch example for this implementation within the subpatcher.
Here’s a way to create a four-way audio crossfader.
Here’s a way to store all of matrixctrl’s settings in a jit.matrix, and recall them whenever the matrixctrl is resized by messages. The maximum size is set at 32×32, but you can modify it to suit your needs.
In this example, you can play notes by pressing the mouse on the kslider object, and when you release the mouse, the notes will be turned off. When the mouse button is released, that fact is reported by a 0 from the left outlet of the mousestate object.
If you have a patch in which you are flashing a button object using metro, the flashing may be delayed due to different degrees of operation priorities when used in a more complicated patch. Here are few things to consider if you’d like to prioritize or have more control over the flashing.
This patch shows how to use line with lcd to create a moving image.
Coordinates in lcd refer to the upper-left corner of a pixel. "0 0" refers to the upper-left corner of the lcd, and also refers to the upper-left corner of cell 0 0 in a jit.lcd. In a default-sized lcd with dimensions 128×128, the coordinate “128 128” refers to the upper left corner of the pixel that is just beyond the lower right corner of the lcd, i.e., just beyond the edge of the lcd (and beyond the matrix of a jit.lcd).
There are several ways to initialize UI objects, but the data is not stored with the object itself (except for the Live objects). Triggering an initializing message to the object with loadbang is one way. See also loadmess, patcherargs, and pattr.