Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • #61
    Announce: Material Skin

    > I also tried to remove that line, but after restart it comes back. Did
    > you only delete it in /cahce/Installedplugins/plugins ?
    > In the D/L zip the line is still there...


    Just leave it alone. With the next update the problem should be gone.

    --

    Michael
    Michael

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

    Comment


    • #62
      Originally posted by kidstypike
      Possibly a coincidence, but since installing the Material skin, something is randomly resetting players volume to zero.
      Anyone else seeing this?
      is there any chance that happens after you pause that player?

      On my setup i only use material skin for one player and the volume from that player is muted every time i paused it.
      The other players (not used with that skin) the volumelevel is untouched.

      Comment


      • #63
        Originally posted by DJanGo
        is there any chance that happens after you pause that player?

        On my setup i only use material skin for one player and the volume from that player is muted every time i paused it.
        The other players (not used with that skin) the volumelevel is untouched.
        Odd, I have just tried and I cannot recreate this. However, I have no real squeezeboxes - only Airplay and piCorePlayer.
        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


        • #64
          Originally posted by cpd73
          Odd, I have just tried and I cannot recreate this. However, I have no real squeezeboxes - only Airplay and piCorePlayer.
          I tried as well and the volume was not affected by pausing with my Radio and Touch.

          Sent from my SM-G900F using Tapatalk
          Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
          Bedroom: Radio
          Bathroom: Radio

          Comment


          • #65
            Pausing doesn't seem to be the culprit for me either. Next time it happens I'll try to find the cause.
            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


            • #66
              Announce: Material Skin

              > Odd, I have just tried and I cannot recreate this. However, I have no
              > real squeezeboxes - only Airplay and piCorePlayer.


              Volume handling is a bitch... you change it in the UI, send the command
              to the server, which in turn would tell your UI to update the volume to
              the volume where it was fraction of a seconds before, as you keep
              pulling the slider... as a result you see a jumping volume slider.
              Happened here, too. And happened with other UIs I've been working on.

              As a starter you should probably buffer volume events coming from the
              server. Or ignore them as long as the user is interacting with the
              volume control.

              --

              Michael
              Michael

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

              Comment


              • #67
                Originally posted by kidstypike
                Pausing doesn't seem to be the culprit for me either. Next time it happens I'll try to find the cause.
                ok pause seems to be the wrong description.

                That player is used with dont stop the music.
                And i never seen the volume change when the player plays.
                Only after pausing it and leave it (player and gui) alone for a while - sometimes the volume is mited.

                Comment


                • #68
                  Originally posted by kidstypike
                  Pausing doesn't seem to be the culprit for me either. Next time it happens I'll try to find the cause.
                  2 mornings on the run now, LMS default UI on PC shows volume=100, using phone/material skin, select a favourite to play, volume=0. (player is Pi/HiFiBerry/squeezelite)
                  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


                  • #69
                    Looking at the code I think I know what might be causing this. Either way, I have a work-around where the skin will check that it's volume dialog is visible before sending any volume commands - and before showing this dialog, retrieve the current volume. I'll experiment more later, and make a release soon.
                    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


                    • #70
                      Originally posted by cpd73
                      That's a good point! I only actually have 2 players, so never thought about this. Perhaps dimming the speaker icon of powered off players? Or colouring the icon blue for powered on players? Don't really want to add another icon next to the player (as there already is a tick and speaker/group icon).

                      I was thinking of adding a dialog to manage the volume of all players. Perhaps this could also be used to power them on/off...
                      I wander away for a few days and ... nice to see all the work going on!

                      I see the speaker icon is now dim for off. What I do like about the traditional skin is that I can click the power button in the player list dropdown without selecting the player, typically when I have left one on by mistake and I start playing on another (they are all synced).Even if the material framework doesn't permit that level of interaction could there be a way of, at minimum, turning all players off?

                      I am going to try to keep up with this thread, but it's moving fast!

                      Comment


                      • #71
                        Originally posted by Peter Galbavy
                        I see the speaker icon is now dim for off. What I do like about the traditional skin is that I can click the power button in the player list dropdown without selecting the player, typically when I have left one on by mistake and I start playing on another (they are all synced).Even if the material framework doesn't permit that level of interaction could there be a way of, at minimum, turning all players off?
                        I have a TODO file (https://raw.githubusercontent.com/CD...al/master/TODO) that lists the features, issues, etc. that are TODO. Managing all players (so volume and power) is on the list. Putting on/off buttons on the list would be a little cramped on a mobile 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


                        • #72
                          Minor issue with using test setup

                          Thank you for a really nice skin! Works very well in normal use (after disabling the "automatic update of plugins" until next release), especially nice in a Chrome window started with the "--app" parameter. I use it all the time now. Simple and clean :-)

                          However, I tried to setup the test config mentioned last in the Readme and couldn't make it work:

                          The skin may be installed on a machine separate to LMS. Currently this is how its developed. e.g.

                          cd in the material folder
                          Start python's simple HTTP server - e.g. python -m SimpleHTTPServer
                          Access on localhost via http://localhost:8000/?lms=192.168.0.1 (replace 192.168.0.1 with the IP address of the LMS server)
                          I have tried on two PC's (both are Linux Mint 18.3) using latest Firefox and Chrome, but it seems to hang with a rotating symbol and text "Looking for players". When I open a java console it shows recurring messages as quoted below:
                          Code:
                          Access to XMLHttpRequest at 'http://linux2:9000/jsonrpc.js' from origin 'http://localhost:8000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
                          server.js:76 
                          Error: Network Error at e.exports (axios.min.js:8)
                          at XMLHttpRequest.l.onerror (axios.min.js:8)
                          I downloaded the plugin as a Zip-file from Github, unzipped and started the python SimpleHTTPServer with the 'material' dir as working directory.
                          Do you have any idea as to what I'm missing? It seems a key message to the LMS server ("linux2" in my case) is blocked on the client by the browser.

                          Please note - this is not a big issue in any way. The skin is actually working very well indeed.
                          2 Touch, 2 Picoreplayer
                          LMS 8.3.0 on Debian 11 on Intel-NUC. All wired
                          Main audio system: speakers Magnepan 3.6, amp "Gdis 400", DAC & pre: NAD M51, streamers: SB Touch // NAD M50

                          Comment


                          • #73
                            Originally posted by cpd73
                            Looking at the code I think I know what might be causing this. Either way, I have a work-around where the skin will check that it's volume dialog is visible before sending any volume commands - and before showing this dialog, retrieve the current volume. I'll experiment more later, and make a release soon.
                            Repeatable.

                            If Material is controlling player "A", and is running on my phone (even if it's in the background), then powering off player "A" by any other means (jivelite touch screen, jivelite with IR remote, Squeezer, Squeeze Ctrl, or the default webUI on a PC) then the volume is instantly set to zero.

                            Powering off Player "A" if Material is controlling another player has no effect on player "A's" volume.
                            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


                            • #74
                              Originally posted by kidstypike
                              Repeatable.

                              If Material is controlling player "A", and is running on my phone (even if it's in the background), then powering off player "A" by any other means (jivelite touch screen, jivelite with IR remote, Squeezer, Squeeze Ctrl, or the default webUI on a PC) then the volume is instantly set to zero.

                              Powering off Player "A" if Material is controlling another player has no effect on player "A's" volume.
                              Can confirm this.

                              Sent from my SM-G900F using Tapatalk
                              Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
                              Bedroom: Radio
                              Bathroom: Radio

                              Comment


                              • #75
                                0.0.6 Release

                                Changes:
                                1. Initial work on SlimBrowse - only used in favorites and radios so far.
                                2. Dutch, German, and French translations.
                                3. Group players have no replaygain setting.
                                4. Show album year in play queue.
                                5. Don't sort favorites - as the order can be determined in default web UI.
                                6. Ensure volume is only ever adjusted whilst dialog is shown.
                                7. Add insert action.


                                Hopefully this fixes the update and volume issues.
                                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
                                😀
                                🥰
                                🤢
                                😎
                                😡
                                👍
                                👎