-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
missing "now playing" values on screensaver #70
Comments
Are you saying this was a problem with the SB3's Now Playing screensaver only? The web UI would show the track information? Can you share a "screenshot"? |
Your SB isn't synced with another player, is it? Please enable debug logging for |
not synced uploaded logs. I ran through the procedure in the last few minutes after 16:50 in the logs:
|
Trying to reproduce this... what screensaver are you using? I'm seeing SaverSwitcher is involved. Could you please go back to just the default Now Playing screensaver. Is the behaviour the same? From the log I'm not seeing what I hoped I'd see. How technical are you? Would you be able to modify one of the source files to try something out? |
I am technical, but I do not have much perl experience. I definitely do some guided modifications. This is the "now playing" value which pops up for a brief period when "screensaver while playing" is active. Note that this triggers when the track changes (either due to track end and next track on playlist or track change via API). The video is of the "spectrum analyzer" value of "screensaver while playing": When using the "now playing" value of "screensaver while playing" the value is correct. Even with the "spectrum analyzer" screensaver active and showing an "empty" value, you can also see in the video a very brief view of the "now playing" screen which appears to be correct. See second 6-10 of the video: 2024-04-02-10-36-45-451.mp4More red herring research: Here is a reference which only adds the |
Can you please confirm the default Now Playing screen saver would behave the same? |
When using the "now playing" setting for "screensaver while playing" the value is correct. |
I'm sorry, this has to wait. This seems to be a rather exotic issue (legacy players only, specific screensaver only, TIDAL only(?), when adding tracks over JSON/RPC only). I'm not even sure whether this is a TIDAL or an LMS issue. I have to prioritise other work. Please ping me again once the Lyrion transition has settled. Thanks for your understanding! |
No worries, I understand the priority. Some additional research I did via the logs (this is the first I saw of the logs). I note that the
The following is an example of a never before played track from another never before played album
I think the The following example log shows after "search for track and play" procedure. Notably this includes a "setTitle" action (presumably triggered from Tidal plugin):
|
I am calling the plugin using the very handy
tidal:
andhttps://listen.tidal.com
protocol handlers like so:All of the track information is present when inspecting details when browsing with the remote and in in LMS, but the "now playing: " only on the "now playing" screensaver is blank if I have not started the song from the Tidal app in LMS before. If I start the song, then it will always display the screensaver now playing value correctly.
I can replicate this down to individual tracks within an album.
I believe this has something to do with how the plugin syncs/stores the values of the tracks. Maybe there is a specific value used by the screensaver which is not populating via the protocol handler pathway?
I noted that
current title
fromstatus
command is empty when playing the tracks with missing valuesUsing my freshly fixed SB3 with this fantastic plugin. Very impressed with completeness and polish!
The text was updated successfully, but these errors were encountered: