Date: Fri, 29 Mar 2024 10:00:07 +0000 (UTC) Message-ID: <884446974.39.1711706407019@b223613f76fc> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_38_146272371.1711706407018" ------=_Part_38_146272371.1711706407018 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Presentation Settings pane allows you to edit = settings that relate to the entire presentation.
As of the BrightAuthor:connected 1.6.46 release, Presentati= on Settings contains a Property Lock feature= . If your presentation has a script or script plugin that contains fun= ctions to configure or change the network settings of the player (for examp= le, HTML or a plugin that modifies device settings), check the Property Lock checkbox to ensure that your settings are= not overwritten by BSN.cloud.
When this box is unchecked and the presentation is published, player pro=
perties are not locked and can be edited and updated through the Properties panel in the Network tab of BrightAuthor:connected.<=
/p>
When you check Property Lock and publish the presentati=
on, users can no longer change the player property settings (Player=
Name, Overview, Device Configuration, Logging, <=
strong>Network SettingsIf Property Lock is=
Checked
The player should reboot automatically when the presentation is publishe=
d. If it has not, reboot the player manually.
When the Property Lock setting changes, there can be a reporting delay o= f up to 10 minutes between the OS, BSN, and the BrightAuthor:connnected UI.= During the reporting delay, the UI may be out of sync with the player. If = you change the properties during this period, the UI will accept the change= s and post them to BSN. BSN will store and deliver those settings to the pl= ayer, but the player will not respond to them (the properties of the player= will be locked). The player will not apply your changes until the settings= handler has been reenabled by the presentation.
Use this section to edit video and audio output settings.
If you are using a Series 5 player and BrightAuthor:connected version 1.= 7.11 and beyond, note that the Connector, Target Resolution, Force Resoluti= on, Enable YCbCr 10-bit Output= , Target Frame Rate, Orientation, and Enable Dolby Vision field= s described below have been moved to the Screens tab.
Connection Type: Select the video connector that connects the player to the display= .
Target Resolution: Choose a resolution that is compatible with your monitor. See = span> here for a list of all available video modes.
Force Resolution : Check this box to have the player output the selected resolution even if the display reports ov=
er HDMI=C2=AE that it does not support it. =
If this box is unchecked, the player will attempt to use the selected =
Target Resolution<=
/span>, but will then fall back to the highe=
st resolution supported by the display if it is unsupported.
Enable YCbCr 10-bit ou= tput : Check this= box to output a 10-bit color video signal to the connected display. See th= e video enco= ding FAQ for mor= e details on supported 4K color spaces and bit depths.
Enable Full Resolution=
Graphics: Check =
this box to enable full-resolution for the selected
Enable Dolby Vision: Check this box to = enable Dolby Vision on the video output. The presentation will be limited t= o a single video zone with this option enabled. This option is supported on= XT244 and XT1144 models only.
Target Frame Rate: Choose a frame = rate that is compatible with your monitor.
Orientation: The monitor orientation fo= r the presentation. This property must be set during presentation crea= tion.
Background Color: Select a background c= olor for the presentation. This color will show through if there's no conte= nt on an area of the screen, or if the content has some level of transparen= cy.
Language: Select a language for your pr= esentation. This option affects the time/date display of Clock zones only. =
Delay Schedule Change = until current media item completes playback: Check this box to have the player wait unt= il a media item completes playback to switch to a new scheduled presentatio= n. For multi-zone presentations, the first media item to complete playback,= no matter the zone, will trigger the scheduled presentation change. If thi= s box is unchecked, a player will switch from one scheduled presentation to= another at the specified time regardless of current playback.
<= /li>Monitor overscan: Select an overscan setting to determine how the content fills the= display screen.
No overscan =E2=80=93 use full screen: Displays content= to the edge of the video signal.
Overscan =E2=80=93 action safe area: Restricts the disp= lay area to a size that is compatible with most displays.
Overscan =E2=80=93 title safe area: Restricts the displ= ay area to a size that is much smaller than the generated video signal.
=Use the Audio tab to configure audio mixing and output options:
Audio Volume: Set the Minimum Volume and Maximum Volume for the audio output= (0 =E2=80=93 100).
HDMI Volume: Set the Minimum Volume and Maximum Volume for the HDMI output (= 0 =E2=80=93 100). If you are using BrightAuthor:connected 1.7.11 or ab= ove and multiple HDMI outputs are available on the device, each will be dis= played as in the image at right.
SPDIF Volume: Set the Minimum Volume = and Maximum Volume for the SPDIF output= (0 =E2=80=93 100).
Audio Configuration: Configure the audio routing for th= e presentation:
Mixed Audio PCM Only: Multiple PCM audio sources (for e= xample, from a video and audio file playing simultaneously) will be mixed i= nto a single source for audio outputs. Differing sampling rates (e.g. 44.1 = kHz vs. 48 kHz) will be merged into a single rate of 48 kHz. This setting a= lso allows for dynamic adding and removing of audio sources while audio is = already playing.
Auto level volume: Check this box to level all PCM audi= o streams on a particular audio output to a similar volume level.
Mixed Audio PCM / Compressed: The behavior is the same = as the Mixed Audio PCM Only setting, but compres= sed audio is supported as well. This is either Mixed PCM = Audio or a Compressed audio source= (compressed audio cannot be mixed), that can be routed to an audio output.=
Fixed Audio: Audio sources are mixed only if their samp= ling rates match. If you attempt to add or remove audio sources while audio= is playing, playback will fail.
AUx5 players do not support some audio options and those will not be dis= played in the Presentation Settings:
Auto level volume in Mixed Audio PCM Only mode
Mixed Audio PCM/ Compressed mode
Use the Support Content section to add s= upplementary files to a presentation.
If you are in BSN.cloud Content mode, you will need to upload support content to your BSN Content Clo=
ud network in the Content=
span> tab first=
before adding it to your presentation. If you are in <=
span class=3D"legacy-color-text-default">Local Content mode, you will add files from yo=
ur local machine.
Add custom files that will be = published along with the presentation. This feature is useful if you freque= ntly publish files that are not used in the presentation itself (for exampl= e, a media file being played by a custom script) and you want to automate t= he process of publishing both presentation files and custom files.&n= bsp;
Name: Specify a name for the auxiliary file.
Select File: Locate and select the auxiliary file.
<= /li>Script plugins allow you to add custom scripts to a standard BrightAutho= r:connected presentation without actually modifying the autorun file. For example, you can use script= plugins to change variable values, extract information from a .tx= t, .csv, .xml, or .json file to display onscreen, change the contents of a playlist, or change how= the presentation responds to external input. Script plugins also allow you= to access features that are enabled in player firmware, but haven't yet be= en built in BrightAuthor:connected.
This custom functionality can be triggered by events (button press, touc= h, video end, etc.) or by commands, such as a Zone Message or UDP Command. = A script plugin can also be triggered by a Plugin Message command, which al= lows you to target the function of a specific plugin.
See the Plugins and Parsers tech note for more information on bu= ilding script plugins.
Name<= span class=3D"legacy-color-text-default">: Specify a name for the script pl= ugin. This name must match the initialization function in the plugin.
Source: Locate and select the script p= lugin file.
You can find examples of plugins on the BrightSign GitHub page:
Widget Hide or Show: Allows you to hide or show a Ticke= r or Clock zone by sending Plugin Message commands.
RTSP Media Server: Converts a 4K or XD player to a medi= a server that waits for clients to connect, then starts streaming video to = them via RTSP.
Touch Audio Feedback: Plays an audio file over HDMI whe= never a touch event is triggered in the presentation.
To retrieve a plugin from the GitHub page, right-click the = Raw link on the plugin page heading and click Sa= ve Link As....
This feature allows you to add= a custom BrightScript snippet for parsing feeds in your presentation. = ;It can be added to states that use feeds to download and display content s= uch as Media List, and, like plugins, can display information from a .tx= t, .csv, .xml, or .json = ;file or change playlist contents. Parsers are not triggered by a comm= and or associated with an event. Any function that uses an event as a trigg= er must be written as a plugin, not a parser.
A parser does not need to work exclusively with the data in the associat= ed feed. Once the parser starts running, you can use it to delete a fi= le on the storage, send a UDP command, or download another feed or file. Se= e the Plugins and P= arsers tech note for more information on building parsers.
Parser Plugin Name: Specify a name for the parser plugi= n file. The name should be the same as the subroutine name in Bri= ghtScript.
Parser Plugin Source: Locate and select the parser plug= in file.
Feed Parser: Enter the name of the feed-parser function= in the script.
User Agent Parser (optional): Enter the name of the par= ser function for user-agent strings.
User Variable Parser (optional): Enter the name of the = user-variable parser function in the script.
You can find examples of parsers on the BrightSign GitHub page:
RSS Converter: Converts a standard RSS feed into t= he same format as a BSN Live Text feed, allowing you to display RSS feed it= ems by index number in a Live Text state.
Live Text Title and Description: = Allows you to display both the title and description of an RSS item in a Li= ve Text State.
To retrieve a plugin from the GitHub page, right-click the = Raw link on the plugin page heading and click Sa= ve Link As....
This plugin changes the video resolution, frame rate, color space and co= lor depth. BrightSign offers the following Video Mode plugins:
SetMultiScreensVideoMode.brs configures video for serie= s 5 players. See https://github.com/brightsign/video-mode-plugin/blob/master/SetMulti= ScreensVideoMode.brs for more details.
SetSingleScreenVideoMode.brs configures video for serie= s 4 and below. See https://github.com/brightsign/video-mode-plugin/blob/master/SetSin= gleScreenVideoMode.brs for more details.
Once you have updated the .brs file with your desired screens settings, = you can add it to BrightAuthor:connected. See Sup= ported Video Modes and VideoM= ode Multiscreen Configuration for more information about which values a= re valid for your player.
https://github.com/brightsign/BrightAuthor-Plugins/tree/mas=
ter/Set-Video-Mode manages a plugin that sets the videomode (the
Add supplementary presentations that will be published along with the pr= imary presentation. You can use the Switch to Presentation command to switch to another presentation whil= e a presentation is running.
Presentation Name: Specify the presentation name, whic= h will be used in the Switch to Presentation command.
Presentation Source: Locate and select the .b= pfx presentation file.
You can also switch presentations based on a timeout event. This feature= is available in both local and BSN mode.
To do this:
Make sure that your presentation is connected to a Timeout Event= and save it.
Open the Switch Presentation dropdown by sele= cting the plus sign. Select the name with the red dot (see Image 1).
Enter a new Presentation Name and Presentation = Source.
Under Event Properties > Advanced, select Ad= d Command (see Image 2).
Select Other in the Command dropd= own.
Under Command Parameters, either:
Select Switch to Presentation and specify the new = Presentation Name.
Or select Specify via user variable and create a new va= riable (under Variables) with the new Presentation= Name as the Default Value. Enter that variable u= nder Specify via user variable.
Save your changes.
You cannot successfully switch presentations between presentations with = different connector types, screen r= esolutions and/or frame rates. If you try to do this, the player wil= l reboot and return you to the originally scheduled presentation. If you ha= ve plugins, etc. that reboot the player, Switch Presentation will also fail.
Switch Presentation does not let you switch to a p= resentation that has never been published. This bug will be resolved in a f= uture release.
Add Data Feeds to the presenta= tion.
Name: Specify a name for the Data Feed.
URL: Source the Data Feed from an RSS URL.
Dynamic Playlist: Source the Data Feed from a Dynamic Playl= ist on your BSN Conten= t Cloud network.
Live Media
Live Data Feed: Source the Data Feed from a Live Data F= eed on your BSN Conten= t Cloud network.
Parser Plugin: Select a feed parser to parse the feed data= before it is passed to the Data Feed.
Optimize Feed Updates (use HEAD calls): Check this= box to have the player make an HTTP HEAD request before retrieving the con= tents of a Data Feed. See the Data Feed section
Automatically generate User Variables from Data Feed: Use the Data Feed to populate a set of User Variables for HTML pa=
ges. The User Variables can then be retrieved using JavaScript. Use the&nbs=
p; <title>
tag of the Data Feed to specify the Name=
of a variable and the <description>
ta=
g to specify its default value.
User Variable Access: Select Shared to make the User Variable accessible to other presentation= s scheduled on the player. If two presentations use a variable with the sam= e name, the value of the variable with the Shared attribute will be used for the variable with the Private attribute.
Select the
The Device Web Page allows you= to view and edit User Variables over your local network. In order to displ= ay a standard or custom device web page, the Local Web Server must be enabled on the player.
Disable: Choose this option if you would like to enable the Local Web Server but do= not want the device webpage to be accessible.
Standard: Choose this option to enable the default device web page, which lists all= User Variables and their default/current values on a sparsely formatted pa= ge.
Custom: = Choose this option to use a device web page with custom appearance, formatt= ing, and functionality. See the Creating a Custom Device Web Page tech note for more information.
Use the Variables section to create, edit, an= d delete User Variables. Use= r Variables are customizable values that can be used in User = Variable states, as we= ll as commands and conditional targets. The values of User Variables can also be changed duri= ng a presentation using the Set Variable or Reset Variable commands.=
Click
Variable Name: Enter a unique name for the User Variabl= e.
Default Value: Specify an initial value for the User Va= riable. Whenever a User Variable is reset (via the Reset Variable co= mmand), it will return to this default value.
Setting a new Default Value and republishing = the presentation will not set the value of that variable to the new default= value. Instead, the variable will retain whatever value it had before the = publish operation. To set variables to their new default values, you will n= eed to check the Reset variables to their default value on pre= sentation start box before publishing the presentation. To se= t a single variable to its new default value, use the Reset Va= riable command.
Access: Select Shared = em>to make the User Variable accessible to other presentations scheduled on= the player. If two presentations use a variable with the same name, the va= lue of the variable with the Shared attribute wi= ll be used for the variable with the Private att= ribute.
Type: Select a User Variable type:
Local: Local variables can be changed with the Set Vari= able/Reset Variable commands or via the Device Web Page. They= can also be set with properly formatted serial, UDP, and Plugin Message ev= ents.
Networked: Networked variables are set and modified usi= ng a feed (RSS, Dynamic Playlist, Live Media Feed, or Live Data Feed).= Note that every RSS entry has a <title> value and a <de= scription> value: use the <title> value to designate the name= of the User Variable being modified; use the <description> valu= e to change the value of the User Variable.
Parser Plugin: Select a feed parser to parse the feed= data before it is used to update the variable.
Optimize Feed Updates (use HEAD calls): Check this= box to have the player make an HTTP HEAD request before retrieving the con= tents of a feed. See the Data Feeds section above for more details.
Automatically generate User Variables from Data Feed: Use the feed to populate a set of User Variables for HTML pages.&n= bsp;See the D= ata Feeds section above for more details.
SystemVariable: System variables are not determined by = the user, but by independent system parameters, such as firmware/autorun ve= rsion number, IP address, RF channel count, and various types of EDID (exte= nded display identification data) information received from the display ove= r HDMI. Note that displays will often lack a complete set of EDID para= meters. Make sure to test the EDID values of a certain display model before= using them in a presentation.
System Variable= : = This option will = appear if you selected System Variable under Type. Use = it to select a system variable from the drop down list. See the image below= .
Connector: This option will be visible if= you selected an EDID System Variable under Type:
If you are using a BS device w= ith one HDMI output, this option will be greyed out and show only HDMI-1.= span>
If you are using a BS device w= ith multiple HDMI outputs, you can use this feature to link the variable to= the available HDMI outputs for that device.
You can also configure settings that apply to all variables in the prese= ntation:
Alphabetize variables in app display: Check this box to= list variables on the Device Web Page alphabetically. Select the arrow nex= t to Variable Name to sort the variables from A to Z or Z = to A. New variables will be added to the end of the alphabetized list and t= he arrow next to Variable Name will revert to a dash (whic= h indicates that the list is again unsorted).
Automatically create media counter variables: Check thi= s box to create Media Counters for all media files in the presentation. Med= ia Counters record how many times a file has played in a presentation. They= can be displayed in a Live Text or User Variable&n= bsp;state.
Reset Variables to their default value on presentation start: Check this box to reset all User Variables to their default values w= henever the presentation begins. If this box is unchecked, User Variable va= lues will be preserved on the SD card after the device reboots, the present= ation is switched, etc.
Update frequency for networked variables: Specify how o= ften networked User Variables should be refreshed by feeds.
The Interactive section allows you to configure in= teractive I/O for the presentation.
Use this tab to configure BP200/BP900 button panels and touch screens.= p>
Use the Bu= tton Panel dropdown= list to select the type of button panel (BP200 or BP900) you wish to confi= gure. The A, B, and C letters specify which device is enumerated first; the= B and C letters are only applicable if you are connecting more than one BP= device to the player.
Choose one of the following:
Automatically configure which buttons are enabled: Only= buttons that are configured with BP200/BP900 events in the presentation wi= ll be enabled. All other buttons will not light up or react to button press= es.
Specify which buttons are enabled: Only the specified b= uttons will be enabled regardless of whether there are BP200/BP900 events i= n the presentation configured to use them. If this option is selected, a BP= 200/BP900 event set to the Any Button option wil= l only react to button numbers that have been enabled.
Cursor: Select a mouse display option for Touch events:
Always hide cursor: The mouse cursor will never appear = with Touch events.
Always display cursor: The mouse cursor will always app= ear with Touch events.
Auto display cursor: The mouse cursor will be present o= nly if there is more than one Touch event region on the screen.
Flip coordinates: Check this box to reverse the coordin= ates of the touchscreen input.
Use this tab to configure serial port, GPIO communication, and IR Remote configuration.
Port: Select a serial port to configure. Most standard = serial devices enumerate on port 0 (on the HO523, they will enumerate on po= rt 1).
A USB-serial device (such as a GPS receiver) will enumerate on port 2.&n=
bsp;Additional USB-serial devices will enumerate on ports 3, 4, 5, etc. The=
enumeration order will remain consistent between reboots as long as the US=
B-serial devices are connected to the same player/hub ports. The enumeratio=
n order can be retrieved using the "usblist" command at the brightsig=
n>
shell prompt; otherwise, it will need t=
o be determined by testing the setup.
GPS Receiver (Port 2 only): Check this box if the = port is being used to connect a USB-serial GPS device to the player.
Protocol: Determine whether the serial data is formatte= d as Binary or ASCII.
Baud rate: Set the baud rate for serial communications = on the port.
Data bits: Set the number of data bits.
Parity: Set the parity.
Stop bits: Select the number of stop bits.
Send EOL: Select the end-of-line character when sending= data to a serial device.
Receive EOL. Select the end-of-line character when rece= iving data from a serial device.
Invert Signals: Check this box to invert the TX/RX= signal levels on the serial port. This allows the player to communica= te with devices that use -12V to 12V signaling. Inversion is only supported= on the following ports: The DE9 and USB ports on the 4Kx42, as well as the= 3.5mm serial port on the XT= x43/XDx33 (units that are rev H or earlier) and HDx23. Except for the 4Kx42, all of these= ports perform 5V signaling.
Many BrightSign models feature a DA15 or Phoenix-style GPIO port for dev= ice communication and interactive input/output. Select Input or Output for each GPIO button to indicate whether it s= hould be used to receive or send information.
The "button" numbers described here are not the same as GPIO "pin" numbe= rs: Some pins act as power supply or ground, so they are not included in th= e button numbering scheme. See the Hardware Interfaces section of the hardware manual as= sociated with your player model to view a mapping of buttons to pins.
The user can select from the events and/or commands available based on t= heir IR In Source and IR Out Destination selections.
Remote Control: This can be either one of BrightSi= gn remotes (RC-1001 or RC-1002), or a user specified remote.
IR In Source: This configuration is one of a dedic= ated IR, or Iguana (USB), or None.
IR Out Destination: This configuration is either d= edicated IR, or Iguana (USB), or None.
Use this tab to configure UDP communications and PTP synchronization.
UDP Destination Address: Specify where UDP commands gen= erated by the presentation should be sent:
Specific IP Address: Enter a single destination IP addr= ess in dotted quad form.
All devices on the local subnet: Broadcast UDP messages= to all devices on the local subnet.
All devices connected via Ethernet: Broadcast UDP messa= ges to Ethernet-connected devices on the local subnet.
All devices connected via Wireless: Broadcast UDP messa= ges to Wireless-networked devices on the local subnet.
UDP Destination Port : Specify the destination por= t for UDP messages generated by the presentation.
UDP Receiver Port: Specify the port used by the player = to receive UDP messages (for triggering UDP events on the player).
This section lists all UDP events in the presentation. For each event, y= ou can specify the following options:
Label: Specify a label for the UDP command button = in the BrightSign App. By default, the command label will be the same as th= e UDP message string.
Show in BrightSign App: Check this box to have the comm= and button corresponding to the UDP Input event appear in the BrightSign Ap= p.
You should always use enhanced synchronization between players. This fea= ture passes synchronization events from leader to follower players (in = ;video walls, for example).
Enable Enhanced Synchronization: Select this checkbox t= o put players in a synchronization domain (this domain selects a PTP a= ddress where clock and synchronization events will be published from the le= ader player and read by the follower player).
Leader (formerly Master): Makes the currently sele= cted player a leader player.
Follower (formerly Slave): Makes the currently sel= ected player a follower player. There can be multiple follower players.
=Domain: Enter a domain number between 0 and 127 th= at is unique for each set of leader/follower presentations on the local net= work. This will ensure that multiple groups of synchronized presentations c= an operate on the same local network without synchronization messages inter= fering with each other.