Cache Control – This section controls the storage and cache limits.
* Clear Cache – Clicking this will clear all the downloaded contents in order to free space.
* Cache Location – The location of the cache (your media items). There are 3 options:
* External storage (this is the default)
* Internal storage
* Custom path (for disk-on-key USB stick, SD card or anywhere else)
* Cache Cleanup – Toggles the conditioned cleanup rules (the default is off).
* Min Free Cache – This is the minimum free memory allowed (in MB). Crossing it will trigger the cleanup of unused media files.
* Max Free Cache – This is the maximum memory (in MB) that will be free after cleanup. That means that if the cleanup process was triggered and
started cleaning, it will stop once it reaches this amount of free storage (or when it has nothing else to clean from the cache folder).
* Max Allowed File Age – This is the number of days of old unused files to be cleaned. The default is 60 days. Every day at midnight, all media files which
are unused for 60 days or more will be deleted from the cache.
* Webimage Widget Refresh Period – This is the refresh period for webimage widget in minutes. the default is 120 (2 hours). That means that every 2 hours the widget will look for new file.
Server Configuration – This option allows you to choose which of NoviSign’s cloud server will be the source for this player app media.
Force Notifications – This setting makes all notification settings behave as turned on. The default is off.
Video Transitions Tune – This section performs fine tuning for the video transitions. Only in some cases, it is required to alter this setting.
* Manual Init Compensation – Toggles this whole section, in case you want to alter the default settings. The default is off.
* Buffer Delay – The buffer duration threshold (in milliseconds). When the Manual Init Compensation is turned off, the default is 30ms, while when the Manual Init Compensation is on, the default is 300ms. For MXQ Pro player, use 300 and “Performance” video transition; for X96 player, use 220 or 260 or 300 (depends in the firmware) and “Performance” video transition. For other devices, which have transition issues, it’s a trial and error.
* Buffer Count – Minimal buffer update count threshold. The default is 1. No need to change it.
Transitions Duration – The default duration for video transitions in milliseconds. The default is set to 1,000 (1 second).
Wait Video Init – This setting will force the app to wait for the video initialization before start playing it (might be helpful in rare cases). The default is set to off.
External Interfaces – This section controls interfaces with the hardware.
* Camera – Toggles using an external camera (usually for integrating with face recognition 3rd party software). The default is off.
* RF ID Reader – Toggles using an RFID or barcode reader. Actually, whenever you use an external device which sends keyboard events, you should turn on this setting, in order to allow the APK to accept keyboard events. The default is off.
* Custom Event Transmitter – Toggles using any external device that can trigger events by transmitting HTTP responses to this device in a certain XML format. The default is off.
* IoT Remote Events – Submenu for the remote events feature (by getting them from a cloud web server, instead of getting the keyboard events directly from a connected USB IoT device).
** Enable Remote Events – Toggles using the remote events feature. The default is off.
** Event Name Prefix – Filters the product code (i.e. RFID tag code) to be sent to the web server. The default is ALL.
** Custom Remote Events API URL – URL of your web server for responding to the app (the cloud that should respond with events). The default is empty.
** Integration API Key – If the cloud’s API requires a key (will be sent in the header as api-key), this is where you should type it. The default is empty.
* Pricer Integration – Settings related to integration with Pricer price tags server.
** Enable Pricer Integration – This allows the APK to integrate with a Pricer server. Then you choose only ONE: either local Pricer server or a SaaS Plaza Pricer server.
** Enable Pricer Local Integration – This option is for integrating with a local store Pricer server.
** Pricer Server Host – This should be the IP address of the local Pricer server you’re integrating with (i.e. 192.168.1.66).
** Pricer API Key – This should be the API REST key coming from Pricer local store server you’re integrating with.
** Enable Pricer Server Integration – This option is for integrating with a SaaS (cloud) Plaza Pricer server.
** Pricer Basic Token – This is the token you should get from the Pricer SaaS server for authentication (it looks like a sequence of random characters).
** Items URL – This is the URL of the Pricer SaaS server for accessing the items data (i.e.e might look something like https://central-manager.nrf2022-us.pcm.pricer-plaza.com/cm/).
* Thermometer Events – This submenu is for setting a possible thermometer in the NoviTizer (NoviSign’s hand sanitizer kiosk).
** Enable Thermometer Events – In order to use the thermometer, you will have to turn on this setting (you will also have to turn on the “RF ID Reader” setting, in order to allow the unit to accept keyboard events). The default is off.
** Event Name Prefix – This is the keyboard event keys which will be sent as a prefix before the temperature degrees (separated with colon character). The default is “THERMO”. No need to change it.
** Fever Threshold – This is the threshold for fever detecting. That means, any reading (from the external thermometer) equals or above this value, will be considered as a person with fever and will trigger the thermometer fever event. For example, for Celsius degrees, you may want to put there something like 37.8 (in case you use Celsius degrees).
** Reading Threshold – This is the threshold for taking readings from the thermometer. Since some thermometers take a reading automatically every 5 seconds, no matter if a person is there or not, we would like to filter out all those demi-readings. For that, we need to set the threshold for taking readings. For example, for Celsius degrees, you may want to put there something like 35 (in case you use Celsius degrees), as below this temperature it is not a real human body temperature reading, which should not trigger anything.
* Custom API Integration – This submenu is for adjusting the settings for integrating this APK with API of some service.
** Name – This is the name of the API (you can give it any name).
** API URL – This is the URL of the API to be used.
** Refresh – This is the interval (in seconds) of communicating with this API.
** Request Type – Either GET or POST.
** Request Body – This can be a JSON format of the body to be received by the API (in case this API is expecting to receive a body part).
** Headers – Here you can add as many headers that are expected to be received from the API (in case this API is expecting to receive any header).
** Property Key – The variable which the response body of the API request will be saved into. And it will be used on the Studio CMS for presenting the response body with the dynamic data expression in the following format: ${@customapi.[property_key].[JSON_path]}
Example: ${@customapi.SHELF.Item0.Price}
** Send Event on Change – The event written here (for example, “RFID:1”) is the event that will be triggered in case the JSON response (any of its values) has been changed when the received input from the API. Notice that you can also test the API by pressing the “TEST” button below.
* Serial Events Settings – Toggles using a serial external device (like a sensor) and has a submenu.
** Vendor Id – The ID of the serial device vendor (should be in 10 base and not in hexadecimal base number).
** Product Id – The ID of the serial product (should be in 10 base and not in hexadecimal base number).
Event Transitions – This section controls the touch and event transitions.
* Touch Transitions – Overrides the default transition settings for touch events only. The default is off.
* Touch Transition Duration – The touch transition duration in milliseconds. The default is 2000. Setting it to 1 millisecond will be the fastest possible transition.
* Touch Skip Video Ready – Ability to start the transition without waiting for the video readiness (in Android it’s instantly). The default is off.
* Event Transitions – Overrides the default transition settings for all other events (mainly keyboard events. The default is off.
* Event Transition Duration – The event transition duration in milliseconds. The default is -1. Setting it to 1 millisecond will be the fastest possible transition.
* Event Skip Video Ready – Ability to start the transition without waiting for the video readiness (in Android it’s instantly). The default is off.
* Reset Next Item Countdown – Ability to reset the next creative duration after every interaction with the player. The default is set to on.
Use Local Properties – Ability to load settings values from local properties. The default is set to off.
