Screenshot Request Action
The Screenshot Request action allows you to push screenshots (or screenshot bursts), in jpeg format, to any URL. As a result, you can see what is happening on your screens in real time. Then, you can troubleshoot issues and ensure dynamic content displays correctly.
Note: You can access screenshots from within Broadsign Control Administrator using Broadsign Control Live. However, we must enable it on your domain. For more information, contact your Sales representative or Broadsign Services.
Call the screenshot_request action using one of the following:
WebSocket Server:
-
JSON – You can pass parameters from within your HTML5 file using JSON.
Note: Ensure that you select Enable Remote Control in the Remote Control tab of the configuration profile. See The Remote Control Tab.
Note: If using JSON via the WebSocket server, any firewall present on Broadsign Control Player should be configured to access port 2326 directly for use.
Port 2324:
- remote_action – An application that ships with Broadsign Control Player, using command line.
- XML – If you want to develop your own applications, you can communicate directly with Broadsign Control Player API using XML.
Note: Ensure that you select Enable Remote Control in the Remote Control tab of the configuration profile. See The Remote Control Tab.
Note: Any firewall present on Broadsign Control Player should be configured to either allow bsp.exe to open ports, or configure port 2324 or port 2326 directly for use.
Note: The Triggers Action is the only exception to this rule. It uses port 2325. See Triggers Action.
You can call this action on Windows and Ubuntu Linux, and find it along the following paths:
- Windows (64-bit):
- Ubuntu Linux:
/opt/broadsign/suite/bsp/bin/
C:\Program Files\BroadSign\bsp\bin
You can request screenshots from a player by invoking the standalone executable remote_action which ships with Broadsign Control Player. It can be found in the player’s installation bin directory.
For example, to request a screenshot, type:
remote_action screenshot_request --dest-url "YourURLHere" --burst-duration 1000 --burst-frequency 100 --scale-factor 100
Where:
- screenshot_request: The action type.
- dest-url: The URL to which you want the player to send the screenshot, in jpeg format.
- burst-duration: The total duration (in milliseconds) for which the player should send multiple screenshots at the specified burst_frequency.
- burst-frequency: If burst_duration_ms is specified, burst_frequency_ms dictates the number of milliseconds between screenshots.
- scale-factor: Optional. Integer, 1-100. 100 = full resolution. Aspect ratio is preserved.
A custom application can request screenshots from Broadsign Control Player by sending an XML message to the monitor_remote port (2324).
<rc version="1" id="1-abcdef" action="screenshot_request" dest_url="https://app.example.com/upload" scale_factor="50" burst_duration_ms="60000" burst_frequency_ms="3000"/>\r\n\r\n
Note: You must terminate the request with \r\n\r\n
.
The player will respond with the following document:
<rc version="1" status="1" action="screenshot_request" id="1" />
Note: Each command sent requires a unique identifier (id). The application can use a simple incrementing value here.
Screenshot Request Action - XML Parameters
Note: Any firewall present on Broadsign Control Player should be configured to either allow bsp.exe to open ports, or configure port 2324 or port 2326 directly for use.
Parameter | Description |
---|---|
version | Mandatory. The version is always 1. |
id | Mandatory. Represents a client-generated unique identifier for the request. This will be passed back unchanged to the dest_url in the HTTP request headers. Maximum any 64 characters. |
action | Mandatory. The kind of action to be taken; always screenshot_request. |
dest_url | Mandatory. The client-supplied URL to which the screenshot will be uploaded, in jpeg format. |
scale_factor | Optional. Integer, 1-100. 100 = full resolution. Aspect ratio is preserved. |
burst_duraton_ms | Optional. Represents the total duration, in milliseconds, for which the player should send multiple screenshots at the specified burst_frequency. |
burst_frequency_ms |
Optional. Default = 3000. If burst_duration_ms is specified, burst_frequency_ms dictates the number of milliseconds between screenshots. Note: The total amount of screenshots sent will be burst_duration_ms / burst_frequency_ms. If burst_frequency_ms is less than the actual time it takes to capture a screenshot and send it, the screenshots will not overlap. |
The player will respond with the following document:
{
"rc": {
"version": "1",
"status": "1",
"action": "screenshot_request",
"id": "1",
}
}
Screenshot Request Action - JSON Parameters
Note: If using JSON via the WebSocket server, any firewall present on Broadsign Control Player should be configured to access port 2326 directly for use.
Parameter | Description |
---|---|
version | Mandatory. The version is always 1. |
id | Mandatory. Represents a client-generated unique identifier for the request. This will be passed back unchanged to the dest_url in the HTTP request headers. Maximum any 64 characters. |
action | Mandatory. The kind of action to be taken; always screenshot_request. |
dest_url | Mandatory. The client-supplied URL to which the screenshot will be uploaded, in jpeg format. |
scale_factor | Optional. Integer, 1-100. 100 = full resolution. Aspect ratio is preserved. |
burst_duraton_ms | Optional. Represents the total duration, in milliseconds, for which the player should send multiple screenshots at the specified burst_frequency. |
burst_frequency_ms |
Optional. Default = 3000. If burst_duration_ms is specified, burst_frequency_ms dictates the number of milliseconds between screenshots. Note: The total amount of screenshots sent will be burst_duration_ms / burst_frequency_ms. If burst_frequency_ms is less than the actual time it takes to capture a screenshot and send it, the screenshots will not overlap. |