Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Originally posted by cpd73

    Foro 'Zap' you need to have (the original) 'Custom Skip' installed. However, I'm guessing you have 'Custom Skip 3'? Just checked and the code does not handle that case.
    You're quite right. Is this something that needs to be added to material, or Custom Skip 3?

    Comment


    • Not sure why you need to change the viewport. The above is Material @ 800x480 - same layout as your screenshot.
      Thanks for looking. The only difference between my screenshots is that first one is rendered in Firefox @ 800x480 while the other is Chromium on RPi with 4.3in 800x480 LCD. I will try your Material debug tip to better understand my issue.

      Comment


      • Originally posted by bossanova808

        You're quite right. Is this something that needs to be added to material, or Custom Skip 3?
        Material has been updated since 3.2.0 to look for CustomSkip3 - just tested and 'Zap' appears in menu for me.
        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


        • I would love to have a minimal Material Skin interface that works on my Galaxy Watch 5. Would a layout customised for a watch via the method at https://github.com/CDrummond/lms-mat...-Customisation be a workable solution using one of the Wear OS browsers? Even better, could the Android LMS app be modified to work under Wear OS?

          Comment


          • Originally posted by roymcd
            I would love to have a minimal Material Skin interface that works on my Galaxy Watch 5. Would a layout customised for a watch via the method at https://github.com/CDrummond/lms-mat...-Customisation be a workable solution using one of the Wear OS browsers? Even better, could the Android LMS app be modified to work under Wear OS?
            Sorry, no Material is not designed for such as small screen. The current customisation code does not easily support changing layouts. It can load custom Javascript, so anything is possible - but it would be quite fragile and prone to breaking. I have no such device, so have not even considered making changes for this.

            Would this just be for current track display and controls? Showing the queue? Browsing? As I'd imagine browsing would be quite difficult on such as small screen.
            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

              Sorry, no Material is not designed for such as small screen. The current customisation code does not easily support changing layouts. It can load custom Javascript, so anything is possible - but it would be quite fragile and prone to breaking. I have no such device, so have not even considered making changes for this.

              Would this just be for current track display and controls? Showing the queue? Browsing? As I'd imagine browsing would be quite difficult on such as small screen.
              Thanks for the quick reply. I'm trying to weigh up how to get an LMS controller interface for my watch. Your feedback is much appreciated because it saves me wasting effort on the customisation option.
              Current track display and control, volume control would be the minimum to be useful. I could start LMS playback from my phone and then switch to using the watch for simple track playback options.
              These simple controls are actually available automatically on the watch for android apps that register as media players, via the Media Control app on the watch. Could the LMS android app be modified to register as a media player and make the default media controls available? The Squeezer and Squeeze Ctrl android aps claim to have Wear compatibility. I've tried Squeezer and the Media Control interface on the watch does appear when I'm using it but the playback controls are ghosted and not usable. I don't have the Squeeze Ctrl app, but I've asked questions on the Squeeze Ctrl forum re its compatibility with Wear OS 3 and I haven't managed to get a definitive answer on whether it does work with the Media Controller on the watch. Regardless, I really like the Material Skin browser interface and the LMS app and I was hoping that a related interface on the watch might be an option.

              Comment


              • Hi Craig, would it be possible to remove the icons when using the custom browse plugin? Click image for larger version

