![]() ![]() Before you can use OSC Features you also need to configure an OSC device. Unlike MIDI Input, OSC Features are enabled for the entire ruleset, with patterns being defined per rule. Similar to MIDI Input, you can enable or disable OSC Features by clicking the 'More' button in the rule toolbar. Also, having disabled the MIDI Input will not prevent the rule from creating MIDI messages of its own. Note that even when MIDI Input is disabled for the rule, it is still possible for other rules to send message to the rule via routing. Exactly which aspects are available depend on the type of message, and whether it is an OSC or MIDI-message. Actions also include custom Lua functions, which allow you to access the Renoise API directly (see the xRules Lua Reference below)īoth Conditions and Actions are applied to certain aspects of a message. Each step can change something about the message, such as its value or intended output device. This makes it possible to create a more complex logic: WHEN - AND - OR - AND - THEN.Īctions define what to do with the message as it passes through the rule. However, it is possible to click the AND label, and toggle between AND and OR logic. ![]() Only messages that match this criteria are passed on.īy default, conditions assume AND logic, meaning that all conditions you define needs to be true in order for the rule to match (think of it as plain language: the initial condition is WHEN, followed by "AND some other condition"). For example, you could look for a message with a MIDI channel higher than 5, or a message whose first data byte is exactly 127. In the user-interface, 'WHEN' makes up the upper part of the rule-editor, while 'THEN' is the lower part.Ĭonditions are criteria that you can freely define.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |