Announce: Material Skin

[sveninndh]

I have downloaded and installed the complete new version.
I deleted the browser cache and cookies.

Now it works on my Android phone and on my pc with ms edge.
But curiously it doesn't work with the Brave (chrome) browser.
But the 'add' button now works with Brave (chrome), only the 'play' button doesn't work yet.

I have to correct myself here. The remaining problem with Brave is apparently a local problem on my computer because it also works fine with Brave on my notebook. How I hate those things that put me on the wrong track in the first place.

[bossanova808]

This is the button that controls the view, doesn't it work on an iPad?

That button works fine to enter/exit the view in question, and is not the issue as such - the issues is what results from using that button, the view itsld - there are two styles of the Extended Now Playing, it seems, and I prefer the side by side one and would like to make that the only version that is used.

[SamY]

Hi, Craig. I have a very simple question. In my library view, it seems that the release year is always displayed next to the album name, which I like very much. My question is: Is there an option somewhere that controls this? I couldn't find it if there is. For the default skin, it is an option that can be specified on the Interface settings of LMS. Thanks.

[cpd73]

Hi, Craig. I have a very simple question. In my library view, it seems that the release year is always displayed next to the album name, which I like very much. My question is: Is there an option somewhere that controls this? I couldn't find it if there is. For the default skin, it is an option that can be specified on the Interface settings of LMS. Thanks.

No, the display in Material is not configurable. It does not use the 'Interface' settings, hence these are hidden when accessing server settings from Material

[SamY]

Thanks for the reply to my previous question, Craig. On a related topic, when adding albums/tracks to the queue from the library view, the release year is picked up and displayed next to the album name in the queue. However, the release year is not displayed when adding the same album/track from the Qobuz plugin view. Where does MS look for the release year? Here is the JSON request coming from the plugin, where the year is not displayed in the queue. It looks pretty much identical to the message from the library view adding the same track, including the 'year' field being populated. Any ideas?

10:44:53 AM] JSON PLAYER (b8:26:eb:c1:71:f0): {"seq_no":0,"mixer volume":39,"player_name":"Max2Play","playlist_trac ks":2,"player_connected":1,"mode":"stop","playli st _timestamp":1677685493.57322,"power":0,"playlist mode":"off","playlist repeat":0,"playlist_cur_index":0,"playlist_loop":[{"bitrate":"750kbps","album_id":"1464","disccou nt" :"2","playlist index":0,"trackartist_ids":"3112","samplesize":"16 ","coverid":"586dcae4","artist_id":"3112","url ":"q obuz://3963525.flac","id":16100,"composer_ids":"3459","sa mplerate":"44100","artist_ids":"3112","duration":" 330","artwork_url":"/imageproxy/https%3A%2F%2Fstatic.qobuz.com%2Fimages%2Fcovers%2 F31%2F30%2F0060251743031_600.jpg/image.jpg","genre":"Pop","album":"August And Everything After","tracknum":"1","artist":"Counting Crows","title":"Round Here (Album Version)","type":"flc","disc":"1","year":"1993"}],"signalstrength":0,"digital_volume_control":0, "re moteMeta":{"id":16100,"title":"Round Here (Album Version)","coverid":"586dcae4","duration":"330","a lbum_id":"1464","genre":"Pop","disc":"1","album":" August And Everything After","type":"flc","disccount":"2","bitrate":"750 kbps","artist_id":"3112","tracknum":"1","url":"qob uz://3963525.flac","year":"1993","artist":"Counting Crows","samplesize":"16","artwork_url":"/imageproxy/https%3A%2F%2Fstatic.qobuz.com%2Fimages%2Fcovers%2 F31%2F30%2F0060251743031_600.jpg/image.jpg","artist_ids":"3112","composer_ids":"345 9","trackartist_ids":"3112","samplerate":"44100 "}, "playlist shuffle":0,"player_ip":"192.168.1.11:58680"}

EDIT: Here is a screenshot of the queue showing the same Qobuz track, the first added from the library view and the second from the Qobuz plugin view:

[cpd73]

Thanks for the reply to my previous question, Craig. On a related topic, when adding albums/tracks to the queue from the library view, the release year is picked up and displayed next to the album name in the queue. However, the release year is not displayed when adding the same album/track from the Qobuz plugin view. Where does MS look for the release year? Here is the JSON request coming from the plugin, where the year is not displayed in the queue. It looks pretty much identical to the message from the library view adding the same track, including the 'year' field being populated.

That JSON you posted is from a status message, I assume, and its only showing the one track. You need to post a JSON message that has both. Anyhow, the year is taken from the "year" in the response.

[SamY]

That JSON you posted is from a status message, I assume, and its only showing the one track. You need to post a JSON message that has both. Anyhow, the year is taken from the "year" in the response.

Okay. I've been doing some more testing and ran into this JSON status request and response where the second track (the one from Qobuz without the year displayed) seems to have TWO "year" attributes associated with it --- the first with "0" and the other from the "remoteMeta" attributes with the correct value "1998". I don't know, however, where the "0" field is coming from. Any ideas?

[12:55:09 PM] JSON REQ: ["cc:cc:68:62:41:ac",["status",0,5000,"tags:cdegilqtuysAAIKNSxx"]]
material.min.js?r=3.1.4:245

