Announcement

Collapse
No announcement yet.

Announce: Material Skin

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • #76
    Originally posted by BosseJ
    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)
    Hi,
    please goto http://your.lms.server.ip:9000/setti.../security.html
    and set your ips into the last filde something with CORS

    Originally posted by kidstypike
    Repeatable.
    aaargs ;-) i just forgot a script on my lms that powers off all stopped or paused more than 10 minutes players ...

    Comment


    • #77
      Originally posted by cpd73
      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.
      Thanks, update and volume issues appear to be fixed.

      If a player is powered off when opening Material on my phone, then there is no playlist, I can't carry on from where I left off. I can't power on the player using Material, as the player on/off switch(s) appear not to work.

      If I power the player on by some other means, then the playlist appears and I can resume playing it.
      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


      • #78
        Originally posted by kidstypike
        Thanks, update and volume issues appear to be fixed.

        If a player is powered off when opening Material on my phone, then there is no playlist, I can't carry on from where I left off. I can't power on the player using Material, as the player on/off switch(s) appear not to work.

        If I power the player on by some other means, then the playlist appears and I can resume playing it.
        I think I noticed the on/off switch issue with the previous version as well as the latest.

        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


        • #79
          Originally posted by slartibartfast
          I think I noticed the on/off switch issue with the previous version as well as the latest.
          Ah, yes. This is a little embarrassing, but I put the 1/0 the wrong way round in the power commands! If you want to fix for yourself, edit MaterialSkin/HTML/material/html/js/toolbar.js and change the "1" on line 172 to a "0", and the "0" on line 176 to a "1"

          I never switch off my speakers via LMS, so never noticed! Sorry.
          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


          • #80
            Originally posted by kidstypike
            Thanks, update and volume issues appear to be fixed.

            If a player is powered off when opening Material on my phone, then there is no playlist, I can't carry on from where I left off. I can't power on the player using Material, as the player on/off switch(s) appear not to work.

            If I power the player on by some other means, then the playlist appears and I can resume playing it.
            I find even if a player is stopped then there is no playlist displayed. I am not entirely sure how "off" differs from "stopped".

            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


            • #81
              Originally posted by slartibartfast
              I find even if a player is stopped then there is no playlist displayed. I am not entirely sure how "off" differs from "stopped".
              How do you stop a player? Can you do this from the default web UI? Currently the skin will only fetch the playlist if the player is "on"
              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


              • #82
                Originally posted by cpd73
                Ah, yes. This is a little embarrassing, but I put the 1/0 the wrong way round in the power commands! If you want to fix for yourself, edit MaterialSkin/HTML/material/html/js/toolbar.js and change the "1" on line 172 to a "0", and the "0" on line 176 to a "1"

                I never switch off my speakers via LMS, so never noticed! Sorry.
                I wpuldn't normally use it either I only noticed when I was playing around with the volume issue last night. I was switching players off with Orange Squeeze (something else I hadn't done before and struggled to find) and Material would not turn them back on [emoji3]

                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


                • #83
                  Originally posted by slartibartfast
                  I find even if a player is stopped then there is no playlist displayed. I am not entirely sure how "off" differs from "stopped".

                  Sent from my SM-G900F using Tapatalk
                  First pic shows player is powered on, in this state, Material sees the playlist when opened.

                  Second pic shows player is powered off, Material doesn't see the playlist when opened.

                  Click image for larger version

Name:	power on.jpg
Views:	1
Size:	34.8 KB
ID:	1565185


                  Click image for larger version

