My Jive clients (Jivelite/Touch) are currently out of sync. server 7.9.1 on osx
This one and similar events triggers an update of the web interface and ipeng
[17-10-30 13:05:42.1375] Plugins::RadioParadise::ProtocolHandler::getMetada taFor (171) Not sure I'm in the right place - scheduling another update soon
[17-10-30 13:05:42.2214] Plugins::RadioParadise::ProtocolHandler::getMetada taFor (145) Current playtime in block (https://apps.radioparadise.com/block...ac?src=alexa): 271.1
[17-10-30 13:05:42.2218] Plugins::RadioParadise::ProtocolHandler::getMetada taFor (175) Scheduling an update for the end of this song: 164
The log is flooded with
[17-10-30 13:08:26.6081] Plugins::RadioParadise::ProtocolHandler::getMetada taFor (133) Returning cached metadata
Which makes it a little difficult to spot which getMetadataFor (175) triggers an update on Jive. Currently the Jive clients sometimes update in the middle of a song and I see many 171, 145, 175 sequences.
Should getMetadataFor (175) trigger the update on Jive? If not what should I look for?
This one and similar events triggers an update of the web interface and ipeng
[17-10-30 13:05:42.1375] Plugins::RadioParadise::ProtocolHandler::getMetada taFor (171) Not sure I'm in the right place - scheduling another update soon
[17-10-30 13:05:42.2214] Plugins::RadioParadise::ProtocolHandler::getMetada taFor (145) Current playtime in block (https://apps.radioparadise.com/block...ac?src=alexa): 271.1
[17-10-30 13:05:42.2218] Plugins::RadioParadise::ProtocolHandler::getMetada taFor (175) Scheduling an update for the end of this song: 164
The log is flooded with
[17-10-30 13:08:26.6081] Plugins::RadioParadise::ProtocolHandler::getMetada taFor (133) Returning cached metadata
Which makes it a little difficult to spot which getMetadataFor (175) triggers an update on Jive. Currently the Jive clients sometimes update in the middle of a song and I see many 171, 145, 175 sequences.
Should getMetadataFor (175) trigger the update on Jive? If not what should I look for?
Comment