PIXILAB Player is a free software for making a player or interactive kiosk out of a small form-factor PC (such as a "NUC computer"), for use with Blocks as a Display Spot. This article describes how to install PIXILAB Player.
We recommend using a NUC computer. For basic applications in HD resolution, you can choose a low-cost, Celeron based model. For most applications, an i3- or i5-based model is sufficient. For demanding applications, select an i7-based model, or faster.
The player needs 8 GB of RAM to be installed. Choose RAM of the fastest type supported by the computer. For optimal video performance, two RAM modules are recommended for best memory bandwidth.
For best performance and additional capabilities, an internal SSD is recommended. Alternatively, the player can be started directly from a USB memory stick, without the need for an internal SSD
Start by going to https://pixilab.se/outgoing/blocks/player-maker7/ (see below) which provides instructions for downloading the latest PIXILAB Player image as well as creating a configuration file for your player. Store the downloaded files somewhere on your computer. For more information about the various configuration options, see the Configuration Options section below.
After downloading the disk image and your configuration file, use Etcher to transfer the disk image to the USB stick.
When Etcher has transferred the image to the USB stick, copy the just downloaded configuration file (named “playerconfig.txt”) to the USB stick. If the USB stick doesn't appear in Explorer/Finder, try removing the USB stick and inserting it again. If multiple external drives appear, select the one labeled "PIXICFG".
IMPORTANT: The configuration file must be named "playerconfig.txt" and be placed at the root-level of the USB memory stick.
After copying the “playerconfig.txt” file to the USB stick, do as follows:
NOTE: If the computer doesn't boot from the USB stick, you need to enter its BIOS and change its boot settings to boot from USB. You may also need to turn off any Secure Boot option.
If you have configured PIXILAB Player to run from the USB stick (i.e., you set the “Install on internal disk” option to “no”), the installation is now complete. Once the player has booted, you should see the PIXILAB logo on the screen with an ID string below, allowing you to add it as a Display Spot to Blocks.
If you are installing PIXILAB Player on an internal SSD, you should see a screen similar to this once the player has booted.
To test the configuration without installing PIXILAB Player on the internal disk yet, press "t". Note that some features such as block caching are not available in the test mode. Reboot the computer to leave the test mode.
To install PIXILAB Player on the internal drive, press "i". The installer will automatically detect the internal drive and install the system onto it.
When the installation has finished, remove the USB drive and power off the player. Connect the player to the network used by the Blocks server (if it is not already connected) and power on the player again. If everything works as expected, you should see the PIXILAB logo on screen with an ID string below, allowing you to add it as a Display Spot to Blocks.
In most cases, only three settings need to be specified:
Enter only the IP address or domain name in the text field. Do not append "/spot" or any other path. When using our Linux based server image, you don't need to specify a port number. However, if you're running Blocks on your Mac or Windows computer, also append any non-standard port number separated by a colon, e.g. :8080.
Additional options can be accessed by checking “Show advanced settings”. Some of these options require more details to be specified and may reveal additional options. Hover over an option to learn more about it, its use cases and possible values.
If you're exposing your Blocks server to the Internet, you're strongly advised to use an encrypted server connection (HTTPS). Note that this requires a domain name and an associated certificate to be installed on your Blocks server.
If players are used only on an intranet, and don't connect over the Internet, you do not need to run HTTPS on those players. In general, unless explicitly forbidden by your server's configuration, players can access the server over HTTP even when the editor and other secure endpoints use HTTPS.
We strongly recommend that you use a hardware network connection (Ethernet) whenever possible. However, if you must use a wireless WiFi connection, you can enable that here. When enabled, you must then specify the network name (SSID) and password for accessing the network.
If no DHCP server is available, it is possible to manually configure the network settings for the player. By setting this option to “Manual”, the IP address (with subnet mask in CIDR notation), the default gateway and the DNS server must be specified.
If the player is behind a proxy server, enable this option. You must then enter the address to the proxy server. You can also provide a comma-separated list of addresses that should bypass the proxy server.
Enables hardware-assisted video decoding on hardware that supports this. This may improve video playback performance, but may in some cases cause other problems or stability issues, so make sure you test on representative hardware and content before deploying players with this function enabled.
We strongly recommend that PIXILAB Player is installed on an internal disk for maximum reliability and performance. However, it is possible to run PIXILAB Player directly from the USB stick without installing onto a disk by setting this option to “no”. Note that some features such as block caching and remote upgrades are not available when running from USB.
If you need to access local time on the player (e.g., for some custom web content), select the local time zone where the player will be used.
If you specify a timezone to access local time on players, you may also want to specify a custom time server used to set the clock in the player. If not specified, a default NTP server will be used.
This string will be appended to the Spot page URL. It can be used to append query parameters to the URL.
The configuration set through the web-based user interface described above results in settings in the playerconfig.txt file. As an alternative to using the web-based user interface, you can set options directly in the playerconfig.txt file. This can also be used to change settings for a player later.
Each setting in the playerconfig.txt file consist of a single line in the form:
key=value
Valid keys are listed below in bold, with values described in the following text.