Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    On Android I run with zoom 70%, font small. On my mobile this gives the best compromise.

    The most annoying thing I was seeing with standard settings (regular font, 50% zoom) was that album reviews (via MAI) were often presented with album artwork images displayed alongside a narrow band of text, making them look untidy and difficult to read, see below (regular, 50% followed by small, 70%).

    The small/70% is preferable to me as the text is pretty much the same size and the formatting is improved, at least on my particular mobile.

    Click image for larger version  Name:	Screenshot_2023-01-30-16-03-25-878_com.craigd.lmsmaterial.app.jpg Views:	10 Size:	81.0 KB ID:	1628622


    Click image for larger version  Name:	Screenshot_2023-01-30-16-04-21-514_com.craigd.lmsmaterial.app.jpg Views:	10 Size:	78.0 KB ID:	1628623


    ​​​​​
    Last edited by staresy; 2023-01-30, 17:55.
    Location 1: LMS 8.3 on Win 10 Brix Server, x3 SB Radios, x1 Touch, x1 Controller : Location 2: LMS 8.3 on Win 10 Brix Server, x2 SB Radios, x1 Duet Receiver, x1 Controller : Alexa Mediaserver Smart Skill, Material Android, SqueezeliteX control

    Comment


      Originally posted by staresy View Post
      On Android I run with zoom 70%, font small. On my mobile this gives the best compromise.

      The most annoying thing I was seeing with standard settings (regular font, 50% zoom) was that album reviews (via MAI) were often presented with album artwork images displayed alongside a narrow band of text, making them look untidy and difficult to read, see below (regular, 50% followed by small, 70%).

      he small/70% is preferable to me as the text is pretty much the same size and the formatting is improved, at least on my particular mobile.

      ​​​​​
      Nice catch! I also was annoyed by that narrow text column beside the artist pic in MAI. Changing to "Small, 70%" fixed it without changing the main display except for losing the power button in the upper left corner, which is a trade-off I can live with. Thumbs up!

      Click image for larger version

Name:	Screenshot_2023-01-30-11-40-34.jpg
Views:	170
Size:	1.17 MB
ID:	1628625
      Sam

      Comment


        Originally posted by SamY View Post

        Nice catch! I also was annoyed by that narrow text column beside the artist pic in MAI. Changing to "Small, 70%" fixed it without changing the main display except for losing the power button in the upper left corner, which is a trade-off I can live with. Thumbs up!

        Click image for larger version  Name:	Screenshot_2023-01-30-11-40-34.jpg Views:	2 Size:	1.17 MB ID:	1628625
        I hadn't noticed the power button disappearing, but as I've been running small/70% for months now, I guess I don't miss it
        Location 1: LMS 8.3 on Win 10 Brix Server, x3 SB Radios, x1 Touch, x1 Controller : Location 2: LMS 8.3 on Win 10 Brix Server, x2 SB Radios, x1 Duet Receiver, x1 Controller : Alexa Mediaserver Smart Skill, Material Android, SqueezeliteX control

        Comment


          I've been meaning to post this for awhile but keep forgetting. As far as I can tell, there isn't any way to save changes made in the main "Player settings" menu screen. There is no "Save Settings" button displayed, as there is on the "Extra player settings" screens, and any changes made on the screen are not saved. Am I missing something?
          Sam

          Comment


            Originally posted by SamY View Post
            I've been meaning to post this for awhile but keep forgetting. As far as I can tell, there isn't any way to save changes made in the main "Player settings" menu screen. There is no "Save Settings" button displayed, as there is on the "Extra player settings" screens, and any changes made on the screen are not saved. Am I missing something?
            Settings are saved when you close the dialog (as per most settings pages in Android). The pages with "Save settings" are not actually from Material, but from the "Classic" skin with some CSS tweaks.
            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 staresy View Post

              I hadn't noticed the power button disappearing, but as I've been running small/70% for months now, I guess I don't miss it
              Now I have tried the 70% zoom and small font I have gone back to regular font keeping the 70% zoom. Although I preferred the text size of the small font I got the impression that the gap between menu items was too big. Losing the player icon/power button doesn't bother me as I wasn't using the power button anyway 😀
              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 View Post

                Now I have tried the 70% zoom and small font I have gone back to regular font keeping the 70% zoom. Although I preferred the text size of the small font I got the impression that the gap between menu items was too big. Losing the player icon/power button doesn't bother me as I wasn't using the power button anyway 😀
                Yeah, I thought the same originally re the gap between menu items but I've got used to it. I just tried going back to regular/70% and the font looks way too big to me now - it looks like a kids learning to read book!

                Location 1: LMS 8.3 on Win 10 Brix Server, x3 SB Radios, x1 Touch, x1 Controller : Location 2: LMS 8.3 on Win 10 Brix Server, x2 SB Radios, x1 Duet Receiver, x1 Controller : Alexa Mediaserver Smart Skill, Material Android, SqueezeliteX control

                Comment


                  Tiny anomaly in display of track listing.

                  This is track listing of Herbie Hancock's Maiden Voyage (1965) - a lovely jazz album btw - when accessed in the "usual way" i.e. from Artist / Album etc

                  Click image for larger version

