Announcement

Collapse
No announcement yet.

[Announce] Squeezelite-X

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

    Originally posted by kidstypike View Post
    This doesn't sound like a SQ-X item, are you using the Material skin?

    If yes, go to Settings > Interface > scroll down to "My Music" click the cog and tick the items you wish to appear.
    Thanks, exactly what I was looking for! I should have dug into the interface more.
    Current:
    Windows 10 - LMS Server 8.3.0 8TB RAID 10 Media Drive
    Office - Windows 10 - Squeezelite-X
    Living Room - 2x RPiZeroW w/ Allo MiniBoss each running a Logitech Z623 System
    Family Room (TV) - 1X RPi3B+ HDMI to Denon Surround Receiver 7.2 System
    Bedroom 1x RPi3B+ with HiFiBerry DAC+ to powered SW and 2X Alesis M1 Active Monitors
    Kitchen - Bose Soundlink Mini II BL speaker

    All running piCorePlayer 8.2.0 and synchronized.

    Building
    Pi Boombox - RPi4B w/ HiFiBerry DAC+

    Comment


      Originally posted by NAG View Post
      I am facing the same issue, Windows 11 10.0.2621 build 22621 . All was fine then about two weeks ago the interface stopped displaying properly, just a rotating white ring on black background. Tried unistalling, wiped registry (1 key) and reinstalling, still no interface. The app plays on the PC, but there is no interace displayed. Any ideas? Thanks!
      If you have not tried this, go into settings and enable advanced settings and toggle Clear Cache and press OK, you will be prompted to restart, say yes. If anyone has a problem after this let me know.

      R Greg Dawson
      Squeezelite-X

      Comment


        Originally posted by rgdawson View Post
        If you have not tried this, go into settings and enable advanced settings and toggle Clear Cache and press OK, you will be prompted to restart, say yes. If anyone has a problem after this let me know.

        R Greg Dawson
        Hi Greg - I tried this. Tried reinstalling both stand alone & windows store versions. Music plays but the interface continues to just show blue quaver logo, squeezelite-X and a rotating white ring on black background. No issues accessing the LMS interface via browser (on port :9000/Material). FYI, running latest LMS Version: 8.3.0 - 1667251155 from lmscommunity on DSM 7.1.1-42962 Update 1 in a docker container.

        I tried usign Recuva Unistaller too, this just picked up the same key I had already found before, not a solution for me.

        Any ideas?

        Comment


          Originally posted by NAG View Post
          Hi Greg - I tried this. Tried reinstalling both stand alone & windows store versions. Music plays but the interface continues to just show blue quaver logo, squeezelite-X and a rotating white ring on black background. No issues accessing the LMS interface via browser (on port :9000/Material). FYI, running latest LMS Version: 8.3.0 - 1667251155 from lmscommunity on DSM 7.1.1-42962 Update 1 in a docker container.

          I tried usign Recuva Unistaller too, this just picked up the same key I had already found before, not a solution for me.

          Any ideas?
          I'll need to see some detailed logging data to troubleshoot. Btw do you get same with default skin?

          R Greg Dawson
          Squeezelite-X

          Comment


            Squeezelite network issue on Windows - Solved?

            Hi Greg

            I'm a keen user of your Squeezebox client

            As I'm sure you know, squeezelite on Windows has a bit of a connectivity issue, which Squeezelite-X I think inherited. A solution at long last was found for this as recent as last week:

            see github.com/ralph-irving/squeezelite/commit/226efa300c4cf037e8486bad635e9deb3104636f

            Will you pick this fix up in any upcoming versions of your client on Windows?

            Thanks much
            Last edited by Fabrini; 2022-12-30, 00:29.

            Comment


              Originally posted by rgdawson View Post

              I'll need to see some detailed logging data to troubleshoot. Btw do you get same with default skin?

              R Greg Dawson
              Hi Greg

              I get the same behaviour with the default skin. I now tried loading squeezelite on two other W11 laptops on the same internal network, same behavour. The client will play, but the interface doesn't display, only the rotating round ring. I looked at the debug log screens, can't see anything obvious wrong (but I'm no expert). Let me know what logs you need. Thanks again.

              Comment


                Originally posted by Fabrini View Post
                Squeezelite network issue on Windows - Solved?

                Hi Greg

                I'm a keen user of your Squeezebox client

                As I'm sure you know, squeezelite on Windows has a bit of a connectivity issue, which Squeezelite-X I think inherited. A solution at long last was found for this as recent as last week:

                see github.com/ralph-irving/squeezelite/commit/226efa300c4cf037e8486bad635e9deb3104636f

                Will you pick this fix up in any upcoming versions of your client on Windows?

                Thanks much
                Sure thing. Downloading new squeezelite client now. I'll repackage and upload to store tonight. (Have been out of town last week).

                R Greg Dawson
                Squeezelite-X

                Comment


                  Originally posted by NAG View Post

                  Hi Greg - I tried this. Tried reinstalling both stand alone & windows store versions. Music plays but the interface continues to just show blue quaver logo, squeezelite-X and a rotating white ring on black background. No issues accessing the LMS interface via browser (on port :9000/Material). FYI, running latest LMS Version: 8.3.0 - 1667251155 from lmscommunity on DSM 7.1.1-42962 Update 1 in a docker container.

                  I tried usign Recuva Unistaller too, this just picked up the same key I had already found before, not a solution for me.

                  Any ideas?
                  It might have something to do with the docker container. I seem to recall another user having an issue with a docker container and discovery wrt to either IP addresses or ports. It was awhile ago and I don't recall what he did to solve the problem, but I think it had something to do with the docker container configuration and LMS port config setup or docker port mapping of some kind. I'd have to go find it and see if it applies as I don't recall precisely. Not sure.

                  Here is what SLX does in any case: SLX uses the discovery protocol to discover the server(s) on your network. If the server you enter is discoverable then the discovery process tells SLX the CLI/Telnet port the server is using (usually 9090). Otherwise, you would have to enter the CLI/Telnet port (defaults to 9090, but you can change it). SLX then connects to the Telnet port. If that fails, then you'll see an error message. If CLI/Telnet succeeds, then SLX uses the CLI interface to query the LMS server for the http port it is using (usually 9000). SLX expects the HTTP interface to work if it was able to connect via CLI/Telnet and successfully get the http port to use. SLX will then fire up the squeezelite player (wait for it to connect to the server) and then load the URL into the browser. When the load process starts, you see the spinning progress indicator. When SLX receives a message from the internal browser that it is done loading the url, it makes the browser window visible.

                  It seems in your case, discovery, CLI/Telnet, the query for the http port appears to succeed, but SLX never gets a message from the browser saying the url navigation is complete. I could confirm that with detailed logging info.

                  That's all I can think of for now.

                  R Greg Dawson

                  Squeezelite-X

                  Comment


                    Originally posted by rgdawson View Post

                    It might have something to do with the docker container. I seem to recall another user having an issue with a docker container and discovery wrt to either IP addresses or ports. It was awhile ago and I don't recall what he did to solve the problem, but I think it had something to do with the docker container configuration and LMS port config setup or docker port mapping of some kind. I'd have to go find it and see if it applies as I don't recall precisely. Not sure.

                    Here is what SLX does in any case: SLX uses the discovery protocol to discover the server(s) on your network. If the server you enter is discoverable then the discovery process tells SLX the CLI/Telnet port the server is using (usually 9090). Otherwise, you would have to enter the CLI/Telnet port (defaults to 9090, but you can change it). SLX then connects to the Telnet port. If that fails, then you'll see an error message. If CLI/Telnet succeeds, then SLX uses the CLI interface to query the LMS server for the http port it is using (usually 9000). SLX expects the HTTP interface to work if it was able to connect via CLI/Telnet and successfully get the http port to use. SLX will then fire up the squeezelite player (wait for it to connect to the server) and then load the URL into the browser. When the load process starts, you see the spinning progress indicator. When SLX receives a message from the internal browser that it is done loading the url, it makes the browser window visible.

                    It seems in your case, discovery, CLI/Telnet, the query for the http port appears to succeed, but SLX never gets a message from the browser saying the url navigation is complete. I could confirm that with detailed logging info.

                    That's all I can think of for now.

                    R Greg Dawson
                    I had similar/same issue.
                    For me, it was too difficult a password, which SLX subsequently failed to communicate to display the site. There was no problem in the first setup step.

                    Maybe this will help someone.​

                    Example of password: zVT562#jJyez#f!ohUEAceXf

                    ---

                    Thanks for the great app!

                    Comment


                      Hi Greg,
                      I have a found a minor issue when using the Visual Statistics plugin with material skin via Squeezelite-X, detalis here:

                      https://forums.slimdevices.com/forum...13#post1626113

                      It seems to be SLX related, I wonder if you could take a look?

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

                        I had similar/same issue.
                        For me, it was too difficult a password, which SLX subsequently failed to communicate to display the site. There was no problem in the first setup step.

                        Maybe this will help someone.​

                        Example of password: zVT562#jJyez#f!ohUEAceXf

                        ---

                        Thanks for the great app!
                        singularita, thank you for posting this, you have saved the day! Indeed, I can reproduce the problem with that password. I have a fix (encoding issue), will submit/upload shortly. I don't know how you figured that out, but I am glad you did, thanks.

                        R Greg Dawson
                        Squeezelite-X

                        Comment


                          New Version 2.11.34 submitted/uploaded

                          Changes:
                          • Squeezelite player updated to version v1.9.9-1419
                          • Fix encoding issue in passing username/password to LMS server
                          • Add support for older Denon AVR's (e.g. pre "X" series before year 2012)

                          R Greg Dawson
                          Squeezelite-X

                          Comment


                            Originally posted by rgdawson View Post
                            New Version 2.11.34 submitted/uploaded

                            Changes:
                            • Add support for older Denon AVR's (e.g. pre "X" series before year 2012)

                            R Greg Dawson
                            Looking forward to trying this out, Greg!
                            Sam

                            Comment


                              Originally posted by SamY View Post

                              Looking forward to trying this out, Greg!
                              I dug up an old Denon AVR-3311 and figured out how to query it and send commands via http instead of TelNet. The XML endpoints and structure is a little different for Pre "X" models. I'm not sure how old it can go, but I think if the AVR supports DLNA discovery then it should work.
                              Squeezelite-X

                              Comment


                                Originally posted by rgdawson View Post

                                I dug up an old Denon AVR-3311 and figured out how to query it and send commands via http instead of TelNet. The XML endpoints and structure is a little different for Pre "X" models. I'm not sure how old it can go, but I think if the AVR supports DLNA discovery then it should work.
                                As luck would have it, mine is an AVR-3311CI. I will be doing some testing later today.

                                Btw, did you ever have a chance to check out the Denon AVR Control plugin's "Denon/Marantz AVR Settings" menus under Material Skin's player settings? While the menus do utilize the telnet protocol, they can be accessed and used independently of the plugin's player-controlled power and volume control functions, although only for AVR's that are associated with an LMS player via the plugin's setup menu. And with the new multi-zone support selected in the setup menu, each zone of the AVR can now also be individually powered on/off and controlled through the menus.

                                (This is the last time I'll nag you about trying this. I promise.)
                                Sam

                                Comment

                                Working...
                                X