Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Testing shortcuts added to tooltips pushed to branch m3, looks good.
    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.
      Testing shortcuts added to tooltips pushed to branch m3, looks good.
      Thanks for testing. That branch will be merged into master soon (probably today).
      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 Ron F.
        Testing shortcuts added to tooltips pushed to branch m3, looks good.
        I've now merged this into master, and removed the 'm3' branch. I've changed the tooltip displays for prev, play/pause, next, 'go back', and 'go home' (for when home button is shown). Can you update and see if these are OK? I'm unsure about the 'play/pause' one where the space bar is used - I just use the unicode 'open box' symbol for this, but perhaps just 'Spacebar' would be better?
        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 now merged this into master, and removed the 'm3' branch. I've changed the tooltip displays for prev, play/pause, next, 'go back', and 'go home' (for when home button is shown). Can you update and see if these are OK? I'm unsure about the 'play/pause' one where the space bar is used - I just use the unicode 'open box' symbol for this, but perhaps just 'Spacebar' would be better?
          OK, I pulled the master branch and looking at the new tooltips, using the Brave and Firefox browsers. I think what you are attempting is a great idea, but I am having trouble seeing the arrows properly. It could be my eyes, (I am frightfully farsighted,) but even with my reading glasses, the arrows look like bars, especially the left and right arrows. The pointy part of the arrows is so small that I have trouble making it out as an arrow! Brave and Firefox display tooltips slightly differently, but the same issue exists in both. Possibly if the tooltips were slightly larger, or if the arrow was not an outline, but a solid character? I am not sure what to suggest. In the case of the Play/Pause button, "Spacebar" would definitely be better.
          Last edited by Ron F.; 2023-05-21, 07:47.
          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.
            I think what you are attempting is a great idea, but I am having trouble seeing the arrows properly. It could be my eyes, (I am frightfully farsighted,) but even with my reading glasses, the arrows look like bars, especially the left and right arrows.
            Thanks, thought there might be issues - I've reverted to just using text ("Left", "Right", "Spacebar", etc.)
            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

              Thanks, thought there might be issues - I've reverted to just using text ("Left", "Right", "Spacebar", etc.)
              Testing update, using words is definitely more readable and I think preferable.
              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


              • Hi folks.

                Challenge: Start UI in fullscreen mode in Web-App style

                Perhaps there's a solution to my challenge!?!?

                System:

                iPhone13
                iOS 16.5
                Safari
                I tried

                Add to Home Screen
                by using a

                192..xxx.x.xxx:9000/material/mobile
                style URL.

                This did not cause a FullScreen start. (I picked that up as a potential solution somewhere)

                It still needs a manual "aA" menu "Hide Toolbar" intervention to go fullscreen.


                Anybody managed to do it?


                THX
                Last edited by soundcheck; 2023-05-23, 13:12.
                ::: my blog: "The Audio Streaming Series & sKit - tuning kit - pCP " :::

                Comment


                • Hi folks

                  A long time ago I threatened to abandon the classics and duet I had in favour of Android tablets running SB Player and LMS. Well a split from my partner and a move into a new house forced that issue and that's exactly what I've done. No physical squeezebox devices in my setup anymore. Bought 3 cheap Android 10 tablets off Amazon and installed the above two apps on each. Generally speaking all works well except 3 points...

                  1. If I have an alarm set and it triggers and I hit the Stop play bar icon within seconds of it triggering, when the Alarm screensaver kicks in again, it switches instead to playing the blackbird back up alarm. If I let whatever random track the Alarm picks to play for about 30 seconds or more before I hit Stop, then the standard Alarm screensaver display comes on as I'd expect. So is there a timing issue with hitting the Stop button too quickly?
                  2. Occasionally, one or more of the tablets switches to displaying and acting as another player despite the player name being set on each tablet to be unique to that tablet in both SB Player and LMS. If I check SB Player on each tablet, the unique name still honours the device it's set for, but LMS has switched to another player. I can switch it back again, but why does LMS loose focus?
                  3. Cosmetic request... Can you make the Alarm icon to be the same colour brightness/contrast as the date & time? It's so dim by comparison it's almost invisible and then the time looks offset from the rest of the text on the display.

                  Thanks in advance.

                  Hyde.

                  Comment


                  • Originally posted by Hyde_TDS
                    1. If I have an alarm set and it triggers and I hit the Stop play bar icon within seconds of it triggering, when the Alarm screensaver kicks in again, it switches instead to playing the blackbird back up alarm. If I let whatever random track the Alarm picks to play for about 30 seconds or more before I hit Stop, then the standard Alarm screensaver display comes on as I'd expect. So is there a timing issue with hitting the Stop button too quickly?
                    I'd expect that to be an LMS issue, not related to the skin.

                    Originally posted by Hyde_TDS
                    2. Occasionally, one or more of the tablets switches to displaying and acting as another player despite the player name being set on each tablet to be unique to that tablet in both SB Player and LMS. If I check SB Player on each tablet, the unique name still honours the device it's set for, but LMS has switched to another player. I can switch it back again, but why does LMS loose focus?
                    Is this using the APK, or just the skin in a browser? If just the skin then you can use this to set a 'Default' player, but not to limit what is shown. To limit to only a single player you need to pass "single" on the URL (which is what the APK does). See https://github.com/CDrummond/lms-mat...ery-parameters for a list of parameters.


                    Originally posted by Hyde_TDS

                    3. Cosmetic request... Can you make the Alarm icon to be the same colour brightness/contrast as the date & time? It's so dim by comparison it's almost invisible and then the time looks offset from the rest of the text on the display.
                    The alarm icon is the same colour/opacity as its alarm time (which is on the same line), and looks fine to 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


                    • For the next release I'm adding a feature to clear upcoming tracks, or previous tracks, from the queue. The idea being that if there are multiple tracks in the queue you can clear ones before or after the current track (the relevant options are only shown if current track is not the first or last track). However, I'm unsure if this is a feature that should be "hidden" behind a long-press of the clear button, and a single/short-press simply prompt to clear all tracks as it does currently. Opinions?

                      If there are multiple tracks in the queue you will be prompted as follows:
                      Click image for larger version  Name:	clear-prompt.png Views:	7 Size:	16.9 KB ID:	1639655

                      The confirmation dialog for a single track in the queue will now be:

                      Click image for larger version  Name:	clear-single.png Views:	7 Size:	6.2 KB ID:	1639656

                      ...but should I use this simple dialog as the default case, and the more complex via long-press? Clear upcoming/previous is a feature I've never had a need for on any music player, hence my query here. I don't want to over-complicate the primary use case, but I'm wary of "hiding" more features behind long-press...


                      [Edit] After playing with this for a while now, I'm leaning towards having the more complex dialog via long-press, as when I press clear I want to remove all tracks...
                      Last edited by cpd73; 2023-05-27, 08:50.
                      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'm constantly appending tracks to a queue or inserting a new playlist into the queue and moving queues between players. This would be a welcome feature for me but I suspect the way I use queues and playlists like this is not that typical..

                        For me either approach works as when i hit the icon on my android phone I already get a confirmation to remove all tracks from the queue before they are actually removed. Having the other options below removing all tracks would be great for me, However I do see your point that many users just want a simple clear option.

                        Personally I don't see it as that complicated so I would have all the options available without the need for a long press. It's not intrusive imho and a lot of causal users would miss this lovely feature if it was behind a long press.

                        Nicholas

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

                        Comment


                        • Originally posted by cpd73
                          For the next release I'm adding a feature to clear upcoming tracks, or previous tracks, from the queue. The idea being that if there are multiple tracks in the queue you can clear ones before or after the current track (the relevant options are only shown if current track is not the first or last track). However, I'm unsure if this is a feature that should be "hidden" behind a long-press of the clear button, and a single/short-press simply prompt to clear all tracks as it does currently. Opinions?

                          If there are multiple tracks in the queue you will be prompted as follows:
                          Click image for larger version Name:	clear-prompt.png Views:	7 Size:	16.9 KB ID:	1639655

                          The confirmation dialog for a single track in the queue will now be:

                          Click image for larger version Name:	clear-single.png Views:	7 Size:	6.2 KB ID:	1639656

                          ...but should I use this simple dialog as the default case, and the more complex via long-press? Clear upcoming/previous is a feature I've never had a need for on any music player, hence my query here. I don't want to over-complicate the primary use case, but I'm wary of "hiding" more features behind long-press...


                          [Edit] After playing with this for a while now, I'm leaning towards having the more complex dialog via long-press, as when I press clear I want to remove all tracks...
                          Don't hide it behind long press (presuming there isn't a further confirmation dialog after selecting the scope of the clear, it would still be only two presses/clicks to clear the whole queue as at present). I would also make the clear button in the single track queue version an option not a blue button:

                          ​​​​​​So, either

                          Clear all
                          Remove upcoming tracks
                          Remove previous tracks
                          Cancel

                          or simply

                          Clear
                          Cancel

                          in the case of a single track queue.

                          While on the subject of queue management, I've noticed that in the Android App, dragging tracks up and down the queue shows the pop up options while you're doing it, unlike the browser version. Can this be suppressed?

                          Comment


                          • Originally posted by soundcheck
                            This did not cause a FullScreen start. (I picked that up as a potential solution somewhere)
                            I only used in Safari (iPhone 11, iOS 16.5) the URL: http://192.168.178.109:9000/material and saved this to the homescreen. Then I am getting this:
                            Click image for larger version

Name:	IMG_8501.png
Views:	183
Size:	1.61 MB
ID:	1639683
                            Attached Files
                            Pi4 4GB piCorePlayer with LMS and Squeezelite for USB inside an Argon One case
                            Pi3B+ (7" Display, Hifiberry DAC+ Pro) piCorePlayer with Squeezlite/Jivelite for Hifiberry inside a SmartiPi touch case
                            Pi Zero W only for Bluetooth headphones
                            Two Airport Express
                            Ikea Symfonisk

                            Comment


                            • Agree with The Groundsman and darrell . No long press needed. Always present all options** and cancel.

                              ** all options differing if one or multiple tracks in queue as stated.

                              My question would be - if multiple tracks are in the queue, and you select "remove previous tracks" would that launch another "confirm" dialog box? I am not sure that is necessary as long as the selections are separated enough to prevent a fat finger. But, if it is a two tap solution, no big deal. Maybe an option to enable/disable two tap requirement, similarly a "remember this choice" or "don't ask again"

                              Jim

                              Comment


                              • Originally posted by darrell
                                presuming there isn't a further confirmation dialog after selecting the scope of the clear
                                No, there is no further confirmation - that'd be a bit OTT.

                                Originally posted by darrell
                                I would also make the clear button in the single track queue version an option not a blue button:
                                Tried, but I think this looks weird:

                                Click image for larger version

Name:	single-track.png
Views:	328
Size:	8.8 KB
ID:	1639700

                                Originally posted by darrell
                                I've noticed that in the Android App, dragging tracks up and down the queue shows the pop up options while you're doing it, unlike the browser version. Can this be suppressed?
                                Thanks for reporting, I had not noticed this. Will try to fix for next release - raised https://github.com/CDrummond/lms-material/issues/677 so its not forgotten.
                                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
                                😀
                                🥰
                                🤢
                                😎
                                😡
                                👍
                                👎