![]() ![]() ![]() The manual fader in the live window reflects the up progress. It is also possible to control the manual up and down fades independently. Note: to control an fade manually, you must set the manual level to 0 and then send a "GO" command. The manual fade percentage can be set using a command (where "nn" is the desired level or "%p" to use the next argument). For example, "CC23" controls the red subchannel. Alternatively, you can specify a specific level, ie or Subchannels that do not have faders in the Channel Controls window can be controlled using a combination of "CC" followed by the subchannel number. Left plain, the floating point value of the next argument interpreted as a percentage sets the level of the fader. These commands take the form of "CCIntensity", "CCPan", "CCTilt", "CCBeam", or "CCIris". This prevents accidental remote editing in blind mode.Īction commands are able to control a fader in the Channel Controls window. There is a preference in the MIDI/OSC tab that always switches to live mode when executing a command line type MIDI command. ![]() Note: a "SUB-1" command has the same effect as "sub: except that the former updates more quickly than the command line version. The SUB- command directly sets the level of the submaster to the floating point value of the next argument interpreted as a percentage. A "record!" OSC action command will record over the current cue with no warning.Īction commands are able to directly control submasters using a command of the form "SUB-nn" (where nn is the submaster number). But if the cue exists, there will be a warning. A "record" OSC action command will record the current live state as the current live cue. With OSC, the entire command can be sent as a string argument to an OSC message (the command setup for the OSC message would read simply "%s"). This is useful because marked channels will not be overridden by a submaster and this provides a way to release marked channels without executing a cue.Īny command that can be executed from the command line can also be triggered by an OSC message. "UNMARK" will unmark the channels in live mode. Other OSC actions include "LIVE" which switches the main display to live mode. Other Live window buttons can also be mapped to OSC by entering "BACK", "HOLD", or "STOP". GO commands have two forms: simple "GO" which runs the next cue in the Live window and "GO:%f" which runs the cue number corresponding to the float value of the next argument. Commands with implied levels interpret the next argument as a float which is converted into a percentage. Maps floating point argument in range (min-max) to output (low-high).Ī command of will replace %p with the percentage value corresponding to the 0.0-1.0 float value of the next argument in the list. Each time an argument is requested, the next value on the list is read and the pointer is advanced until there are no more arguments to read.Īrguments can be read as the following types: %fįloat argument from 0.0 to 1.0 becomes 0 to 100Īrgument from 0.0 to 255.0 becomes 0 to 100 Detect allows you to find the appropriate address value by pressing a key or moving a slider to send an OSC message to LXConsole.Īrguments to OSC Messages can be retrieved by reading them off the list of received arguments one at a time. Clicking this button causes OSC input to be enabled. The Detect button allows you to detect received OSC packets. Action commands triggered by OSC can be a command executed from the command line, a "GO" type button command that is run by the Live window, or control of a fader in the Channel Controls or Live window. The OSC tab of the Setup window allows editing of a list of actions that can be triggered from OSC packets via a UDP network connection. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |