In this example, we have two connections: an iCal connection and an Atem Video switcher. The iCal connection contains a variable called event_name, and the Atem Video switcher performs an Auto transition. We follow the logic from left to right.
We retrieve the value from the Connection variable of the iCal connection and input it into a Logic node to compare it with a specific value, in this case, “test_on.” When the iCal calendar encounters an Activity with the name “test_on,” the logic evaluates to true. While we could directly pass the value to the connection event, this would trigger on all changes, including when the logic becomes false. To address this, we utilize the Change Switch to filter the output from the logic. The Change Switch now outputs a new timestamp each time the logic becomes true.
By implementing this logic, the Auto transition will only be triggered when the iCal calendar encounters an Activity with the name “test_on,” not when the activity ends and the logic becomes false again. This allows for more flexibility and control over the triggering conditions.
We can further expand this logic by adding multiple Logic nodes, each testing for a different Activity. This enables us to trigger various actions based on specific events in the iCal calendar.
In this workflow, we utilize an internal feedback mechanism to monitor the status of a video switcher. The output of this feedback node is a Boolean value, enabling us to directly pass it to a change switch. Consequently, as long as the PCR1-Mix 1 is connected, the router will route input 12 to output 12. However, in the event that Buttons loses connection to the PCR-Mix 1, the feedback will generate a false output, prompting the router to route input 1 to output 12. While this serves as a basic example, it can be significantly expanded to automate the system in the event of component failure.
In this straightforward REST server example, we expose five endpoints that can be integrated into a webpage or accessed by external devices capable of making GET and POST requests. The four POST requests will trigger the event inputs on the event switch, thereby modifying the numeric values on the output and storing them in the houselight_scene variable using the workflow variable write node. Conversely, the GET request will enable the external webpage or device to retrieve the current value from the houselight_scene variable. This ensures that the external webpage or device remains synchronized, even if other buttons change the variable.
