...
| Anchor | ||||
|---|---|---|---|---|
|
...
The Synchronize event synchronizes playback with other BrightSign players on the same local network using UDP. This event is useful for synchronizing playback according to user input.
...
For Synchronize events to work, you must ensure UDP communication is configured correctly in Presentation Settings > Interactive > Networking.
...
The Zone Message event allows you synchronize content between zones. This event is compatible with all state types, while the Link Zones event only works with video and image states; however, the Link Zones event provides better synchronization times because it pre-loads the next image/video file before displaying it.
Zone Message events can be used with Synchronize events to synchronize zones in a multi-screen presentation, while Link Zones events cannot be used with Synchronization events.
In the Specify zone message field, enter the message that is sent by the corresponding Send Zone Message command.
...
The UDP Input event triggers when the BrightSign player receives a UDP (User Datagram Protocol) message from another device on the local network. Source devices can include tablets/smartphones running the BrightSign App, other BrightSign players, and PCs/Macs.
Specify UDP input: Enter the UDP message string that will trigger the event. You can also use the <any> wildcard to match some or all of the UDP message string (i.e. entering "<any>" in this field will match all UDP messages, while entering "mycommand_<any>" will match any UDP message that begins with "mycommand_").
Label: Specify a label for the UDP command button in the BrightSign App. By default, the command label will be the same as the UDP message string.
Show in BrightSign App: Display the command button corresponding to the UDP Input in the BrightSign App.
Assign input to variable: Assign the content of the UDP message to a User Variable.
Input specifies variable: The UDP message string will dynamically specify which User Variable to modify. The UDP message string must be sent in the form of "<variable name> : <variable value>".
Specify fixed variable: The UDP string will modify a fixed User Variable. Use the dropdown list to choose which User Variable the UDP input will modify. The UDP string must be sent in the form of "<variable value>".
| Tip |
|---|
You can use the Input specifies variable option to modify more than one User Variable with a single event. Use the following UDP string format: "<variable name> : <variable value> !! <variable name> : <variable value>" |
Assign wildcard to variable: Specify the value of a User Variable using the <any> wildcard. Select the User Variable to modify using the dropdown menu to the right. The Specify UDP Input field must contain the <any> wildcard, either by itself or with additional text (e.g. "message_<any>").
GPIO Event
...
The GPIO event triggers when a specific GPIO button is pressed or input is received. The playlist toolbar includes the different GPIO button numbers that you can use to define interactions.
Specify button number: Specify the number of the GPIO button.
Trigger Event on Button: Specify whether the event should trigger when the button is depressed (Down) or when it is released (Up). If you've selected Down, choose one of the following behaviors:
Press (First Touch): The event triggers once at the moment the button is depressed.
Press Continuous: The event triggers the moment the button is depressed, then continues triggering at the specified Repeat interval in milliseconds as long as the button is depressed.
| Note |
|---|
The "button" numbers described above are not the same as GPIO "pin" numbers: Some pins act as power supply or ground, so they are not included in the button numbering scheme. See the Hardware Interfaces section of the hardware manual associated with your player model to view a mapping of buttons to pins. |
Plugin Message Event
...
The Plugin Message event triggers when a message is received from a custom script plugin that is attached to the presentation. See the Parsers and Plugins tech note for more information on creating custom scripts that send plugin messages.
Plugin Name: Use the dropdown menu to determine which plugin the event can receive messages from.
Specify Plugin Message input: Enter the message string that will trigger the event. You can also use the <*> wildcard to match some or all of the plugin message string (i.e. entering "<*>" in this field will match all plugin messages, while entering "mycommand_<*>" will match any plugin message that begins with "mycommand_").
Assign input to variable: Assign the content of the Plugin Message to a User Variable.
Input specifies variable: The Plugin Message string will dynamically specify which User Variable to modify. The Plugin Message string must be sent in the form of "<variable name> : <variable value>.
Specify fixed variable: The Plugin Message string will modify a fixed User Variable. Use the dropdown list to choose the User Variable to modify. The Plugin Message string must be sent in the form of <variable value>".
| Tip |
|---|
You can use the Input specifies variable option to modify more than one User Variable with a single event. Use the following Plugin Message string format: "<variable name> : <variable value> !! <variable name> : <variable value>". |
Assign wildcard to variable: Specify the value of a User Variable using the <any> wildcard. Select the User Variable to modify using the dropdown menu to the right. The Specify Plugin Message input field must contain the <any> wildcard, either by itself or with additional text (e.g. "message_<any>").
USB Event
...
The USB event triggers when a BrightSign player receives the specified input from a connected USB device.
In the Specify USB input field, enter the USB input string that will trigger the event.
Keyboard Event
...
The Keyboard event triggers when a BrightSign player receives the specified input from a connected keyboard.
In the Specify keyboard input field, enter the keyboard input that will trigger the event.
Remote Input Event
...
The Remote Input event triggers when the BrightSign player receives the specified input from an IR remote control.
In the Specify remote input field, enter the NEC remote control code that will trigger the event.
Video Time Code / Audio Time Code Event
...
The Video Time Code and Audio Time Code events perform commands at specific times during video or audio file playback. If you want to trigger a transition at a certain point in a video or audio file, use the Timeout event instead.
Click the 
Add Time Code button to add a new time-code command. Enter the Timeout interval for the command (in milliseconds), and then select the Command and Parameters from the corresponding lists.
Time/Clock Event
...
The Time/Clock event triggers at a specific time and date or at regular intervals on a recurring schedule.
Single date/time event: Specify a one-time-only event.
Date: Specify the time and date of the event.
Specify with user variable: Use the value of a User Variable to specify the date and time. Choose a variable from the dropdown list. The value of the variable must be in this format: “yyyy-mm-ddThh:mm:ss”. For example, if you would like the event to occur on December 20, 2021 at 3:45PM, then you would use the value “2021-12-20T15:45:00”.
Daily timeout event: Specify a recurring event.
Once per day: Select this option to have the event occur once per day at the specified Time.
Periodic throughout the day: Select this option to have the event occur at intervals throughout the day.
Interval between events: Determine the frequency of the recurring event (in minutes).
Active between: Specify the period during which recurring events can trigger.
Set the days the timeout is active: Select which days the time/clock event is active.
...
Use the Link Zones event, combined with the Link Zones command, when you require close, millisecond-level synchronization of content between zones on the same player.
The Link Zones event supports video and image states only; use the Zone Message event to synchronize other states. The Link Zones event provides better synchronization times than the Zone Message event because it pre-loads the next image/video file before displaying it.
Link Zones events cannot be used in the same presentation as Synchronize events; to synchronize zones in a multi-screen presentation, use the Zone Message event.
In the Specify link keyword field, enter the message that is sent by the corresponding Link Zones command.
Serial Input Event
...
The Serial Input event triggers when the BrightSign player receives input from a device connected to a serial port.
Specify port: Enter the port number of the input device. Most standard RS-232 serial devices enumerate on port 0. If you are connecting a USB-serial device, it will enumerate on port 2. To configure the serial port, navigate to Presentation Settings > Interactive > Connectors.
Specify serial input: Enter the serial input string that will trigger the event. You can also use the <*> wildcard to match some or all of the serial input (i.e. entering "<*>" in this field will match any input, while entering "mycommand_<*>" will match any input message that begins with "mycommand_").
Assign input to variable?: Check this box to assign the content of the serial input to a User Variable.
Input specifies variable: The serial input string will dynamically specify which User Variable to modify. The serial input string must be sent in the form of "<variable name> : <variable value>".
Specify fixed variable: The serial input string will modify a fixed User Variable. Use the dropdown list to choose which User Variable the serial input will modify. The serial input string must be sent in the form of "<variable value>".
| Tip |
|---|
You can use the Input specifies variable option to modify more than one User Variable with a single event. Use the following serial input string: "<variable name> : <variable value> !! <variable name> : <variable value>". |
Assign wildcard to variable?: Check this box to specify the value of a User Variable using the <*> wildcard. Select the User Variable to modify using the dropdown menu to the right. The Specify serial input field must contain the <*> wildcard, either by itself or with additional text (e.g. "message_<*>").
...
.