Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Originally posted by d6jg
    What I am saying is that I think that within Material there needs to be a way of selecting which Plugins you want to install rather than an all or nothing.
    This is not an LMS issue, its Material that is expliclity updating all plugins - the code could be updated to have a checkbox, but I decided for simplicity not to add these and just update all.

    As slartibartfast mentioned, you can use server settings to update individual plugins.

    [Edit] I think the original update code was before server settings was integrated. Perhaps for 3.2.0 I'll change "Update plugins" to "Update all plugins", and then provide a clickable link to open the server setting's plugins page to allow more fine-grained control.
    Last edited by cpd73; 2023-02-10, 13:34.
    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

      ....... Perhaps for 3.2.0 I'll change "Update plugins" to "Update all plugins", and then provide a clickable link to open the server setting's plugins page to allow more fine-grained control.
      I think that would be a good idea.

      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


      • Wondering whether you'd consider adding capability Material to treat the phones and tablet it's running on as a local player. As it is it's great for playback to a LMS endpoint but can't play back to the phone or tablet it's running on meaning it can't be used whilst commuting.
        puddletag - now packaged in most Linux distributions.

        Comment


        • Originally posted by audiomuze
          Wondering whether you'd consider adding capability Material to treat the phones and tablet it's running on as a local player. As it is it's great for playback to a LMS endpoint but can't play back to the phone or tablet it's running on meaning it can't be used whilst commuting.
          2 apps for Android that make your phone/tablet an LMS endpoint.



          And for IOS.
          https://apps.apple.com/gb/app/ipeng/id767266886 (in app purchase).
          Server - LMS 8.4.0 RPi4B 4GB/NanoSound ONE case/pCP 8.1.0 - 75K library, playlists & LMS cache on Sata SSD (ntfs)

          Lounge - DAC32 - AudioEngine B2
          Office - RPi 3B+/HiFiBerry DAC HAT/RPi screen - Edifier D12
          Bedroom - Echo Show 8

          Spares - 1xSB Touch, 1xSB3, 4xRPi, AVI DM5 speakers

          Comment


          • Originally posted by audiomuze
            Wondering whether you'd consider adding capability Material to treat the phones and tablet it's running on as a local player. As it is it's great for playback to a LMS endpoint but can't play back to the phone or tablet it's running on meaning it can't be used whilst commuting.
            The skin itself can no do this, as its just a HTML web app. The Android APK, however, can be configured to run SB Player, SqueezePlayer, or Squeezelite (via Termux)
            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


            • Craig, I have a question if you would be so kind. I am having an issue with Radio Now Playing plugin that I am trying to understand. I am sure that it is something goofy with my system, and not the plugin. I don't want to bother Paul with it anymore until I get something tangible. I may just rebuild my LMS.

              What happens is the metadata (song/artist/art) will get stuck on a previous song/station ID, and this can go on for quite some time. I see it on a controller or touch UI.

              However, if I wake up my phone running the material apk, Within 2-5 seconds, it fixes the issue. I have not tried this with the default LMS UI via browser, but will.

              My question, does material do some sort of query to LMS upon waking that might cause LMS to refresh of sorts?

              Jim

              Comment


              • Originally posted by Redrum
                My question, does material do some sort of query to LMS upon waking that might cause LMS to refresh of sorts?
                The only thing Material will do is refresh the status of the current player (it send a status JSONRPC request). Perhaps this forces LMS to refresh?
                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

                  The only thing Material will do is refresh the status of the current player (it send a status JSONRPC request). Perhaps this forces LMS to refresh?
                  Maybe, thank you for the info, this might help. I'll dig in a bit more

                  Jim

                  Comment


                  • Can you make search always accessible? Having to hit home first is almost more than mildly annoying. Thanks.

                    Comment


                    • Originally posted by spacecase-25
                      Can you make search always accessible? Having to hit home first is almost more than mildly annoying. Thanks.
                      Not keen on this if you are suggesting that another item gets added to the main screens.
                      ------------------------------------------------------------------------------------

                      Comment


                      • If you are browsing somewhere other than My Music, and you want to start a search, what would you expect to be searched? The category you are currently viewing, or My Music?

                        Also it appears to me that if you are in a sub-category of My Music, it is not necessary to go all the way to the home screen in order to start a search. The top level of My Music will suffice.
                        Usually running latest beta LMS nightly on Raspberry Pi OS with virtual players. Occasionally using SB Radio, Boom or Classic.

                        Comment


                        • Originally posted by RobbH
                          If you are browsing somewhere other than My Music, and you want to start a search, what would you expect to be searched? The category you are currently viewing, or My Music?

                          Also it appears to me that if you are in a sub-category of My Music, it is not necessary to go all the way to the home screen in order to start a search. The top level of My Music will suffice.
                          global search, just as it functions now. I would just like a button on the tool bar to be present when layers deep in browsing the library

                          Comment


                          • Hi Craig

                            How often does Material refresh the status of the current player. I have an issue which I see quite frequently where the Now Playing does not update and the only way to force this is to click on the Volume button which then refreshes the screen.

                            Originally posted by cpd73

                            The only thing Material will do is refresh the status of the current player (it send a status JSONRPC request). Perhaps this forces LMS to refresh?

                            Comment


                            • Originally posted by Shozzer
                              How often does Material refresh the status of the current player
                              At the start and end of a track Material polls quite frequently (every second or 2 for the first/last 5ish seconds), and then every 10 seconds. However, update should come via notifications over cometd from LMS.
                              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


                              • Thanks, I will keep an eye on my set up.

                                Originally posted by cpd73

                                At the start and end of a track Material polls quite frequently (every second or 2 for the first/last 5ish seconds), and then every 10 seconds. However, update should come via notifications over cometd from LMS.

                                Comment

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