Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Originally posted by ModelCitizen
    My keyboard does not pop up either so I don't think I can do that.

    Anyway. I've added it as an issue at Github now so if Craig is inclined to correct it I am sure he will.
    So if your keyboard doesn't pop up you can't search for anything. That doesn't seem right.

    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 MrC
      Question....

      Would it be possible to have a quick control button, perhaps near the A-Z "Sort by", which could toggle On / Off the display of integrated media?

      I love the Spotty library integration, but am now finding it difficult to find my own local media rips, as my saved Spotty songs / albums in the past few years have now far exceed purchases during the same time period. So a quick Show/Hide would be great.
      You can probably do this yourself, using Advanced Search to search by path, and create a library view for Local Only files and another for Online Only files.
      Usually running latest beta LMS nightly on Raspberry Pi OS with virtual players. Occasionally using SB Radio, Boom or Classic.

      Comment


      • LMS Material not showing battery voltage on Information tab

        I have two players (SqueezeAMP and ESP Muse Luxe) that report its battery voltage to LMS. The default LMS skin shows the battery voltage on the Information tab, but LMS Material does not.

        For example, default LMS UI shows following Player Information for my ESP Muse player:

        ESP Muse
        Player Model: SqueezeESP32
        Player Type: squeezeesp32
        Firmware: v1.0-1012-16
        Player IP Address: 192.168.0.106
        Player MAC Address: xx:xx:xx:xx:xx:xx
        Wireless Signal Strength: 76%
        Voltage: 4.03

        In LMS Material the last line is missing. Would it be possible to also show the Voltage in Material?
        Last edited by CJS; 2022-01-29, 11:55.
        | LMS 8.3.2 on Linux Mint 21.2 | Squeezebox Boom | RPi0W + pCP 8.2.0 + HiFiBerry DAC Zero | ESP Muse Luxe |

        Comment


        • Originally posted by CJS
          I have two players (SqueezeAMP and ESP Muse Luxe) that report its battery voltage to LMS. The default LMS skin shows the battery voltage on the Information tab, but LMS Material does not.
          I have no such players, but have updated Material to attempt to add this - but cannot confirm. Will be in next release.
          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
            I have no such players, but have updated Material to attempt to add this - but cannot confirm. Will be in next release.
            Thanks! I will check if the voltage is shown after next release is available.
            | LMS 8.3.2 on Linux Mint 21.2 | Squeezebox Boom | RPi0W + pCP 8.2.0 + HiFiBerry DAC Zero | ESP Muse Luxe |

            Comment


            • Continuous logging from material skin

              I run a script that's a "listener" for LMS events, using the "listen 1" CLI command. (I have some home automation things that happen in response to some LMS events.)

              "Lately" (and I'm not sure how long that is), I've been getting repetitive messages from material-skin:
              Code:
              $ telnet slimserver 9090
              Trying 192.168.111.3...
              Connected to slimserver
              Escape character is '^]'.
              listen 1
              material-skin plugins-status needs_restart%3A0 downloading%3A0
              material-skin plugins-status needs_restart%3A0 downloading%3A0
              material-skin plugins-status needs_restart%3A0 downloading%3A0
              material-skin plugins-status needs_restart%3A0 downloading%3A0
              material-skin plugins-status needs_restart%3A0 downloading%3A0
              material-skin plugins-status needs_restart%3A0 downloading%3A0
              material-skin plugins-status needs_restart%3A0 downloading%3A0
              material-skin plugins-status needs_restart%3A0 downloading%3A0
              material-skin plugins-status needs_restart%3A0 downloading%3A0
              ^]
              telnet> quit
              Connection closed.
              Those messages come out every 2 seconds.

              They're not a huge problem, but they sure clutter my logs. Any way to stop them?

              Server version is:
              Code:
              Version: 8.2.0 - 1627922070 @ Tue Aug 3 11:37:35 CEST 2021
              Plugins:
              Code:
              Plugins
              
              Additional Browse Modes 1.0
              Classical.com 1.0
              Full text search 1.0.0
              Live Music Archive 1.0
              Material Skin 2.8.4
              Network Test 1.0
              Online Music Library Integration 1.0
              Pandora 3.0
              PowerSave 7.4.1
              Radio 1.0
              Rescan Music Library 1.0

              Comment


              • Originally posted by pgf
                "Lately" (and I'm not sure how long that is), I've been getting repetitive messages from material-skin:
                These are when Material's 'Information' dialog is open, it polls to see if there are any plugin updates.
                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


                • Ha! I guess that tells me how "Lately". Like, since I opened the dialog.

                  Thanks. False alarm, clearly.

                  paul

                  Comment


                  • Qobuz Search - Grid view issue

                    Using LMS 8.3 / Material master.

                    Browse view: when Grid view is enabled and the Qobuz search field is used, after hitting "OK" the Browse display remains unchanged and the following error is posted:

                    browse-functions.js?r=GIT-da4d2e148:488 Uncaught (in promise) TypeError: view.search is not a function
                    at browse-functions.js?r=GIT-da4d2e148:488
                    (anonymous) @ browse-functions.js?r=GIT-da4d2e148:488
                    Promise.then (async)
                    browseClick @ browse-functions.js?r=GIT-da4d2e148:485
                    click @ browse-page.js?r=GIT-da4d2e148:661
                    click @ VM976:3
                    He @ vue.min.js?r=2.6.11:6
                    n @ vue.min.js?r=2.6.11:6
                    Yr.o._wrapper @ vue.min.js?r=2.6.11:6


                    If Grid view is not enabled, everything works perfectly. I note also that this Grid issue does not occur with the Spotty plugin, I only see it with Qobuz. I don't know when this issue with displaying Qobuz search results began; I stumbled into it today when searching for "Neil Young!"
                    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.
                      Browse view: when Grid view is enabled and the Qobuz search field is used, after hitting "OK" the Browse display remains unchanged
                      Caused by changes to fix missing context menu. Should be fixed in master now.
                      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
                        Yes, I've seen the github issue (thanks, BTW) - and will try to fix.
                        Thanks very much indeed Craig!

                        To the others...

                        My keyboard does pop up, just no so readily for Material Skin. I have a very *hit Xiaomi A2 phone that seems to have quickly developed memory issues since it's Android One program ended. It's most likely due to that. In fact the keyboard will pop up, but it's delayed and only works if I very quickly tap the field.
                        Take care of your tongue. It is in a wet place and can easily slip.

                        Lounge: Naim NDX with Touch as controller, Naim NAP 180, NAC 82, NAPSC, HiCap, Shahinian Arc speakers
                        Kitchen/outside: Chromecast audio, Azatom iBigBoy 2 (500W)
                        And... SB+, radios & tons of Chromecasts... all run from LMS and controlled via Material Skin on any nearby device and a couple of Touchs.

                        Comment


                        • Originally posted by ModelCitizen
                          Thanks very much indeed Craig!

                          To the others...

                          My keyboard does pop up, just no so readily for Material Skin. I have a very *hit Xiaomi A2 phone that seems to have quickly developed memory issues since it's Android One program ended. It's most likely due to that. In fact the keyboard will pop up, but it's delayed and only works if I very quickly tap the field.
                          Now you mention it I am pretty sure I have seen occasions where my keyboard on a Pixel 3a doesn't always appear when I expect it to. Rare but it does happen.

                          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 slartibartfast
                            Now you mention it I am pretty sure I have seen occasions where my keyboard on a Pixel 3a doesn't always appear when I expect it to. Rare but it does happen.
                            Having had enough of cheap phones I hope to upgrade to a Pixel 6 when I can't abide the Xiaomi any longer. Just stretching it out in the hope that used prices decrease soon.
                            Take care of your tongue. It is in a wet place and can easily slip.

                            Lounge: Naim NDX with Touch as controller, Naim NAP 180, NAC 82, NAPSC, HiCap, Shahinian Arc speakers
                            Kitchen/outside: Chromecast audio, Azatom iBigBoy 2 (500W)
                            And... SB+, radios & tons of Chromecasts... all run from LMS and controlled via Material Skin on any nearby device and a couple of Touchs.

                            Comment


                            • Originally posted by ModelCitizen
                              Thanks very much indeed Craig!

                              To the others...

                              My keyboard does pop up, just no so readily for Material Skin. I have a very *hit Xiaomi A2 phone that seems to have quickly developed memory issues since it's Android One program ended. It's most likely due to that. In fact the keyboard will pop up, but it's delayed and only works if I very quickly tap the field.
                              Hmm actually I have also seen that behaviour with my old Xperia phone at least few times. Didn't think it was specifically in material skin but maybe it was
                              3x Squeezebox Touch, 4x Squeezebox Radio, Squeezelite (RPi 3B with HiFiBerry DAC+Pro on OSMC), Material Skin Apk, Squeeze Commander, Logitech Media Server Version: 8.2.0 with Material Skin (Docker in DS218+)

                              Comment


                              • Qobuz album as favorite ?

                                I just move from Tidal to Qobuz.
                                Is it possible to save an album as favorite, i can only save à Qobuz track in favorite.
                                Thanks

                                Comment

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