Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Originally posted by garym
    Are you using the new Material skin plugin from today. Ver 3.1.3
    Have you cleared the cache? It works OK for me.
    Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
    Bedroom: Radio
    Bathroom: Radio

    Comment


    • clear cache on web browser or on LMS (running on rPi)? I rebooted rPi running LMS and cleared cache on firefox browser. Also tried on Chrome as browser (which I never use for LMS access), and get spinning when clicking on YEARS. But all other items are very fast (genres, album artists, albums, etc.)
      Home: Pi4B-8GB/pCP8.2.x/4TB>LMS 8.3.x>Transporter, Touch, Boom, Radio (all ethernet)
      Cottage: rPi4B-4GB/pCP8.2.x/4TB>LMS 8.3.x>Touch>Benchmark DAC I, Boom, Radio w/Battery (Radio WIFI)
      Office: Win11(64)>foobar2000
      The Wild: rPi3B+/pCP7.x/4TB>LMS 8.1.x>hifiberry Dac+Pro (LMS & Squeezelite)
      Controllers: iPhone14Pro & iPadAir5 (iPeng), CONTROLLER, Material Skin, or SqueezePlay 7.8 on Win10(64)
      Files: Ripping: dBpoweramp > FLAC; Post-rip: mp3tag, PerfectTunes, TuneFusion; Streaming: Spotify

      Comment


      • Originally posted by garym
        clear cache on web browser or on LMS (running on rPi)? I rebooted rPi running LMS and cleared cache on firefox browser. Also tried on Chrome as browser (which I never use for LMS access), and get spinning when clicking on YEARS. But all other items are very fast (genres, album artists, albums, etc.)
        Is this on a PC. I always assume a phone is being used. I tried on Firefox on Windows 10 and see the same issue. Android works perfectly.
        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

          Is this on a PC. I always assume a phone is being used. I tried on Firefox on Windows 10 and see the same issue. Android works perfectly.
          yes, on a windows PC. Just tried Material on my iPhone, and all works just fine. So something related to running on my Windows 10 computer accessing Material via Firefox or Chrome.
          Home: Pi4B-8GB/pCP8.2.x/4TB>LMS 8.3.x>Transporter, Touch, Boom, Radio (all ethernet)
          Cottage: rPi4B-4GB/pCP8.2.x/4TB>LMS 8.3.x>Touch>Benchmark DAC I, Boom, Radio w/Battery (Radio WIFI)
          Office: Win11(64)>foobar2000
          The Wild: rPi3B+/pCP7.x/4TB>LMS 8.1.x>hifiberry Dac+Pro (LMS & Squeezelite)
          Controllers: iPhone14Pro & iPadAir5 (iPeng), CONTROLLER, Material Skin, or SqueezePlay 7.8 on Win10(64)
          Files: Ripping: dBpoweramp > FLAC; Post-rip: mp3tag, PerfectTunes, TuneFusion; Streaming: Spotify

          Comment


          • Originally posted by garym

            yes, on a windows PC. Just tried Material on my iPhone, and all works just fine. So something related to running on my Windows 10 computer accessing Material via Firefox or Chrome.
            I can’t try this at the moment - no PC switched on but suggest try on PC with mobile display rather than desktop
            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 d6jg

              I can’t try this at the moment - no PC switched on but suggest try on PC with mobile display rather than desktop
              I tried mobile mode on PC and it suffered from the same issue.
              Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
              Bedroom: Radio
              Bathroom: Radio

              Comment


              • Originally posted by garym
                Are you using the new Material skin plugin from today. Ver 3.1.3
                Yes, but I'm using the Android version. It now appears that this is a Windows-only issue.
                Sam

                Comment


                • Originally posted by SamY

                  Yes, but I'm using the Android version. It now appears that this is a Windows-only issue.
                  It's not Windows-only, but non-touch only. It's due to some code to remove the HTML that was appearing in tooltips, etc. This HTML is to provide links to artists, albums, etc - and these are not provided for touch-devices, hence not affected by this bug.

                  Fixed for 3.1.4
                  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

                    It's not Windows-only, but non-touch only. It's due to some code to remove the HTML that was appearing in tooltips, etc. This HTML is to provide links to artists, albums, etc - and these are not provided for touch-devices, hence not affected by this bug.

                    Fixed for 3.1.4
                    Thanks for the fast turnaround on this marvelous piece of software!
                    Home: Pi4B-8GB/pCP8.2.x/4TB>LMS 8.3.x>Transporter, Touch, Boom, Radio (all ethernet)
                    Cottage: rPi4B-4GB/pCP8.2.x/4TB>LMS 8.3.x>Touch>Benchmark DAC I, Boom, Radio w/Battery (Radio WIFI)
                    Office: Win11(64)>foobar2000
                    The Wild: rPi3B+/pCP7.x/4TB>LMS 8.1.x>hifiberry Dac+Pro (LMS & Squeezelite)
                    Controllers: iPhone14Pro & iPadAir5 (iPeng), CONTROLLER, Material Skin, or SqueezePlay 7.8 on Win10(64)
                    Files: Ripping: dBpoweramp > FLAC; Post-rip: mp3tag, PerfectTunes, TuneFusion; Streaming: Spotify

                    Comment


                    • Hello, I have a few questions, primarily for the developer (cpd73) of this great plugin, but also for anyone who can provide information on my questions, as I myself can't stop tinkering with my version of the Qobuz plugin from time to time.

                      1.) It's about the function 'Toggle View' which can switch between a list view with small icons and a gallery view. Here I think it would be nice if each view would remember the set value. It is currently a global switch (although the browser cache sometimes gives the impression that this is not the case). For example, if you select the gallery view in the album view and then go back to the menu, the menus will soon also be displayed in the gallery view, all icons will then be displayed as huge images, which looks stupid to my taste.
                      I've now tried to find out where this change of view happens in the code, but unfortunately I couldn't find anything. Either I'm looking for the wrong stuff or maybe it's a feature of the skin.
                      If it is a function of the skin, I would like to put it out there as a suggestion to remember the personal selected view setting for each view. Or, if that is easier to implement, that you differentiate between menu views and views with images from the image cache and then set the desired view option in the settings for these two view types, which is then always selected when these view types are called, temporary switching "Toggle View" then remains unaffected.

                      2.) In Material Skin there is a menu button (three vertical dots) in the top right corner of the header. This menu contains the settings, help, etc. and sometimes other menu items depending on the context.
                      What does the plugin developer have to code in order to add a menu item permanently or context-dependently to this menu?
                      Is that even possible?

                      I hope I was able to explain my request clearly. It would be great if I could get helpful information and tips on this.​

                      Comment


                      • Originally posted by sveninndh
                        1.) It's about the function 'Toggle View' which can switch between a list view with small icons and a gallery view.
                        It's not global. However it is set per-command. e.g. "artists", "albums", "apps", "qobuz", etc. So, for "quobuz" there is one setting. The issue with having it per unique list is that its difficult (impossible?) to know if (e.g.) qobuz is listing artists, albums, tracks, etc. Saving a grid/list setting for each level then becomes unfeasible - as don't want to store a setting for each album, etc.

                        Originally posted by sveninndh
                        2.) In Material Skin there is a menu button (three vertical dots) in the top right corner of the header. This menu contains the settings, help, etc. and sometimes other menu items depending on the context.
                        What does the plugin developer have to code in order to add a menu item permanently or context-dependently to this menu?
                        Is that even possible?
                        There is no current method. Also, the items are only placed into this menu fromthe browse view in mobile layout if the current view is "slim". e.g. The toggle grid/list icon is quite often moved into this menu, but this never happens for desktop layout.

                        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

                          It's not global. However it is set per-command. e.g. "artists", "albums", "apps", "qobuz", etc. So, for "quobuz" there is one setting. The issue with having it per unique list is that its difficult (impossible?) to know if (e.g.) qobuz is listing artists, albums, tracks, etc. Saving a grid/list setting for each level then becomes unfeasible - as don't want to store a setting for each album, etc.
                          Thank you, I think I understand that so far.
                          But there must be some place where you can read the current status of the grid/list setting.
                          How does Material-Skin know if it should display the current view as a grid or as a list?
                          Isn't there a function or a command that Materil-Skin calls to query the grid/list status of the current view?

                          There is no current method. Also, the items are only placed into this menu from the browse view in mobile layout if the current view is "slim". e.g. The toggle grid/list icon is quite often moved into this menu, but this never happens for desktop layout.
                          I think we may have misunderstood each other. My second question has nothing to do with the Grid/List icon.
                          It's all about the menu on the top right.
                          In addition to the player menu on the left, this is the only menu that is always present (regardless of whether it is in the mobile or desktop view) and I would like to place a separate menu item there that should then execute some command.

                          Comment


                          • Originally posted by sveninndh
                            But there must be some place where you can read the current status of the grid/list setting.
                            Material stores the setting in your browser's local storage. There yoiu will find items sic as "lms-material::albums-grid"

                            Originally posted by sveninndh
                            I think we may have misunderstood each other. My second question has nothing to do with the Grid/List icon.
                            I know, I used that as an example of an item that is placed there - and when/how this happens.

                            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


                            • Blank or only partially filled Browse pane. This is recent behavior:
                              When bringing up Material in a browser, (Vivaldi, Brave, or Firefox,) or using Melodeon, or the Android APK, the Browse pane is either blank or only contains a few items. If I toggle the Grid View or hit the Search icon, the pane is then populated correctly and works going forward. This behavior began not long ago, so I might try reverting back to an earlier version of LMS / Material to see what happens. Restarting LMS, dumping cache, doesn't make any difference. I note with some amusement, that the one browser where this weird behavior does not occur, is when I am using trusty old Epiphany! It works fine. Yes, I thought that would get a laugh. I assume since Epiphany is by far the slowest of all browsers, that this must be a race condition of some kind.

                              Using slimserver public/8.4 and lms-material 3.2, both cloned from Github.

                              Below are some of the error messages that I caught using developer tools in Firefox, when the page is first opened or refreshed:

                              utils.js:137:17
                              ReferenceError: stripLinkTags is not defined
                              VueJS 13
                              beforeMount http://192.168.*.*:9000/material/htm...r=1.5.24trim:6
                              VueJS 63
                              <anonymous> http://192.168.*.*:9000/material/htm...T-a9f3bc231:11
                              vue.min.js:6:11752
                              Source map error: Error: request failed with status 404
                              Resource URL: http://192.168.*.*:9000/material/htm...in.js?r=0.19.2
                              Source Map URL: axios.min.map

                              [8:54:36 PM] JSON REQ: ["",["material-skin","get-notifs"]] utils.js:137:17
                              Source map error: Error: request failed with status 404
                              Resource URL: http://192.168.*.*:9000/material/htm...js?r=1.0.10mod
                              Source Map URL: vue-virtual-scroller.min.js.map​
                              Last edited by Ron F.; 2023-02-06, 21:41.
                              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.
                                ReferenceError: stripLinkTags is not defined
                                Is this only with the 3.2 branch? Is master ok?
                                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

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