The Products Section

The Products section applies exclusively to player configuration profiles. The settings in this section control the behaviours of the various media products used to display content on-screen.

The Application tab of Configuration Profile Properties

Here you can control whether a player is allowed to run application ad copies with administrator rights. See Ad Copies – Application.

The Ticker tab of Configuration Profile Properties

Here the Ticker product can be configured to respect or ignore network control time spans with respect to fetching ticker feeds.

The Image tab of Configuration Profile Properties

Here you can enable transitions for images. The supported types of transitions are:

    • Fade In/Fade Out: Fades the image in from black and fades it back to black.
    • Crossfade: Fades one image out while the other one fades in. This only works if you have two images back-to-back otherwise the transition will not be applied.
    • Page Turn: The corner of the image curls up in 3D and the current image is pulled off the screen revealing the image underneath. Once you select this strategy, a text box will appear which will permit you to specify an optional absolute path to a logo file that exists on the player system. This logo will appear on the underside of the page turn transition. This transition only works if you have two images back-to-back otherwise the transition will not be applied.

Here you can configure HTML content, browser support and HTML transitions.

    • HTML: These parameters control the usage of HTML content on the player.
        • Allow local URLs: Allow links to local URLs (e.g. C:somefile.html).
        • Allow “mailto” URLs: Allow “mailto:” hyperlinks to email addresses.
        • Append Resource ID: See “Append Address”.
        • Append Location Code: See “Append Address”.
        • Append Address: Optionally appending dynamic variables (Player Resource Id, Display Unit Location Code or Display Unit Address) to URLs fetched by the player’s browser. Appending these variables allows intelligent server-side logic to determine which player is requesting a resource and customize its response. Appending the player’s resource ID with the default variable name is required for use with Broadsign Creator. For example, if the URL requested is http://sample.com and the HTML product is configured to append the Resource ID and the variable name is set to “player_id”, the actual request the server receives will be http://sample.com?player_id=12345
        • Prebuffer content: This setting controls whether or not HTML content should be pre-buffered in advance of when it should be displayed. This is highly recommended, as some web pages take several seconds to load. However, in some cases, a web page might have Flash animations or sounds that should not start until the content is actually displayed. In this case, you can disable pre-buffer content. Alternatively, if you control the source of the webpage, you can start your animations in a javascript function called “BroadsignPlay()”. If this javascript function exists in the page, it will be invoked by the Broadsign Player just before the HTML page is displayed. This will give the best of both worlds: pre-buffered html content and animations that start only when shown. For more information, see BroadsignPlay()
    • Browser Support: Here you can specify which browser plug-in to use:
        • Windows: The default is Internet Explorer, or Edge in Windows 10 (Auto). You can also select Chromium.
        • Note: As of Broadsign Core v11.1, we support Chromium version 51, branch 2704.
          Note: If you are updating to Broadsign Core v11.1.0 from v10.3.0-v11.0.0, and use Chromium, you will need to create a new configuration profile for v11.1.0.
        • Ubuntu: The default is Webkit (Auto). You can also select Chromium.
    • Transitions: These parameters control the use of smooth transitions for HTML content displayed on the player:
        • Enable transitions: Select this option to enable choosing transitions.
        • Transition type: Choose from the following options:
            • Fade In/Fade Out: Fades the video in from black, and fades it back to black.
            • Crossfade: Fades one video out while the other one fades in.
            • Page Turn: The corner of the HTML display curls up in 3D, and the current image is pulled off the screen revealing the image underneath. Once you select this strategy, a text box will appear which will permit you to specify an optional absolute path to an HTML file that exists on the player system. This logo will appear on the underside of the page turn transition. This transition only works if you have 2 images back-to-back otherwise the transition will not be applied.
        • Transition Duration: Control the duration of the transition (in seconds).
 

The Digital TV tab of Configuration Profile Properties

Here you can set various options about how the TV capture product behaves.

    • Enable YUV Overlay: Uses the hardware overlay to renders the video. Some TV tuners need to disable this because of driver bugs.
    • Enable Deinterlace Filter: The de-interlacing filter cleans up the image to eliminate combing effects, however, it consumes a lot of CPU to do so. Stop device instead of pausing it is another setting that works around bugs in some TV Capture products.
    • Pause device instead of stopping it (recommended for most devices)
    • Ensure that video is rendered (recommended)
    • Reinitialize rendering when the device is stopped (recommended)
    • Some TV tuners are not compatible with MsVidCtl and require their own custom client software to view live TV. These devices are *not* supported by Broadsign. In general, a device that advertises itself as “Windows Media Center Compatible” will be compatible with Broadsign because they both use MsVidCtl.
    • Due to their nature as consumer devices, some TV Tuner devices are notoriously buggy. They may work once or twice (i.e for the home user) but overheat, crash, deadlock or leak memory when used in a demanding 24/7 environment such as digital signage where there is no user present to unplug and plug in the device.
    • Vendors are continuously updating their drivers, so if you are encountering issues, make sure you are using the latest driver.
    • Before deploying a TV tuner solution, the best advice is to purchase a few different devices and test them thoroughly for your desired use case. Make sure that you can return the devices that do not meet your endurance criteria.
 

