Announce: Material Skin

[cpd73]

I'm seeing that obj class appear on all tracks where the artist tag has multiple entries.

Aaargh!!! That's because of the change to make artist, etc, links clickable (on non-touch devices) in the queue and browse - I forgot to update this view to handle that! Will fix, sorry.

[cpd73]

Is it possible and how do I revert to the previous version in case of...etc.?

No automated way, but all releases are available from https://github.com/CDrummond/lms-material/releases

[bwaldron]

Aaargh!!! That's because of the change to make artist, etc, links clickable (on non-touch devices) in the queue and browse - I forgot to update this view to handle that! Will fix, sorry.

I just updated to the latest version on github with the fix. Thanks!

However, I am still encountering a minor issue: I am seeing the "obj class" when viewing an album (in standard browsing view) with 100+ tracks. Obviously an edge case, but I do have some box set "albums" with this many tracks (I also use LMS for my collection of classic radio shows, and a number of those have many more than 100 episodes/tracks).

Clearly not a big deal (I love seeing composer info when browsing albums), but thought I'd let you know in case this can be easily fixed.

EDIT: I see this issue on my desktop browser (and Squeezelite-X), but all is fine using the (new) APK on my phone

[audiomuze]

I'm seeing some inconsistencies in display of composer and am not sure whether it's a bug or intentional. See composer display on left side vs queue on right. Composer display is inconsistent, appearing in some tracks, but not others on the queue side. There are 6 tracks with more than one composer tag. The track listing shows this is detected by Material, but not all make it to the the queue display.

[cpd73]

I just updated to the latest version on github with the fix. Thanks!

However, I am still encountering a minor issue: I am seeing the "obj class" when viewing an album (in standard browsing view) with 100+ tracks. Obviously an edge case, but I do have some box set "albums" with this many tracks (I also use LMS for my collection of classic radio shows, and a number of those have many more than 100 episodes/tracks).

Clearly not a big deal (I love seeing composer info when browsing albums), but thought I'd let you know in case this can be easily fixed.

EDIT: I see this issue on my desktop browser (and Squeezelite-X), but all is fine using the (new) APK on my phone

Same issue as before, just a different place for fix. The reason you do not see this on a phone is that its not used for touch devices.

[cpd73]

I'm seeing some inconsistencies in display of composer and am not sure whether it's a bug or intentional. See composer display on left side vs queue on right. Composer display is inconsistent, appearing in some tracks, but not others on the queue side. There are 6 tracks with more than one composer tag. The track listing shows this is detected by Material, but not all make it to the the queue display.

Is this on an iOS device? If so, can you try on a non-iOS device and see if it is the same? Also, can you list all the tags of an incorrect track? e.g. track 1 (Keep On Turning). I think the issue is that, for some reason, the composer and artist are being set to the same for the queue, and therefore not shown. But I need your tags so I can create a fake file with these and recreate the issue.

[slartibartfast]

Sometimes a long press on the DSTM symbol doesn't bring up the DSTM selection screen. It seems to go to the next option which is repeat off. It seems to happen after cycling through the repeat options to reach DSTM, but not every time.

Edit If you long press the symbol immediately after cycling through the options it works. If you leave a gap of say 10 seconds it always fails to open the DSTM settings.

Did this get missed? It's not a showstopper but I haven't noticed it before.

[cpd73]

Did this get missed? It's not a showstopper but I haven't noticed it before.

No, but works fine for me. Sorry, but I cannot recreate your issue - works fine every time for me.

[slartibartfast]

No, but works fine for me. Sorry, but I cannot recreate your issue - works fine every time for me.

Hmm OK. Here is another weird one. If I cycle through the repeat options I don't see the DSTM infinity symbol for any of my players except for a Radio.

Edit Never mind DSTM was disabled for the others 🤦♂️

[Shozzer]

I am experiencing an issue following the latest update and wonder if other users are seeing this too? When searching under Music Sources, pCP freezes, as if the system has gone into overload. I am curious if I am the only one having this issue? I first noted the issue when I tested a pre-release version of the plugin for Craig. The problem resolved when I reverted to the previous version. The exact issue returned today following the update to the plugin. Craig advised that he couldn't think of any code that would interfere with the search function. Thanks.

[audiomuze]

Is this on an iOS device? If so, can you try on a non-iOS device and see if it is the same? Also, can you list all the tags of an incorrect track? e.g. track 1 (Keep On Turning). I think the issue is that, for some reason, the composer and artist are being set to the same for the queue, and therefore not shown. But I need your tags so I can create a fake file with these and recreate the issue.

It's not on iOS, it's Chromium on Linux. Herewith tags:


And the raw tags from metaflac:


Tags from a track that is displaying correctly:


raw tags:

[cpd73]

I am experiencing an issue following the latest update and wonder if other users are seeing this too? When searching under Music Sources, pCP freezes, as if the system has gone into overload. I am curious if I am the only one having this issue? I first noted the issue when I tested a pre-release version of the plugin for Craig. The problem resolved when I reverted to the previous version. The exact issue returned today following the update to the plugin. Craig advised that he couldn't think of any code that would interfere with the search function. Thanks.

I've looked at the changed 3.0.3 and 3.1.0 and the only thing I can see that would affect the CPU load on the backend is that I ask for more meta-data back from tracks - this is to show composers, conductors, etc. The extra metadata requested is Genre, samplesize, extra artist IDs (for composer, etc). Perhaps fetching these extra IDs causes pCP issues? Not sure why. They are not part of the query, they jsut control what data LMS should send back for a track that matches the query.

[cpd73]

It's not on iOS, it's Chromium on Linux. Herewith tags:

Thanks, I can recreate the issue with these tags.

p.s. I notice it looks like you are using KDE/Plasma - same here

[slartibartfast]

I've looked at the changed 3.0.3 and 3.1.0 and the only thing I can see that would affect the CPU load on the backend is that I ask for more meta-data back from tracks - this is to show composers, conductors, etc. The extra metadata requested is Genre, samplesize, extra artist IDs (for composer, etc). Perhaps fetching these extra IDs causes pCP issues? Not sure why. They are not part of the query, they jsut control what data LMS should send back for a track that matches the query.

Same on a Pi4 running Bullseye. Playback was interrupted for a while during a search.

[cpd73]

It's not on iOS, it's Chromium on Linux. Herewith tags

This might partially be an LMS issue. Material asks LMS for the list of composers. In the status message (used for the queue) this is returned as "A,B" (no space) - and this is how Material expects such lists to be composed (so that "A,X, Y and Z" splits into "A" and "X, Y and Z"). But when listing the album tracks LMS returns the composer as "A, B" (so Material does not split). Now if composer==artist then Material does not show this, to prevent duplication. So, in the queue case the fist composer = artist, so is not shown, but in browse composer!=artist so is shown. (Hope that makes sense).

I guess in the case of multiple composers Material should handle the others, as opposed to just looking at the first - hence its only a partial LMS issue.

mherger Can you look into this?