Streamit Lisa Compact, Руководство пользователя

Страница: 65 / 109

Lisa Compact 65
A stream timeout counter higher than zero does not necessarily mean that the end user has
heard issues with the audio. The Lisa has a buffer that lasts many seconds. Many
consecutive read timeouts will eventually result in an empty audio buffer and the end user will
hear a silence while the device reconnects (and re-buffers), or resorts fallback.
disconnec
t The number of times the stream was disconnected since the last ‘periodic’ connection
Each time the connection with the streaming server is unexpectedly terminated, the
disconnect counter will be increased. When no fallback is possible, or when the device was
playing a playlist stream, the device will try to establish the connection as soon as possible
and pick up the stream where it left off. When the connection is re-established before the
buffer has run out of data, the end user will not notice any problems (no silence in the audio).
When the device does not succeed to connect to the stream before the buffer runs out of
data, the audio will stop playing.
When fallback is possible and the device is playing a direct stream (no playlist), a disconnect
from the streaming server will make the device switch to fallback immediately. When this
occurs, the end user will hear a silence while the device prepares to start playing from card.
buf.emp The number of times the buffer of the Lisa ran out of data since the last ‘periodic’ connection
When the device receives less data than it consumes, the audio buffer will run empty. When
this occurs, the end user will hear a silence while the device re-buffers.
fallback The number of times the Lisa switched to fallback since the last ‘periodic’ connection
14.4 Event-driven log messages
Event-driven log messages
In addition to the periodic log messages, the Lisa also sends log messages when the device goes into a
certain state, e.g. when the playlist update is started etc. For a large part the log message is the same
as a
periodic log message . However, the information on stream stability is left out and an extra message
is added to describe the event or state change. Currently the following messages have been
implemented.
Message Description
<scheduled_task> task started
<scheduled_task> task failed
Task scheduler triggered, or failed to trigger,
execution of a task. Triggering may file because the
task misses information, has wrong parameters,
there is no card in the Lisa while the task requires a
card, etc.
Tasks that can be reported:
Activate device
Clean up card
Comm. & Ann. update
Configuration update