[12:55:09 PM] JSON RESP: {"params":["cc:cc:68:62:41:ac",["status","0",5000,"tags:cdegilqtuysAAIKNSxx"]],"method":"slim.request","id":0,"result":{"seq_ no" :0,"mixer volume":21,"player_name":"Bedroom pair","playlist_tracks":2,"player_connected":1,"mo de":"stop","playlist_timestamp":1677693309.32002 ," power":0,"playlist mode":"off","playlist repeat":0,"playlist_cur_index":0,"playlist_loop":[{"album_id":"1472","disccount":"1","playlist index":0,"trackartist_ids":"3481","remote":1,"samp lesize":"24","coverid":"12ceb25e","artist_id":"348 1","url":"qobuz://27056131.flac","id":16364,"composer_ids":"3483","a rtist_ids":"3481","duration":"360","artwork_url":"/imageproxy/https%3A%2F%2Fstatic.qobuz.com%2Fimages%2Fcovers%2 F30%2F71%2F0088807237130_600.jpg/image.jpg","genre":"Blues","album":"In Session","tracknum":"3","artist":"Albert King","title":"Pride And Joy","disc":"1","year":"1998"},{"playlist index":1,"duration":"360","artwork_url":"/imageproxy/https%3A%2F%2Fstatic.qobuz.com%2Fimages%2Fcovers%2 F30%2F71%2F0088807237130_600.jpg/image.jpg","remote":1,"samplesize":"24","coverid": "-232007292","album":"In Session","artist":"Albert King","url":"qobuz://27056131.flac","id":"-232007292","title":"Pride And Joy","year":"0"}],"signalstrength":0,"digital_volume_control":1,"remoteMeta":{"id":16364,"title":"Pride And Joy","coverid":"12ceb25e","duration":"360","album _ id":"1472","genre":"Blues","disc":"1","album":"I n Session","disccount":"1","tracknum":"3","url":"qob uz://27056131.flac","year":"1998","artist_id":"3481","a rtist":"Albert King","samplesize":"24","artwork_url":"/imageproxy/https%3A%2F%2Fstatic.qobuz.com%2Fimages%2Fcovers%2 F30%2F71%2F0088807237130_600.jpg/image.jpg","artist_ids":"3481","composer_ids":"348 3","trackartist_ids":"3481","remote":1},"playli st shuffle":0,"player_ip":"192.168.1.14:50340"}}
material.min.js?r=3.1.4:245

[cpd73]

Okay. I've been doing some more testing and ran into this JSON status request and response where the second track (the one from Qobuz without the year displayed) seems to have TWO "year" attributes associated with it --- the first with "0" and the other from the "remoteMeta" attributes with the correct value "1998". I don't know, however, where the "0" field is coming from. Any ideas?

Nope. And remoteMeta is not in the track list, but as an extra. Which, I guess means its only for one track. Do you have a status message like this for more tracks? Just to see if its only for one or for all.

[SamY]

Nope. And remoteMeta is not in the track list, but as an extra. Which, I guess means its only for one track. Do you have a status message like this for more tracks? Just to see if its only for one or for all.

I can generate one. What scenario exactly do you want to see? The behavior is consistent. All tracks added to the queue from the Qobuz plugin are missing the year. All tracks added from the library display the year. Again, here is what the queue looks like for the same Qobuz track, the first added from the library view and the second from the plugin.

[cpd73]

I can generate one. What scenario exactly do you want to see?

If you past your JSONRCP RESP messages into a JSSON formatter (e.g. https://jsonformatter.org/) you can see the structure of the respnse. e.g.

{
  "params": [
    ...
  ],
  ...
  "result": {
     ...
    "playlist_loop": [
      {
        "playlist index": 0,
        ...
        "year": "1998"
      },
      {
        "playlist index": 1,
        ...
        "year": "0"
      }
    ],
    ...
    "remoteMeta": {
      ...
      "year": "1998",
    },
    ...
  }
}​

Here you can see there is a "playlist_loop" with 2 entries, one with year 0 and one with year 1998. There's also a "remoteMedia" section, which also has a year. I was wondering if the queu ehad 2 (or more) remote trackss, does the "remoteMedia" have details for all tracks? My guess is no, and that it's only for the current track.

Anyhow, your original question was "where does Material get the year from" - and now you can see its from LMS.

[bossanova808]

Hi Craig

The Zap option you added a while back, seems to have disappeared? Was that intentional? I miss it!

[cpd73]

Hi Craig

The Zap option you added a while back, seems to have disappeared? Was that intentional? I miss it!

Foro 'Zap' you need to have (the original) 'Custom Skip' installed. However, I'm guessing you have 'Custom Skip 3'? Just checked and the code does not handle that case.

[SamY]

If you past your JSONRCP RESP messages into a JSSON formatter (e.g. https://jsonformatter.org/) you can see the structure of the respnse. e.g.

{
"params": [
...
],
...
"result": {
...
"playlist_loop": [
{
"playlist index": 0,
...
"year": "1998"
},
{
"playlist index": 1,
...
"year": "0"
}
],
...
"remoteMeta": {
...
"year": "1998",
},
...
}
}​

Here you can see there is a "playlist_loop" with 2 entries, one with year 0 and one with year 1998. There's also a "remoteMedia" section, which also has a year. I was wondering if the queu ehad 2 (or more) remote trackss, does the "remoteMedia" have details for all tracks? My guess is no, and that it's only for the current track.

Anyhow, your original question was "where does Material get the year from" - and now you can see its from LMS.

Thanks for your help, Craig. Just wanted to let you know that I am still trying to figure out why the 'year' attribute is not being populated correctly for playlist additions coming from the Qobuz plugin. Thanks very much for the link to the JSON Formatter tool. It sure makes it easier to parse those messages! And you were right about the "remoteMeta" section. It is only in the list once for the current track. In this case, it was for the one that came from the library, as opposed to Qobuz.

[carldickson]

HI, Is there a way of remembering the LMS password so every time I go to Material Skin I don't have to enter the password in on that device?

[cpd73]

HI, Is there a way of remembering the LMS password so every time I go to Material Skin I don't have to enter the password in on that device?

That is controlled by tour browser - this login dialog happens before Material is loaded.