chill wrote:
> disabled the 'maintain sync while playing' option they went noticeably
> out of sync much faster than every 37 seconds - even after a few seconds
> I could hear the difference.
By glitch I assume a short gap of silence but no audio missed. This
does seems otbe player buffer running out - very unusual unless using
Flac or high rate compressed as player normally buffer at least a
minute. It is possible using logging to see fullness of the player
audio buffer and the decoded output buffer. For a glitch to occur
output would have to be empty (also implies audio buffer is also
empty).
Example of a stream starting and how buffers are filled up -
network.protocol.slimproto set to INFO
Code:
--------------------
[19-07-17 15:26:58.3468] Slim::Player::Squeezebox::stream_s (928) Using smart
transition mode
[19-07-17 15:26:58.3474] Slim::Player::Squeezebox::stream_s (988) Starting
decoder with format: f flags: 0x0 autostart: 1 buffer threshold: 255 output
threshold: 20 samplesize: ? samplerate: ? endian: ? channels: ?
[19-07-17 15:26:58.3494] Slim::Networking::Slimproto::_stat_handler (785)
74:da:38:a6:39:77: STAT-STMf: fullness=0, output_fullness=-1, elapsed=0.000
[19-07-17 15:26:58.3495] Slim::Networking::Slimproto::_stat_handler (785)
74:da:38:a6:39:77: STAT-STMf: fullness=0, output_fullness=-1, elapsed=0.000
[19-07-17 15:26:58.3496] Slim::Networking::Slimproto::_stat_handler (785)
74:da:38:a6:39:77: STAT-STMc: fullness=0, output_fullness=-1, elapsed=0.000
[19-07-17 15:26:58.4528] Slim::Networking::Slimproto::_http_response_handler
(554) Squeezebox got HTTP response:
HTTP/1.1 200 OK
Server: Logitech Media Server (7.9.2 - git-4153ef839)
Connection: close
Content-Type: audio/x-flac
[19-07-17 15:26:58.4995] Slim::Networking::Slimproto::_stat_handler (785)
74:da:38:a6:39:77: STAT-STMs: fullness=1376256, output_fullness=1824768,
elapsed=0.000
[19-07-17 15:26:58.5001] Slim::Networking::Slimproto::_stat_handler (785)
74:da:38:a6:39:77: STAT-STMt: fullness=1376256, output_fullness=1824768,
elapsed=0.000
[19-07-17 15:26:59.5009] Slim::Networking::Slimproto::_stat_handler (785)
74:da:38:a6:39:77: STAT-STMt: fullness=2097151, output_fullness=3262464,
elapsed=0.993
[19-07-17 15:27:00.5015] Slim::Networking::Slimproto::_stat_handler (785)
74:da:38:a6:39:77: STAT-STMt: fullness=2097151, output_fullness=3257080,
elapsed=1.998
[19-07-17 15:27:01.0008] Slim::Networking::Slimproto::_stat_handler (785)
74:da:38:a6:39:77: STAT-STMt: fullness=2097151, output_fullness=3263224,
elapsed=2.496
--------------------
> I gave my new mesh network the same name as my old wifi network, so
> maybe pCP is remembering something about the old network that isn't
> suitable for the new one. Perhaps I should just give the new network a
> different name.
I think having same name might cause problem as some network
characteristic may only be detected/saved when first validated.
------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=110765
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/discuss