Name:	power off.jpg
Views:	1
Size:	32.8 KB
ID:	1565186
                  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


                  • #84
                    Originally posted by kidstypike
                    First pic shows player is powered on, in this state, Material sees the playlist when opened.

                    Second pic shows player is powered off, Material doesn't see the playlist when opened.
                    I know that material does not show the play queue if the player is powered off - which makes sense to me. Or do you think it should also show the play queue even if the player is off? If so, why? Not against changing it to be that way, would just like to know the reason.

                    The question I was interested in is how you "stop" a player - as I was getting the impression that this is not the same as it being off. I assume it can be on and stopped?
                    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


                    • #85
                      Originally posted by cpd73
                      I know that material does not show the play queue if the player is powered off - which makes sense to me. Or do you think it should also show the play queue even if the player is off? If so, why? Not against changing it to be that way, would just like to know the reason.

                      The question I was interested in is how you "stop" a player - as I was getting the impression that this is not the same as it being off. I assume it can be on and stopped?
                      Yes, a player can be stopped, but still powered on.

                      My use case, just stopping/pausing the player, leaves the player powered on, showing the word clock screensaver.

                      I power "off "the player last thing at night using an IR remote, this dims the screen and shows a digital clock screensaver that I use as a bedside clock.
                      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


                      • #86
                        Originally posted by cpd73
                        How do you stop a player? Can you do this from the default web UI? Currently the skin will only fetch the playlist if the player is "on"
                        I have the power button on my radio configured in LMS to "stop on power off and remain stopped on power on". If I use pause instead it causes issues with the BBC iPlayer plugin where the station would resume from the paused position rather than play the current programme when powered on.

                        BUT my Touch is also in the "stopped" state and the playlist is visible. So I think the Radio is stopping and switching off since when I power on again (before it completely powers down) the playlist reappears in Material.

                        In this Stopped/Off state the Default skin of LMS does show the playlist.

                        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


                        • #87
                          Originally posted by cpd73
                          I know that material does not show the play queue if the player is powered off - which makes sense to me. Or do you think it should also show the play queue even if the player is off? If so, why? Not against changing it to be that way, would just like to know the reason.
                          Personally, I would like to see the playlist when the player is powered off, as is the case with the default webUI, then I can decide if I wish to resume it or play something different

                          The default webUI shows the playlist for all my players, whether they're powered on or off.
                          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


                          • #88
                            Originally posted by kidstypike
                            Yes, a player can be stopped, but still powered on.

                            My use case, just stopping/pausing the player, leaves the player powered on, showing the word clock screensaver.

                            I power "off "the player last thing at night using an IR remote, this dims the screen and shows a digital clock screensaver that I use as a bedside clock.
                            As stated, I have no real squeezeboxes. But how do you stop the player? i.e. what I'd like to do is simulate a stop (and start?) so that I can test how things behave. Is there a way on the web ui to stop the player? If you stop your player - does the queue disappear from the skin? If you then start the player, does the skin then show the queue?

                            ...ah missed the post above yours!
                            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


                            • #89
                              Originally posted by kidstypike
                              Yes, a player can be stopped, but still powered on.

                              My use case, just stopping/pausing the player, leaves the player powered on, showing the word clock screensaver.

                              I power "off "the player last thing at night using an IR remote, this dims the screen and shows a digital clock screensaver that I use as a bedside clock.
                              Is this issue tied in with the reversed on/off logic? If I power off the player using the default skin button then the playlist appears in Material. If I power on the player in default then the playlist disappears. So fixing the on/off logic may also fix this.

                              On second thoughts maybe not as the playlist is displayed in the default skin regardless of the power state.

                              Sent from my SM-G900F using Tapatalk
                              Last edited by slartibartfast; 2018-10-30, 10:52.
                              Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
                              Bedroom: Radio
                              Bathroom: Radio

                              Comment


                              • #90
                                Originally posted by slartibartfast
                                Is this issue tied in with the reversed on/off logic? If I power off the player using the default skin button then the playlist appears in Material. If I power on the player in default then the playlist disappears. So fixing the on/off logic may also fix this.

                                Sent from my SM-G900F using Tapatalk
                                My case is the reverse of yours!

                                Powering the player off using the button on the default webUI, the playlist disappears from material on my phone, you can see it happen!

                                Powering the player on using default webui the playlist appears.

                                Vanilla install of material, I haven't touched any code.
                                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

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