Deprecated logs

From SpinetiX Support Wiki

Jump to: navigation, search
This article is a stub. Main article: Logs.


These logs are deprecated and were merged into player.log in firmware 3.1.0.


The info log main purpose is to keep a real-time "heartbeat" record of the HMP performance. A log entry is added every 10s during the first 5 minutes of playing, and then one entry every minute.

Example log line:

10-12-2010 14:00:31 INFO spx.display.render - Render: 0:00:20 Nb Pic: 600 in 10ms ( 11ms) Max: 30ms Buffers: 62.7 (min 61) Factor: 1-1
  • 10-12-2010 14:00:31: Date and time of entry;
  • spx.display.render: Component of the player related to the log (mostly the renderer);
  • Render: 0:00:20: Player has been rendering 20s of content since the beginning.
  • Nb Pic: 600: The player has rendered 600 pictures since the last log entry.
    • When the output set at 60Hz, the HMP is functioning normally if this number is 600 during the first 5 minutes (when there's a log entry at every 10 seconds) and 3600 thereafter (when there's a log entry at every one minute). When the output set at 50Hz, the values are 500, respectively 3000.
    • A lower number means some frame were dropped - this is also reflected in the factor entry.
  • in 10ms ( 11ms): Average rendering time per frame. This should be below 16ms for optimal rendering at 60fps and below 20ms for 50fps.
    • A large number here means that the content is "difficult" to render and might shutter when displayed on the screen.
    • The number in brackets should be ignored.
  • Max: 30ms: The time the longest frame took to render. This should be below the maximum rendering latency to ensure that no frames are dropped. A larger number here means that a document took a lot of time to be opened.
  • Buffers: 62.7: On average, 62.7 buffer were used (a larger number is better). The maximum number of buffers depends on the resolution of the screen.
  • (min 61): The lowest level of the buffer since the last entry. A number bellow 4 means that some frames were drop. The larger number is better.
  • Factor: 1-1: The lowest and highest factor of the framerate (in this case, 60fps and 60fps). A number larger than 1 means that the player had to drop to a lower framerate to keep up with the rendering.
    • For instance 1-2 would mean that the player dropped to 30fps for some, but not all of the time since the last entry.
    • Some content (e.g. tickers) need a constant 60fps framerate to appear smooth.

Common errors:

  • No memory info messages:
    INFO  spx.display.framebuffer - No Memory : FBIO_POST_SWAP_CHAIN_SLOT no free slots
    These are appearing when changing some settings (that are not triggering a restart) or generating a report. They can safely be ignored.


Contains any errors generated by the JavaScript code within the project running on the HMP.

  • You can write to the javascript.log file using standard JavaScript alert() calls.
  • To change the global logging level, use the logAtLevel() method.


This log contains information about each resource played by the HMP, along with the date and time when it started. It can also include extra details about the video / audio streams inside the media, redirects, unsupported media etc.

The typical message that is added when a resource starts to play, has this format:
dd-mm-yyyy hh:mm:ss INFO   - New Resource 'URI' [flags] (dlc/tcd)
  • URI is starting with spx://localserver/ for local resources and with http(s):// for the external ones.
  • [flags] ([PCIC]) have the following meaning:
    P = PHP processing is done (i.e. the resource is .php).
    C = the caching mechanism is used for this resource (i.e. the resource is not local), but not necessarily that the resource is currently being played from cache.
    I = iCal processing is done (i.e. the resource is .ics).
    C = the resource is currently cached. (added in firmware 3.0).
    This flag is used in combination with the first C flag (i.e. [ C C]) and followed by the caching information (dlc/tcd).
  • (dlc/tcd) means "duration left in cache" from "total cache duration". (added in firmware 3.0)
    • dlc ("duration left in cache") can be either a number (of seconds) <= tcd or the string "----" meaning that the resource will be retrieved from the server.
    • tcd ("total cache duration") can be between 10s and 3600s.
Note Note:
The last 'C' char may be replaced by a '0' (i.e. [ C 0]), indicating that the cache mechanism is used for asynchronous retrieval, but that the resource is NOT cached. It will be retrieved each time it is needed by the player. In this case the (dlc/tcd) is not present.

If a resource is being played continuously in a loop, the above line is added only once at starting time. Nevertheless, in case of a media resource, one or more lines will be added each time the media is restarting - for instance:

date INFO - video H.264, 1920x1080  (16:9) 29.97 fps Main profile Level 4.0 NRF=1 MDFB=2
date INFO     - Found media stream: audio AAC, 48000Hz stereo
date INFO - [wmv3 @ 0x405bfa30]Extra data: 8 bits left, value: 0

Common errors

  • Unsupported media stream:
    Unsupported media stream: ffmpeg codec id=0
    If your video/audio file is not playing correctly then check the encoding settings on the Video encoding page. If your video is playing as expected and you still see this error in the logs, then it can safely be ignored; the player is discarding the streams it does not handle, such as subtitles and metadata.
  • Server or proxy hostname lookup failed:
    Server or proxy hostname lookup failed : '[requested_file_url]' -> Could not resolve hostname `[proxy_server]': Host not found
    HMP cannot connect to the Internet - check if you have correctly entered the proxy details.
  • Object Not Found:
    File not found : 'project://AutoServer0-4/index.svg' -> 404: Object Not Found
    The "Autoserver" source (followed by a number) represents a remote network path. If you see this error then you will usually be using Client/Server mode but you have specified the server source incorrectly. Check the source is a directory path, and not a file.
  • Stream demuxing failed:
    WARN - Stream demuxing failed because more than 1048576 bytes of buffering is required
    This is the result of a non-optimal multiplexing of the audio and video streams that requires more than 1 MB (respectively 3 MB in case of streaming media) of buffering of the audio or video stream in order to keep it in sync with the other. The solution is to re-multiplex the audio and the video streams using a software that creates correct multiplexing, like FFMpeg.
  • SSL certificate verification failed:
    HTTP Error : Command: GET on 'https://...' -> 0: Server certificate verification failed: issuer is not trusted
    The HMP could not verify the SSL certification for the resource URL and thus the resource is not loaded. Try using http or manually add the missing certificate on the HMP.


This log contains the device's starting events and, whenever possible, the stopping events.

A regular starting event contains the following information:

  • date and time;
  • HMP firmware version;
  • starting flags.
    • When the player boots into safe mode, the -safemode flag is added.

Example log line:

date time WARN spx.player - SpinetiX Hyper Media Player version 'Jungfrau 2.2.5-1.0.16095' started with : '/usr/bin/raperca -daemon'

The "Stopping player" event is written into the log whenever is possible - when the restart is triggered by:

Note Note:
Not all the stopping events can be logged - for example is not possible to log powering off the device.

Example log line:

08-11-2011 01:00:19 WARN  spx.player - SIGINT or SIGTERM received. Stopping player
This page was last modified on 30 August 2019, at 14:02.