Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Originally posted by SlimChances
    it did not require any action my part, it just updated on it's own through autoupdates
    That's puzzling to me but, then again, a lot of things are. ;-)

    The update still hasn't hit the servers yet but should any time now. In the meantime, I installed it from the zip file and the problem is indeed fixed.

    A thought just occurred to me. Do you have an entry in "Additional Repositories" that would pick up the new version directly from Craig's Github page? That would explain things.

    UPDATE: It just hit the server so everyone should be getting updated shortly.
    Last edited by SamY; 2022-07-17, 19:42.
    Sam

    Comment


    • Originally posted by SamY
      That's puzzling to me but, then again, a lot of things are. ;-)

      The update still hasn't hit the servers yet but should any time now. In the meantime, I installed it from the zip file and the problem is indeed fixed.

      A thought just occurred to me. Do you have an entry in "Additional Repositories" that would pick up the new version directly from Craig's Github page? That would explain things.

      UPDATE: It just hit the server so everyone should be getting updated shortly.
      Yup, the repository used to be in the first post.


      Sent from my Pixel 3a using Tapatalk
      Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
      Bedroom: Radio
      Bathroom: Radio

      Comment


      • Originally posted by SamY
        That's puzzling to me but, then again, a lot of things are. ;-)

        The update still hasn't hit the servers yet but should any time now. In the meantime, I installed it from the zip file and the problem is indeed fixed.

        A thought just occurred to me. Do you have an entry in "Additional Repositories" that would pick up the new version directly from Craig's Github page? That would explain things.

        UPDATE: It just hit the server so everyone should be getting updated shortly.
        Yes you're right I do have it in 3rd party unsupported repositories
        Last edited by SlimChances; 2022-07-17, 19:55.
        Logitech Media Server Version: 8.4.0 - 1678519305 @ Sat 11 Mar 2023 08:54:37 AM CET
        Operating system: Debian - EN - utf8
        Platform Architecture: x86_64-linux
        Perl Version: 5.34.0 - x86_64-linux-gnu-thread-multi
        Database Version: DBD::SQLite 1.58 (sqlite 3.22.0)​

        Comment


        • Update has appeared via regular plugins route. Everything seems back to as it was. I don’t use Alarms so can’t comment on that implementation

          Edit. I did have to clear Safari cache
          Last edited by d6jg; 2022-07-17, 21:39.
          Jim



          VB2.4 storage QNAP TS419p (NFS)
          Living Room Joggler & Pi4/Khadas -> Onkyo TXNR686 -> Celestion F20s
          Office Joggler & Pi3 -> Denon RCD N8 -> Celestion F10s
          Dining Room SB Radio
          Bedroom (Bedside) Pi Zero+DAC ->ToppingTP21 ->AKG Headphones
          Bedroom (TV) & Bathroom SB Touch ->Denon AVR ->Mordaunt Short M10s + Kef ceiling speakers
          Guest Room Joggler > Topping Amp -> Wharfedale Modus Cubes

          Comment


          • Originally posted by cpd73
            Update, should be handled now. Clickable items don't wrap. But if this message is sent as text it should now wrap.
            Hey, Craig. You may recall this change you made during v2.10.0 development that allowed menu text messages to wrap and I remember testing and verifying that it worked with the Denon menus. However, the change does not appear to be in the current v2.10.1 release as the messages are again being truncated. Was this something that slipped through the cracks or was it intentionally left out?
            Sam

            Comment


            • Originally posted by SlimChances
              Yes you're right I do have it in 3rd party unsupported repositories
              As opposed to unreported suppositories.
              Sam

              Comment


              • Originally posted by SamY
                Hey, Craig. You may recall this change you made during v2.10.0 development that allowed menu text messages to wrap and I remember testing and verifying that it worked with the Denon menus. However, the change does not appear to be in the current v2.10.1 release as the messages are again being truncated. Was this something that slipped through the cracks or was it intentionally left out?
                Yeah, confirmed. Will fix for 2.10.2 to make sure its fixed for your scenario, can you send me the JSON RESP message that corresponds to the incorrect display? See my sig for details. This way I can hard-code that into my dev version, and see the actual results.
                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


                • Have just seen this post. I saw another comment about clearing the cache and tried it myself and all seems to be working as expected now, thanks.

                  Originally posted by slartibartfast
                  Did you clear the cache?

                  Sent from my Pixel 3a using Tapatalk

                  Comment


                  • Originally posted by cpd73
                    Yeah, confirmed. Will fix for 2.10.2 to make sure its fixed for your scenario, can you send me the JSON RESP message that corresponds to the incorrect display? See my sig for details. This way I can hard-code that into my dev version, and see the actual results.
                    Here it is. For testing purposes, I expanded the message so that it would be sure to wrap:

                    Code:
                    [2:40:46 PM] JSON RESP: {"result":{"offset":0,"item_loop":[{"text":"AVR menu not active for this player abcde fghij klmnop qrst uvwxyz","icon":"plugins/DenonAvpControl/html/images/denon_control.png"}],"count":1},"id":0,"method":"slim.request","params":["cc:cc:4c:51:85:cb",["avpTop","0","300"]]}
                    These messages are also used (and truncated) in the submenus. Here is one from the Reference Level menu:

                    Code:
                    [2:49:36 PM] JSON RESP: {"id":0,"params":["b8:26:eb:c1:71:f0",["avpRefLvl","0",300,"menu:avpRefLvl"]],"method":"slim.request","result":{"offset":0,"item_loop":[{"text":"Unavailable when in Direct or Pure Direct modes."}],"count":1}}
                    You indicated previously that you would ignore the 'icon' attribute used in the first example, which is fine. However, I would like to keep it there if possible as it is displayed by other clients.

                    Thanks.
                    Sam

                    Comment


                    • Originally posted by SamY
                      Here it is. For testing purposes, I expanded the message so that it would be sure to wrap:
                      Thanks, and this is now fixed for 2.10.2

                      Originally posted by SamY
                      You indicated previously that you would ignore the 'icon' attribute used in the first example, which is fine. However, I would like to keep it there if possible as it is displayed by other clients.
                      Well using an icon gives even less room for the text, plus what does it actually provide? Of your two examples only the first ("not supported here") has an icon, and the user already knows they entered this plugin so showing its icon again does not add much.
                      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 cpd73
                        Thanks, and this is now fixed for 2.10.2
                        Thanks!

                        Well using an icon gives even less room for the text, plus what does it actually provide? Of your two examples only the first ("not supported here") has an icon, and the user already knows they entered this plugin so showing its icon again does not add much.
                        Good point. I may go ahead and remove it in the next release.
                        Sam

                        Comment


                        • APK Screensaver

                          I am having a new problem with the screensaver feature in Material, Github: "Adjust screensaver text positions." Parent:374a98, which was pushed immediately after the release of 2.10.1.

                          The screensaver looks OK in various browsers such as Chrome, Brave, and Fully Kiosk, but it does not render well in the lms-material-app, tested in versions 2.0 and 2.1; the Time display is now too large and spills out over the edges on both sides. In my apk setup, I am having a conflict between the Interface settings->Font size and Application->Scale. It looks like the rendering for Time in the screensaver has gotten much larger.

                          I have now set Interface Font size to Regular, and I set the APK Application Scale to something that makes everything minus the screensaver look good, and for now I will just live with the over-sized screensaver Time display.

                          I am using a Pixel 3a, Android 12, and looking at Plugins/MaterialSkin/HTML/material/html/css/style.css, I figure I am now getting a screensaver font size of 64px for Time instead of 48px, which is probably what I used to get, although I don't understand why?
                          Living Room: SB Touch + DIY PSU > CI Audio VDA.2 DAC + VAC.1 PSU > VRX.1 cables > Emotiva XSP-1 Gen 2 preamp + XPA-DR2 amp > Blue Jeans cables > B&W 804 speakers
                          Laptop: System76 Galago + Ubuntu 18.04 + Squeezelite + Epiphany/Material Skin > Emotiva Little Ego DAC > Grado PS500 headphones
                          Bedroom: RPi Zero W + Squeezelite > miniBOSS DAC HAT > Bose SoundLink Revolve
                          Phone: Pixel 6a + Termux/Squeezelite + Material APK > Senn IE80 earbuds
                          Server: System76 Meerkat + Pop!_OS 22.04 + LMS 8.4

                          Comment


                          • Originally posted by Ron F.
                            I am having a new problem with the screensaver feature in Material, Github: "Adjust screensaver text positions." Parent:374a98, which was pushed immediately after the release of 2.10.1.

                            The screensaver looks OK in various browsers such as Chrome, Brave, and Fully Kiosk, but it does not render well in the lms-material-app, tested in versions 2.0 and 2.1; the Time display is now too large and spills out over the edges on both sides. In my apk setup, I am having a conflict between the Interface settings->Font size and Application->Scale. It looks like the rendering for Time in the screensaver has gotten much larger.

                            I have now set Interface Font size to Regular, and I set the APK Application Scale to something that makes everything minus the screensaver look good, and for now I will just live with the over-sized screensaver Time display.

                            I am using a Pixel 3a, Android 12, and looking at Plugins/MaterialSkin/HTML/material/html/css/style.css, I figure I am now getting a screensaver font size of 64px for Time instead of 48px, which is probably what I used to get, although I don't understand why?
                            It seems to me that with zoom set to near maximum the screensaver font is much larger in landscape than portrait mode. Is it landscape mode where you see the issue? Click image for larger version

