Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Now playing looking awesome on desktop device!! Thanks for creating this view.

    But... Not so much when using a mobile device. Would the desktop now-playing layout also be possible on a mobile device?

    Edit. Also changing windows size on desktop give some layout issues like overlapping song info on art. Fullscreen landscape desktop all is perfect.
    Last edited by edwin2006; 2019-07-21, 14:49.
    SqueezeBoxes: 1x Transporter (Living room) 1x SB2 (shed), 1x Radio (Kitchen), 1x Boom (Dining room), 1x piCorePlayer (jacuzzi), 1x piCorePlayer (Garden) 1x OSMC + Squeezelite (Movie room), 1x Touch (Study 2), few spare unit's (SB2, SB3, Boom, Touch)
    Server: LMS on Pi3B+ 8.1.2 on PcP 7.0.1
    Network: Draytek, Netgear Smart Switch 24p, Ubiquiti PoE, 3x Ubiquity

    Comment


    • Originally posted by d6jg
      Might be worth a Poll - what is the first menu item you use?
      My GoTo's, in order:

      1. Album Artists (I use ArtistSort tag to go by last names)
      2. New Music
      3. Compilations (Soon to be replaced by Spotty)

      Hope this helps the decision making. Either way, thanks for Material Skin!

      Comment


      • 1. New Albums (Doesn't function now - a component of Custom Browse)
        2. Albums (Doesn't function - a component of Custom Browse)
        3. Music Folder

        reason I use Custom Browse for these choices is that with MultiLibrary (Erland's plugin) I am able to select either from my FLAC or MP3 libraries and can keep them separate
        Last edited by SlimChances; 2019-07-21, 19:53.
        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


        • Qobuz Search

          I'm unable to search Qobuz from the material skin. i'm using a Synology DS216J NAS, and LMS 7.9.2. i've tried Chrome and Safari and neither works. click the search option in the Qobuz plugin and nothing happens. reverting to the default skin works fine.

          it doesn't work on Mobile either.
          --
          4 TB Drobo-->FW 800-->mac mini-->Ethernet
          Transporter--> Wireworld Eclipse 6 coax-->Meridian G61
          G61--> Nordost Red Dawn-->Primare 30.3
          Primare-->Ocos--Vienna Acoustics Beethoven/Maestro

          Comment


          • Originally posted by d6jg
            Might be worth a Poll - what is the first menu item you use?
            1. Almost always: Music Folder
            2. Distant second: Artists
            3. Much more distant third: Albums
            4. (default UI only): Advanced Search
            Usually running latest beta LMS nightly on Raspberry Pi OS with virtual players. Occasionally using SB Radio, Boom or Classic.

            Comment


            • Announce: Material Skin

              > I'm unable to search Qobuz from the material skin.

              I can confirm this. The click() function would simply return if an item
              was of type search. Search items must be treated somewhere else?

              --

              Michael
              Michael

              "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
              (LMS: Settings/Information)

              Comment


              • Originally posted by netchord
                I'm unable to search Qobuz from the material skin. i'm using a Synology DS216J NAS, and LMS 7.9.2. i've tried Chrome and Safari and neither works. click the search option in the Qobuz plugin and nothing happens. reverting to the default skin works fine.

                it doesn't work on Mobile either.
                I can verify this. The "Search" button for Qobuz no longer works - nothing happens. I had to flush all cookies and browsing data first however, and refresh the tab running the Material skin - and then it no longer worked using the 0.9.1 release.

                Aside from that, question: is it possible in a future release for the Qobuz Search option to work more like the Search option in Spotty, where I can see a some kind of list of prior text searches? Is this something that would have to be added to the Qobuz plugin itself?

                Anyway, thank you Craig for all your hard work - it certainly shows, what a fabulous job you have done.
                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


                • Announce: Material Skin

                  > Aside from that, question: is it possible in a future release for the
                  > Qobuz Search option to work more like the Search option in Spotty, where
                  > I can see a some kind of list of prior text searches? Is this something
                  > that would have to be added to the Qobuz plugin itself?


                  Yes, that's a feature of the individual services. Not available everywhere.

                  --

                  Michael
                  Michael

                  "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
                  (LMS: Settings/Information)

                  Comment


                  • Originally posted by mherger
                    > Aside from that, question: is it possible in a future release for the
                    > Qobuz Search option to work more like the Search option in Spotty, where
                    > I can see a some kind of list of prior text searches? Is this something
                    > that would have to be added to the Qobuz plugin itself?


                    Yes, that's a feature of the individual services. Not available everywhere.

                    --

                    Michael
                    Thank you for the info Michael.

                    -Ron
                    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 mherger
                      > I'm unable to search Qobuz from the material skin.

                      I can confirm this. The click() function would simply return if an item
                      was of type search. Search items must be treated somewhere else?
                      Yeah, search is handled differently - as its not a clickable area, it should be a text field, and search performed upon pressing return.

                      I assume Qobuz search worked with 0.9.0? Is the search in the 1st level of Qobuz items (i.e. in the list of items after entering the Qobuz app)? Does this list allow toggling from grid to list? i.e. is the "Toggle view" button in the sub-toolbar, or in the main 3-dotted menu on the right in the upper toolbar?

                      For 0.9.1 I changed some code so that the view recycler is used more often - as this is much quicker when changing from list to grid, and back. I'm thinking this change might be the cause of the issue.
                      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


                      • Announce: Material Skin

                        > Yeah, search is handled differently - as its not a clickable area, it
                        > should be a text field, and search performed upon pressing return.


                        Oh, that might explain it: Qobuz is another of those implementations
                        which uses icons, resulting in a grid view. Is search covered for grids?

                        > I assume Qobuz search worked with 0.9.0? Is the search in the 1st level
                        > of Qobuz items (i.e. in the list of items after entering the Qobuz app)?


                        Yes, 1st level.

                        > Does this list allow toggling from grid to list? i.e. is the "Toggle
                        > view" button in the sub-toolbar, or in the main 3-dotted menu on the
                        > right in the upper toolbar?


                        Yes, it can be toggled. But Search still wouldn't work.

                        --

                        Michael
                        Michael

                        "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
                        (LMS: Settings/Information)

                        Comment


                        • Originally posted by mherger

                          > Does this list allow toggling from grid to list? i.e. is the "Toggle
                          > view" button in the sub-toolbar, or in the main 3-dotted menu on the
                          > right in the upper toolbar?


                          Yes, it can be toggled. But Search still wouldn't work.
                          No, then it won't work. To speed up the recyler, I removed as many "if" clauses as possible - as I mainly want the recylcer for lists of the same type. So, when this is used, the search part is not wired in. I think I might see the error. Can you edit "browse-resp.js" and move line 341 ("types.add(i.type);") to line 340 - (i.e so that it is now before the closing bracket, not after).
                          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


                          • ..obviously the above edits would be for the non-minified git checkout version, not the released code...
                            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


                            • Announce: Material Skin

                              > No, then it won't work. To speed up the recyler, I removed as many "if"
                              > clauses as possible - as I mainly want the recylcer for lists of the
                              > same type. So, when this is used, the search part is not wired in. I
                              > think I might see the error. Can you edit "browse-resp.js" and move line
                              > 341 ("types.add(i.type);") to line 340 - (i.e so that it is now before
                              > the closing bracket, not after).


                              Yes, that would work. I'd no longer get the grid view, but a text input
                              for search instead.

                              --

                              Michael
                              Michael

                              "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
                              (LMS: Settings/Information)

                              Comment


                              • Originally posted by mherger
                                > No, then it won't work. To speed up the recyler, I removed as many "if"
                                > clauses as possible - as I mainly want the recylcer for lists of the
                                > same type. So, when this is used, the search part is not wired in. I
                                > think I might see the error. Can you edit "browse-resp.js" and move line
                                > 341 ("types.add(i.type);") to line 340 - (i.e so that it is now before
                                > the closing bracket, not after).


                                Yes, that would work. I'd no longer get the grid view, but a text input
                                for search instead.
                                Great! I'll commit this for the next release, thanks for the confirmation. Silly typo...
                                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
                                😀
                                🥰
                                🤢
                                😎
                                😡
                                👍
                                👎