CPU: Intel(R) Core(TM) i5-3610ME CPU @ 2.70GHz
RAM: 4GB
GPU: Intel(R) HD Graphics 4000
DISK: SATA SSD 64GB
See also Players comparison
All layouts size supported by the hardware
| Format | Color space | Limits |
|---|---|---|
| JPG | RGB | No CMYK |
| PNG | RGB, RGBA | Only 24 bit (no palette); support for alpha channel |
| BMP | RGB | Only 24 bit (no palette) |
test bed: fullscreen layout FULL-HD (1920x1080)
| Format | Codec Video | Codec Audio | Max bitrate (kb/s) |
|---|---|---|---|
| AVI | H.264 | MP3 | 10000 |
| WMV | Windows Media Video 9 (WMV3), VC1 | WMA2 | 5000 |
| FLV,F4V | On2’s VP6.2 (VP6F), H.264 | MP3 | 10000 |
| MP4 , MPG, M4V, MOV, AVI | H.264 | MP3, AAC | 10000 |
| MP2, MPG, MPEG, VOB | Mpeg2 (MPGV), Mpeg1 (MPGV) | MP3 | 10000 |
| Format | Codec Video | Codec Audio | Max bitrate (kb/s) |
|---|---|---|---|
| HLS | H.264 | MP3 | 10000 |
| RTMP | H.264 | MP3 | 10000 |
1 o 2 audio channels at 16bit 44.1KHz
The complexity of layouts (number and sized of zones) and the numbers of video in execution at the same time (more than 2) can introduce issues on playout due to the hardware resources needs for decoding.
The limits reach can be identified by:
- freeze o skips of video frames
- audio cracking or disturbed
| Format | Codec Audio | Max bitrate (Kb/s) |
|---|---|---|
| MP3 | MP3 | 320 |
| WMA | WMA2 | 320 |
| MP4 | MP4 | 320 |
| WAV | PCM16LE | 1400 (CD Quality: 16 bit stereo 44100 Hz) |
Xuniplay Player is compatibile with VAST 2.0 specification with the following restrictions:
When using Google Ads on Xuniplay Player, the VAST url needs some placeholder that will be set by the Player:
correlator=[ts] : the Player should set to a truly random, positive, integer value that is not being reused by multiple page views (reference: https://support.google.com/admanager/answer/10678356?hl=en#correlator)
ppid=[ppid] : ppid parameter accepts a variable value of the identifier is used in frequency capping, audience segmentation and targeting, sequential ad rotation, and other audience-based ad delivery controls across devices; the value should be some sort of encrypted/hashed data; (reference: https://support.google.com/admanager/answer/10678356?hl=en#ppid)
To configure the VAST url placeholders on Player, see document Replace-VAST-fields
An example of Google Ads VAST url used for tests:
https://pubads.g.doubleclick.net/gampad/ads?iu=/22248368690/DOOH_sample_campaign&tfcd=0&npa=0&sz=1080x1920&gdfp_req=1&output=vast&unviewed_position_start=1&env=vp&correlator=[ts]&ad_type=video&vpmute=1&vpa=auto&vpos=preroll&wta=0&scor=17&ppid=[ppid]
Using placeholders:
correlator=[ts] : Player is configured to replace [ts] with current timestamp (epoch ms)ppid=[ppid] : Player is configured to replace [ppid] with md5(ZoneID+XPPID)