Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Mini player

    What's the rationale for removing the mini player? Am I the only one who found it useful?

    Comment


    • @cpd73

      Do you plan to make a grid view for Artist like albums do ?
      Then picture can be import from a website like lastfm, discogs, wikipedia...
      Or maybe an artist.jpg in artist folder in the library.

      What do you think ?

      Comment


      • Originally posted by a491765
        @cpd73

        Do you plan to make a grid view for Artist like albums do ?
        Then picture can be import from a website like lastfm, discogs, wikipedia...
        Or maybe an artist.jpg in artist folder in the library.

        What do you think ?
        It's already there - and has been for some time. You need to enable Artist images in the "Music and Artist Information" plugin.
        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 already there - and has been for some time. You need to enable Artist images in the "Music and Artist Information" plugin.
          Amazing ! Thanks

          Comment


          • Originally posted by stevel6868
            What's the rationale for removing the mini player? Am I the only one who found it useful?
            Never saw the point in it. If it supported multiple instances then maybe. As is, just shrink the current window.
            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 stevel6868
              What's the rationale for removing the mini player? Am I the only one who found it useful?
              Well, I'm using it with Fluids possibility to pin it to my statusbar.
              Attached Files
              LMS 8.4 on MacBookPro | 1x Raspberry Pi Zero 2 W + moOde 7 UPnP as USB-Player + TEAC UD-501 USB-DAC + Phonitor Mini Headphone Amplifier + AKG K812 Headphones | 5x Squeezbox Radio (Red, White, Black) | 1x Raspbery Pi4 + Allo Boss 2 + Arcam FMJ A22+P25 BiAmping + B&W Nautilus 805

              Comment


              • Originally posted by stevel6868
                What's the rationale for removing the mini player? Am I the only one who found it useful?
                I use(d) it occasionally as well (via Squeezelite-X).

                Comment


                • Would it be possible in a future version to replicate the functionality in LMS that shows progress when doing a rescan? It looks like this:

                  Comment


                  • Originally posted by Apesbrain
                    Would it be possible in a future version to replicate the functionality in LMS that shows progress when doing a rescan? It looks like this:
                    You can see a scan's progress in Material, but not on the home page like the Default skin.

                    Click image for larger version

Name:	scanmaterial.jpg
Views:	1
Size:	62.9 KB
ID:	1568054
                    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 kidstypike
                      You can see a scan's progress in Material, but not on the home page like the Default skin.
                      Thanks, I hadn't looked at the "Settings" area of Material in some time and there's a lot that's new in there!

                      Comment


                      • Originally posted by tfec
                        Well, I'm using it with Fluids possibility to pin it to my statusbar.
                        I've re-added a mini-style view. "http: //SERVER:9000/material/mini" will now redirect to "http ://SERVER:9000/material/?layout=desktop" - but if the window height is <= 180px the middle part (browse/queue), menu button, 'i' button, and expand/collapse button will be hidden, the top/bottom toolbars will also be 'merged' (as in the borders removed, and the middle section given the same colour). This will mimic the previous min layout. It also means you can toggle this view just by shrinking the window when in desktop layout.

                        The only thing missing now is the entry in the main menu to launch the mini-player. Ideally I'd add a full/mini toggle to switch the main view from full-desktop to mini - but, AFAIK, this is impossible in Javascript (to stop malicious sites changing the window size).
                        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've re-added a mini-style view. "http: //SERVER:9000/material/mini" will now redirect to "http ://SERVER:9000/material/?layout=desktop" - but if the window height is <= 180px the middle part (browse/queue), menu button, 'i' button, and expand/collapse button will be hidden, the top/bottom toolbars will also be 'merged' (as in the borders removed, and the middle section given the same colour). This will mimic the previous min layout. It also means you can toggle this view just by shrinking the window when in desktop layout.

                          The only thing missing now is the entry in the main menu to launch the mini-player. Ideally I'd add a full/mini toggle to switch the main view from full-desktop to mini - but, AFAIK, this is impossible in Javascript (to stop malicious sites changing the window size).
                          I've now added an icon in the player menu (next to the power icon) to open mini-player. This allows you to have a mini-player per player.
                          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


                          • Is there a way to show the album covers in the music folder section? At the moment it only shows on albums, compilations and new music.

                            Thanks in advance

                            Comment


                            • Originally posted by Frank Black
                              Is there a way to show the album covers in the music folder section? At the moment it only shows on albums, compilations and new music.
                              AFAIK, no. This info is provided by LMS. Checked with default web UI, and SqueezeCtrl, and neither show covers.
                              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


                              • 1.4.0 Release

                                Feature release, main changes:
                                1. Add (optional) screensaver that will kick in after 60 seconds if nothing is playing on current player.
                                2. Notify on server updates, and add text stating new version available to information dialog.
                                3. When searching all categories, perform individual searches and combine results.
                                4. Allow playing of podcast episodes from search reponse.
                                5. Tweak UI a little; remove shadows, define a set of colours to allow easier customisation, use Roboto Mono for monospace font.
                                6. Add new themes; light (coloured toolbars), dark (coloured toolbars), and black. Various colour variants.
                                7. Merge mobile and desktop layout HTML files, so that page does not need to be reloaded when layout changes.
                                8. Make mini player HTML a redirect to desktop HTML. Shrinking the height of desktop will recreate the mini look. Show 'Open mini-player' icon next to power icon in player menu. Each player can be launched in its own mini-player window.
                                9. Make now-playing HTML a redirect to desktop HTML and auto trigger large now-playing view.
                                10. Open 'Text files from music folder' in an embedded iframe.
                                11. Read JSON file from server to appent custom entries to main menu, player's menu in 'Manager players' dialog, or as a list of actions at bottom of player settings dialog (if there is only 1 player). See README.md on github page for format.
                                12. Show circular progress in main toolbar when library is being rescanned. Clicking will show scan info.
                                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
                                😀
                                🥰
                                🤢
                                😎
                                😡
                                👍
                                👎