Name:	view.jpg
Views:	552
Size:	143.6 KB
ID:	1635143
                Living: EtherRegen -> Ultrarendu -> Benchmark DAC2 HGC -> Benchmark AHB2 -> ATC SCM19 v2 & Sennheiser HD650
                Kitchen: SB Touch -> Audio Pro Addon T10 gen2
                Kids rooms: SB Booms
                Bedroom: SB Boom & SB Radio
                Controls: Material Skin & LMS via internet, iPeng
                Server: Windows 10 Pro with LMS 8.3
                Spare: 2 SB Touch, 1 SB3, 2 SB Radio

                Comment


                • Originally posted by Blackfiction
                  Hi Craig, would it be possible to remove the icons when using the custom browse plugin?
                  Done for 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


                  • Hi,
                    I'm using the Material Skin but I miss the menu option Sorting Order.
                    I use Spotty and have a lot of albums in the entry. The sorting is always albums in alphabetic order. I like to have a sort order with first interpreter, then albums ...
                    In the Material User Guide there is a Sorting Order menu in the Grid and List View entry of the manual.
                    May be someone can point me to a setting for my problem.
                    Gue

                    Comment


                    • Originally posted by Gue
                      Hi,
                      I'm using the Material Skin but I miss the menu option Sorting Order.
                      I use Spotty and have a lot of albums in the entry. The sorting is always albums in alphabetic order. I like to have a sort order with first interpreter, then albums ...
                      In the Material User Guide there is a Sorting Order menu in the Grid and List View entry of the manual.
                      May be someone can point me to a setting for my problem.
                      Gue
                      The sort order of Spotify content is controlled by the Spotty plugin. Material Skin allows for specifying the sorting order of the library and player queue only. I don't use Spotify but the Qobuz plugin supports choosing the sort order of Qobuz albums in its settings menu.
                      Last edited by SamY; 2023-03-31, 20:17.
                      Sam

                      Comment


                      • 3.2.3 release, changes:

                        1. Alter dimensions upon which now playing layout changes.
                        2. If 'replaceAll()' fails try 'replace()' with a regular expression.
                        3. Add a 'replaceAll()' polyfill.
                        4. Only show 'No Player' in 'Manage players' dialog if there are no players on this server and none seen on other servers.
                        5. Add 'npRatio' URL query parameter to control width/height ratio before now-playing toggles between landscape and portrait.
                        6. Replace all fill and stroke colours in SVG files.
                        7. Fix recolouring some plugin icons.
                        8. If list uses same image for all entries then do not show (does not apply to all lists).
                        9. Strip HTML tags before showing toast messages.
                        10. Add 'Symphonies' to default composer and conductor genres.
                        11. Ensure 'Classic' skin changes are applied to pages when loaded from plugins link in 'Information' dialog.
                        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
                          3.2.3 release, changes:


                          11. Ensure 'Classic' skin changes are applied to pages when loaded from plugins link in 'Information' dialog.
                          I think this is almost certainly obvious to everyone except me, but I can't seem to work out what this is or what problem it solves. I do prefer the classic skin when adding or changing plugins but otherwise always use material skin - so this change may or may not help if I can figure out what it is. A really simple explanation of the use case might help me, if someone has the time to provide it.

                          Sorry for being a bit slow
                          Nicholas

                          RPi4 / piCorePlayer v8.2.0 /Logitech Media Server Version: 8.3.1/ Hifiberry Digi+
                          3 Chromecast (2 mini x1 Chromecast Audio) 2 UPNP devices
                          also use a Gramofon off platform

                          Comment


                          • Originally posted by The Groundsman

                            I think this is almost certainly obvious to everyone except me, but I can't seem to work out what this is or what problem it solves. I do prefer the classic skin when adding or changing plugins but otherwise always use material skin - so this change may or may not help if I can figure out what it is. A really simple explanation of the use case might help me, if someone has the time to provide it.

                            Sorry for being a bit slow
                            For 'Server settings', extra 'Player settings', and 'Extras' Material uses the 'Classic' (not 'Default') skin but add some CSS tweaking to make them look more Material-like. It also adds a little javascript so that file-selector buttons are added to path selectors, etc. If you clicked on the text underneath the 'Update plugins' button (which is only shown if you have plugins that need updating) then Material opens 'Server settings' on the 'Plugins' page - but if opened this way, Material was not applying its javascript tweaks (so no path selector buttons).

                            Does that make sense?
                            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


                            • Got it now, yes makes sense. Thank you.
                              Nicholas

                              RPi4 / piCorePlayer v8.2.0 /Logitech Media Server Version: 8.3.1/ Hifiberry Digi+
                              3 Chromecast (2 mini x1 Chromecast Audio) 2 UPNP devices
                              also use a Gramofon off platform

                              Comment


                              • Does anyone know how to get F-Droid to automatically alert you when an LMS update is available? I have it set to do exactly that but it flatly refuses. I just opened the F-Droid app to check and the LMS update is available and has been there for 5 days. It only alerts me after I've manually checked and found it myself which is annoying to say the least 🤦‍♂️
                                Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
                                Bedroom: Radio
                                Bathroom: Radio

                                Comment

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