Smart Programs

Programs can consider shows just on the auditorium in question (Auditorium mode) or shows on all auditoriums in the site (Site mode).

This is an example of a Program that modifies the volume of a given auditorium. The program should be triggered by the macro which should be set on the show playlist at the time when volume adjustment is needed.

There are two steps:

Each step contains a condition based on the seats sold. The actions following the conditions will only be invoked if the condition is true, so if for example, 60% of the seats for a show were sold then the volume would be set to 10, the step to set the volume to 5 would not be invoked.

This example shows how a defensive program could be set. It is not advised to use something similar as a replacement for day start automation, but it can help to recover when the device is on eco power mode or offline just before a show start.

The trigger is set without any gap to detect, so it would be triggered before any show. The offset value should be set a reasonable amount of time before the show, so the device would have enough time to start up and prepare for the show.

This example shows how a program can be configured, so it would check early in the day if there are any expected transfers on the auditorium and if there are, wake up the player (or another device).

It is a better practice to check if the player is actually offline before trying to wake it up.

If the site should have Site mode offset automation, this program can still be left on Auditorium mode because there should be another program which will wake up the device considering the Site mode offset.

This will result in the “Day Start - Start Early for Transfers” program being scheduled after the “Day Start - Wake Up the Player” program if that specific auditorium has shows starting later compared to other auditoriums. However, this is fine because the player will be online way before the desired offset from the first show and there should be enough time to ingest.

This example shows how a separate program can be configured to wake up the player (or another device) at the start of the day. The same program can be extended to include other automation, like turning on lights in the auditorium, but it is not suggested as it may take some time for the player to come back online. So in our examples, we provide it as a separate program which should run 5 minutes later.

In the same way player wake-up is executed, other automation can turn on different PDUs to manage other hardware, like a sound rack.

Different PDU outlets can be turned on with small delays in between to turn on different devices in sequence:

This example continues on the previous one. It simply turns the lights on or executes any other required macros a few minutes after the player comes online after the “Day Start - Wake Up the Player” program.

This example shows how a program can turn off the lights in the auditorium after all shows.

Note that for the end of the day automation, the offset mode should be changed to AFTER_ACTIVITY.

This example shows how a program can check if any transfers are expected after all shows and based on that decide if a player (or another device) should be sent to power eco mode or offline. If this approach is used, the next program is also mandatory, so it would turn off the device after transfers are completed.

Continuing from the previous program example, this example shows how a program can send the device offline or to power eco mode after transfers to the device are completed. Best behaviour can be achieved with Bulk transfers selected, so the program would not be triggered when the first of many transfers completes.

​