mherger wrote:
> What kind of player are you using in this case? Are you syncing players?
> Any 3rd party software involved?
Usually a Touch, but also Radios. The Touch has EDO; no other 3rd party
software being used. I get the problem on any/all players, whether
synced or not.
mherger
Just submitted another log, with player.source=INFO enabled.
I have only included today's log. A bunch of possibly interesting stuff
was generated at 09:40, when a skip occurred, then nothing more was
logged for sometime after that.
Living room: SB Touch, with coax to: Marantz PM7005, TDL
And another log (..._2), a bit longer.
09:56:59.7628 of interest?
Living room: SB Touch, with coax to: Marantz PM7005, TDL RTL3 speakers.
Dining room: SB Boom.
Kitchen: SB Radio 1/4 with battery.
Bedroom 1: SB Radio 2/4 no battery, SB Radio 3/4 with battery.
Bedroom 2: SB3 1/2, AE 2.1.
And another log (..._2), a bit longer.
09:56:59.7628 of interest?
Hmm... that's interesting, but unlikely the cause for Bill chiming in
randomly. A comment in the code mentions that the "queue too long" can
happen when there's a very short track. Bill's announcement could
potentially be
Ge Ba wrote:
> hi Philippe,
>
> I have authorised the API in my Google Account, but suddenly the plugin
> stopped working for me. There I was an auto-update from Synology, so I
> hope it didnt break anything.
>
> Just repeated the authorisation, to no success.
>
> [18-09-06 00:30:41.3398]
hi Philippe,
I have authorised the API in my Google Account, but suddenly the plugin
stopped working for me. There I was an auto-update from Synology, so I
hope it didnt break anything.
Just repeated the authorisation, to no success.
[18-09-06 00:30:41.3398]
pippin wrote:
> Right now, it's only bug fixes, I'm afraid
Hi Pippin,
I'm using the IckStream plugin with Tidal, and it works beatifully...
Thanks for that :)
Do you have a roadmap for the project - any plans of adding additional
services?