Broadsign Cinema Post-Show is based on our loop policies functionality.
You will need to be familiar with loop policy construction before setting up a Post-Show.
Pre-Show playlists run until a movies’ advertised showtime. If you include a Post-Show, your loop policy will include content after showtime, as well.
Here is a sample Post-Show timeline:
The maximum number of stages is 99. You can provide whatever value you want to the values below. For more information, see Post-Show Loop Policy Variables (below).
The stage_align_to_showtime
variable is quite important:
- If you omit this variable, the Player assumes that the entire multi-stage assembled loop will end exactly at the showtime.
- If you configure this variable to a stage that is not configured with a
condition
andmax_duration
variable, the Player ignores it. - If you configure this variable with a valid stage number, but the Vista
showtimes.xml
file does not exist or is unsynchronized, the Player ignores it.
To add variables to the Loop Policy:
- In your Loop Policy Properties dialogue box, go to Settings > Variables.
- Enter the following variables:
preshow_type
=”multistage”stage_1_max_duration
= “[value in milliseconds]”stage_1_condition
=”preshow” (suggested value)stage_2_max_duration
= “[value in milliseconds]”stage_2_condition
=”security” (suggested value)stage_3_max_duration
= “[value in milliseconds]”stage_3_condition
=”postshow” (suggested value)stage_align_to_showtime
=”2″ (suggested value)
- Click OK or Apply.
To Schedule content to the Display Unit:
See Pre-Show’s Step 4: Schedule a Conditional Campaign to the Display Unit.
Broadsign created two new Loop Snapshot report column options for Post-Show:
- Display Pre-Show Stage Conditions
- Display Pre-Show Stage Number
For general information about this report, see Loop Snapshot.
Variable | Description | Value |
---|---|---|
preshow_type | Default value. | multistage |
stage_1_max_duration | Controls the maximum duration of the pre-show section in milliseconds. If the loop exceeds this length after it is assembled and ordered, the player removes content from the beginning of the loop until the duration is equal to, or less than, the maximum duration. | [value in milliseconds] |
stage_1_condition | Controls the condition name for content in the first part of the loop.We suggest a value of “preshow”, though it can be what you want. You will need to set all campaigns and content that will appear in the pre-show section with this name. Note: Matching of the variable to the condition name is case-sensitive. | preshow (suggested value) |
stage_2_max_duration | Controls the maximum duration of the security section in milliseconds. If the loop exceeds this length after it is assembled and ordered, the player removes content from the beginning of the loop until the duration is equal to, or less than, the maximum duration. | [value in milliseconds] |
stage_2_condition | Controls the condition name for content in this section of the loop. We suggest a value of “security”, though it can be what you want. You will need to set all campaigns and content that will appear in the Security section with this name. Note: Matching of the variable to the condition name is case-sensitive. | security (suggested value) |
stage_3_max_duration | Controls the maximum duration of the pre-show section in milliseconds. If the loop exceeds this length after it is assembled and ordered, the player removes content from the beginning of the loop until the duration is equal to, or less than, the maximum duration. | [value in milliseconds] |
stage_3_condition | Controls the condition name for content in this section of the loop. We suggest a value of “postshow”, though it can be what you want. You will need to set all campaigns and content that will appear in the Security section with this name. Note: Matching of the variable to the condition name is case-sensitive. | postshow (suggested value) |
stage_align_to_showtime | Identifies which stage the player will align to start on the showtime, as specified in the vista showtimes.xml file. As a result, it determines the overall real start and end times of the playlist. If you omit this variable, the player assumes that the entire multi-stage assembled loop will end exactly at the showtime. If you configure this variable to a stage that is not configured with a condition and max_duration variable, the player ignores it. If you configure this variable with a valid stage number, but the Vista showtimes.xml file does not exist or has not been synchronized, the player ignores it.
|
2 (example) |