Name:	image.png
Views:	111
Size:	44.9 KB
ID:	1628684

                  This is the track listing of the same album when "browsed" from the bottom of the MAI bio - note only 16bit is shown rather than the full tech info as before

                  Click image for larger version

Name:	image.png
Views:	109
Size:	126.3 KB
ID:	1628686

                  Click image for larger version

Name:	image.png
Views:	107
Size:	26.1 KB
ID:	1628685

                  Obviously it makes no difference to functionality so I am reporting it purely as an anomaly and it is entirely up to Craig whether he wants to correct or not.

                  I think it is across all browser types.​
                  Jim
                  https://jukeradio.double6.net


                  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 View Post
                    Tiny anomaly in display of track listing.
                    ...

                    Obviously it makes no difference to functionality so I am reporting it purely as an anomaly and it is entirely up to Craig whether he wants to correct or not.​
                    Yeah, for some reason I added the bit-size meta-data flag regardless of tech info display. I've now fixed this, and tech info should be shown for all track listings (if enabled, and apart from the queue).

                    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 View Post

                      Settings are saved when you close the dialog (as per most settings pages in Android). The pages with "Save settings" are not actually from Material, but from the "Classic" skin with some CSS tweaks.
                      Maybe I wasn't clear. Changes made to the settings on this screen are NOT saved when the dialog is closed. Otherwise, I wouldn't have reported it as a problem.
                      Sam

                      Comment


                        Originally posted by SamY View Post

                        Maybe I wasn't clear. Changes made to the settings on this screen are NOT saved when the dialog is closed. Otherwise, I wouldn't have reported it as a problem.
                        Which specific changes? Because I have just tried, and they are saved 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


                          Originally posted by cpd73 View Post

                          Which specific changes? Because I have just tried, and they are saved for me.
                          None of them are saved for me. We can start with the "Audio/On song change" crossfade setting. A change made on this page is not saved. However, if the change is made from the "Extra player settings/Audio" page ("Crossfade" setting) and "Save Settings" is pressed, it is saved. The problem is that many of the player settings, specifically those related to alarms, are only available on the main player settings page and thus cannot be changed (for me) in MS.
                          Sam

                          Comment


                            Originally posted by SamY View Post

                            None of them are saved for me. We can start with the "Audio/On song change" crossfade setting. A change made on this page is not saved. However, if the change is made from the "Extra player settings/Audio" page ("Crossfade" setting) and "Save Settings" is pressed, it is saved. The problem is that many of the player settings, specifically those related to alarms, are only available on the main player settings page and thus cannot be changed (for me) in MS.
                            Any errors logged in your browser's developer tools console or network tabs? Which version of Material are you using? If its git/master then I've noticed an issue here. I added a "userInterfaceIdiom:Material" to all JSONRCP queries, so that plugins can know the request is from Material (this was asked for by another user). But, this seems to break some queries. So, I'll remove this before 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


                              Originally posted by cpd73 View Post

                              Any errors logged in your browser's developer tools console or network tabs? Which version of Material are you using? If its git/master then I've noticed an issue here. I added a "userInterfaceIdiom:Material" to all JSONRCP queries, so that plugins can know the request is from Material (this was asked for by another user). But, this seems to break some queries. So, I'll remove this before release.
                              Well, this is embarrassing! After noticing that the changes are actually saved correctly for the players using my Denon AVR Control plugin, I found a bug in the playerpref callback routine of the plugin that results in it incorrectly "eating" the playerpref commands for non-Denon players without calling the original LMS function. Oops!!! Incidents like this remind us how interdependent we all are on each other in this wonderful LMS development world. Fortunately, this is an easily fixed problem that only affects a small subset of users but it would have been more difficult to track down if it hadn't happened to me first. Sorry for causing you additional unnecessary work, Craig. I owe you one.

                              EDIT: Denon AVR Control plugin updated and verified. Fixed in next release.
                              Last edited by SamY; Yesterday, 20:18.
                              Sam

                              Comment

                              Working...
                              X