You may override the config.yml location with the environment variable APP_CONFIG_FILE, e.g.: APP_CONFIG_FILE=/a/b/c/d/osc.yml. From a birds eye view,

Search code, repositories, users, issues, pull requests...

submited by

Style Pass

2024-12-02 18:30:06

You may override the config.yml location with the environment variable APP_CONFIG_FILE, e.g.: APP_CONFIG_FILE=/a/b/c/d/osc.yml.

From a birds eye view, oscbridge provides a central "message store", to which "osc sources" can publish messages. Every time a new message arrives, each action is checked, if their trigger_chain conditions are resolving to true based on the current store. If every the trigger chain resolves to true, then the action's tasks are executed.

Then there are two actions defined, "to_pulpit" and "to_stage". Each has a single trigger, that matches /ch/01/mix/on to be 0 or 1.

Whenever the internal store receives an update, OSCBridge checks each action's trigger_chain, the tree of conditions if they match the store or not. If the trigger_chain is evaluated to be true, then the tasks will be executed.

There is an option, that can be specified for each action, called debounce_millis, if provided then the logic changes a bit. Upon store change, if the trigger_chain resolves to true, then after the specified ammount of milliseconds the trigger_chain is re-evaluated. If it is still true, only then will the tasks be executed.