The Video tab of Configuration Profile Properties

The Video tab in the Settings group of the Configuration Profile Properties dialog allows you to configure how a player will display video content.

Video Output

We recommend the following system configuration:

    • Dual or Quad Core CPU 3Ghz or above
    • 2 GB RAM
    • Nvidia 9400 and above Note: This feature is not supported on Matrox video cards. Also, with a hardware accelerated OpenGL driver implementation, the requirements are OpenGL 2.0 and above .

You can configure the following settings in the Video Output tab:

    • Use default configuration:  The recommended setting for general usage. The Broadsign Player will automatically select the appropriate video display settings based on the capabilities of the system.
    • AV Player: The AV Player is Broadsign’s built-in video engine. It is universal to both Windows and Linux based players. All of the supported containers, video and audio codecs are provided natively by AV. No additional codecs are required to render these media formats. The AV video engine can have different video output strategies depending on the platform.
        • Auto: The recommended choice as the selection will be made at runtime by the player based on the OS capabilities.
        • Hardware Overlay: Uses the video overlay capabilities of the video card to do color conversion and scaling in the GPU. This is the recommended video output for Windows XP systems without desktop composition (i.e. Windows Aero).
        • OpenGL: For hardware-accelerated rendering, and is supported on both Linux and Windows systems. It offers perfect gapless playback with no transition flickers and allows for Fade in/Fade out, Crossfade and Page Turn video transitions.
        • Direct 3D: Uses the 3D capabilities of the GPU to render the video surfaces. This is the recommended video output for systems with desktop composition (i.e. Windows Vista and Windows 7).
    • AV Player with Hardware:  Enables decoding of certain types of video using the system’s GPU. Note that this feature is restricted to certain GPUs and video codecs. For more information, see Hardware Acceleration.
Transitions

You can control the use of smooth transitions between consecutive videos displayed on the player.

The supported types of transitions are:

    • Fade In/Fade Out: Fades the video in from black and fades it back to black.
    • Crossfade: Fades one video out while the other one fades in. This only works if you have 2 images back-to-back otherwise the transition will not be applied.
    • Page Turn: The corner of the video curls up in 3D and the current image is pulled off the screen revealing the image underneath. Once you select this strategy, a text box will appear which will permit you to specify an optional absolute path to a logo file that exists on the player system. This logo will appear on the underside of the page turn transition. This transition only works if you have 2 images back-to-back otherwise the transition will not be applied.
 

The Flash tab of Configuration Profile Properties

The Flash tab in the Settings group of the Configuration Profile Properties dialog allows you to control how Adobe Flash content is rendered on your Broadsign Player systems. The settings are different for Linux and Windows based player operating systems.

    • Windows Flash Runtime: Windows Flash version. In this section you can control how Flash is rendered on Windows-based players:
        • Default, i.e, whatever is currently installed: This is the behaviour for pre-version 8.0 Broadsign Players. Flash content will be rendered using the ActiveX plugin that is already installed on the system (either manually, or by default included with windows).
        • Enforce a specific version of flash: This option allows you to remotely upgrade or downgrade the installed version of the Adobe Flash runtime. If you select a specific version, the Broadsign Players will download the installer from Broadsign’s FTP servers and install it.
    • Linux Flash Runtime: Linux Flash version. In this section you can control how Flash is rendered on Linux based players:
        • Default (Use Broadsign’s embedded Flash 7 Player): Flash content will be rendered using the embedded Flash 7 player that ships with the Broadsign Player.
        • Use Browser Plugin, i.e., whatever is currently installed: This option allows you to use the Web Plugin distributed by Adobe that is already installed locally on the machine. Please note that in order for the Player to find it, libflashplayer.so must be in /home/bsp/.mozilla/plugins or symlinked.
        • Enforce a specific version of Flash: This option allows you to remotely upgrade or downgrade the installed version of the Adobe Flash runtime. If you select a specific version, the Broadsign Players will download the installer from Broadsign’s FTP servers and install it.
    • Flash Crossfade: Enable Flash Crossfade to have your Flash content crossfade into the preceding, and following, product.

To consult the Adobe EULA, see Adobe Flash Player 10.2.