Originally posted by Shozzer
View Post
Announcement
Collapse
No announcement yet.
Announce: Material Skin
Collapse
X
-
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
-
Originally posted by rgdawson View Post
Perhaps you could arrange the buttons the same way you do in now playing, that is, thumbs to the left and right of the skip/play/pause/skip group. That is where I would expect to see them and it would seem more consistent.
And for Pandora you could hide the Skip Back as there is no such thing and it is disabled anyway.Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
Comment
-
3.1.2 release, changes:
1. If browsing into a composer via "All Artists" try not to show artist (composer) on track line.
2. Fix artist not showing if "Show artist first in now-playing and queue" is set to "No" in Material's server side settings.
3. If showing Pandora thumbs up/down then don't show technical info in desktop layout bottom bar.
4. Prevent technical info from overlapping track meta-data in desktop layout bottom bar.
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
- Likes 3
Comment
-
Originally posted by ptou View Post
I had an idea, maybe the rating does not get cleaned when track changes naturally? If the next track has a rating, it correctly overwrites the previous one, but if no rating is present (the field in the json response is completely missing), then the rating field is not reset but keeps the previous track value.
This may also justify why when maximizing/minimizing the rating updates, because in this case the whole interface must be re-painted and all fields start from empty (which corresponds to no rating provided).
Let me know if I can help in checking if my hypothesis is true, with some hints to where to look in the code.
Note: Running Material under Squeezelite-X I have never had problems with the ratings not updating.
Logitech Media Server Version: 8.3.0 - 1667251155 @ Fri Nov 4 09:09:12 WEST 2022
Operating system: Windows 11 - EN - cp1252
Platform Architecture: 8664
Perl Version: 5.14.1 - MSWin32-x86-multi-thread
Audio::Scan: 1.05
IO::Socket::SSL: 2.068
Database Version: DBD::SQLite 1.58 (sqlite 3.22.0)
Additional Browse Modes 1.0
Last.fm Audioscrobbler 1.0
Material Skin 3.1.2
Presets Editor 1.0
Radio 1.0
Random Mix 1.0
TrackStat 3.3.602
Comment
-
Originally posted by cpd73 View Post
Sorry, but no. The code for this bottom toolbar is too much of a pain as is - and I don't use Pandor (nor show tech info).Squeezelite-X
- Likes 1
Comment
-
Originally posted by KTSq View Post
Thank you very much both of you for looking into this. I have the same problem using the app on Android, and I will be happy to help if you need me to test anything. (My workaround to see the correct rating for the track playing is to click “Queue”, and then back to “Playing”.)
Originally posted by KTSq View PostNote: Running Material under Squeezelite-X I have never had problems with the ratings not updating.
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
Comment
-
Originally posted by rgdawson View Post
I see. Well, my thought was it might be similar to that button block as implemented elsewhere and therefore easier for you, but I guess not.. I've never used those like/don't like buttons in my life and never will, so would not mind never seeing them anyway. How do you turn those off?Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
Comment
Comment