Name:	Screenshot_20220720-072447.jpg
Views:	1
Size:	67.3 KB
ID:	1575486

                            Sent from my Pixel 3a using Tapatalk
                            Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
                            Bedroom: Radio
                            Bathroom: Radio

                            Comment


                            • Hi,

                              not sure if this is really a Material issue, but I noticed it after the latest update (2.10.1), it worked before than. Maybe Michael who maintains the Qobuz plugin is reading along too in case...

                              Qobuz offers booklets to be viewed, however since the latest (or previous version) of Material the availability of the booklet is still shown as before but it is no longer shown as a link/url to the PDF on the Qobuz server.

                              Click image for larger version

Name:	Schermafbeelding 2022-07-20 om 10.43.35.jpg
Views:	1
Size:	168.8 KB
ID:	1575487

                              Click image for larger version

Name:	Schermafbeelding 2022-07-20 om 10.44.30.png
Views:	1
Size:	105.5 KB
ID:	1575488
                              Last edited by hsmeets; 2022-07-20, 09:52. Reason: Added version of Material
                              does the all-black SB sound better than the white SB?

                              Comment


                              • Using Material on FiiO M6 - display problem

                                The FiiO M6 is a mini android music player using a modified version of android 7.

                                Using LMS apk gives a now playing screen which doesn't display the metadata image when the track changes - just the generic disc image.
                                Squeezer shows the track images.

                                (see attached pics - sorry for camera quality, but I can't discover how to take screenshots on the M6)

                                I may be mistaken but I think this may be a recent change following the updates to accommodate the alarm displays.

                                All other apps on the M6 work without issues.
                                Attached Files
                                ------------------------------------------------------------------------------------

                                Comment

                                Working...
                                X
                                😀
                                🥰
                                🤢
                                😎
                                😡
                                👍
                                👎