Announcement

Collapse
No announcement yet.

[Announce] Community Firmware for Squeezebox Radio/Touch/Controller and LMS 8

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Originally posted by Shozzer
    Yes, it is catchy - it's just a bit too catchy to wake up to, particular when my SO wants to continue her sleep! Thanks for the link, I had not seen it before.
    It does the job though. Nobody sleeps through that alarm [emoji1787]

    Sent from my Pixel 3a using Tapatalk
    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
      It does the job though. Nobody sleeps through that alarm [emoji1787]

      Sent from my Pixel 3a using Tapatalk
      True. But to weigh in, I'd prefer a slightly more laid back fallback alarm as well.


      Gesendet von iPad mit Tapatalk

      Comment


      • Originally posted by pputzer
        True. But to weigh in, I'd prefer a slightly more laid back fallback alarm as well.


        Gesendet von iPad mit Tapatalk
        I think the file can be replaced if you SSH into the Radio. I am sure it has been discussed before. This link shows where the file is located.


        Sent from my Pixel 3a using Tapatalk
        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
          Which units and which SD cards?

          Sent from my Pixel 3a using Tapatalk
          I have VIDABOX OpenSqueeze device, 6 of them are not booting when powerup. each device has a Micro SD card on it, i removed a SD card from a working device and put to the none working ones. when i do that it boots properly. so i believe its the issue with SD card. but um not sure. kindly advise me what should i do now?

          Comment


          • Originally posted by nxavier
            I have VIDABOX OpenSqueeze device, 6 of them are not booting when powerup. each device has a Micro SD card on it, i removed a SD card from a working device and put to the none working ones. when i do that it boots properly. so i believe its the issue with SD card. but um not sure. kindly advise me what should i do now?
            First guess is copy the working SD card to a PC/MAC and then write it back to new SD cards and put them into your old non-working players.
            SD card copiers such as balenaEtcher would probably work.
            If they get the MAC address from the hardware rather than something on the SD card then that is probably all that you have to do on the device.
            If that does not work or you need more help then start a new thread with "Vidabox" somewhere in the subject since this thread (and the other that you posted in) is nothing to do with the Vidabox device (which is no longer listed on their web site).
            Paul Webster
            Author of "Now Playing" plugins covering Radio France (FIP etc), PlanetRadio (Bauer - Kiss, Absolute, Scala, JazzFM etc), KCRW, ABC Australia and CBC/Radio-Canada
            and, via the extra "Radio Now Playing" plugin lots more - see https://forums.slimdevices.com/showt...Playing-plugin

            Comment


            • Originally posted by mherger
              > So, I guess I have to update Ubuntu? Because I see version 2.067-1 only
              > for Ubuntu 20.04.


              Some people have had success updating using CPAN

              perl -MCPAN -e shell
              install IO::Socket::SSL

              --

              Michael
              I'm on a Raspberry with Max2Play installed. Ive tried the sudo apt and CPAN options.
              First option says its up to date, CPAN says on version 2.068.
              LMS info screen states: IO::Socket::SSL 2.002.......not sure how to solve.
              Logging shows same download errors on new firmware as others have experienced.

              any tips/suggestions how to update IO::Socket::SSL alternatively?

              Comment


              • Originally posted by MPO
                I'm on a Raspberry with Max2Play installed. Ive tried the sudo apt and CPAN options.
                First option says its up to date, CPAN says on version 2.068.
                LMS info screen states: IO::Socket::SSL 2.002.......not sure how to solve.
                Logging shows same download errors on new firmware as others have experienced.

                any tips/suggestions how to update IO::Socket::SSL alternatively?

                Are you sure you are up to date ?

                Max2Play
                Version 2.53
                Raspberry PI 3b+
                L
                ogitech Media Server Version: 8.1.1 - 1609139162 @ Mon Dec 28 08:38:56 CET 2020
                Hostname: max2play
                Server IP Address: 192.168.1.***
                Server HTTP Port Number: 9000
                Operating system: Debian - EN - utf8
                Platform Architecture: armv7l-linux
                Perl Version: 5.28.1 - arm-linux-gnueabihf-thread-multi-64int
                Audio::Scan: 1.02
                IO::Socket::SSL: 2.060
                Database Version: DBD::SQLite 1.58 (sqlite 3.22.0)
                Total Players Recognized: 0

                Comment


                • Originally posted by MPO
                  I'm on a Raspberry with Max2Play installed. Ive tried the sudo apt and CPAN options.
                  First option says its up to date, CPAN says on version 2.068.
                  LMS info screen states: IO::Socket::SSL 2.002.......not sure how to solve.
                  Logging shows same download errors on new firmware as others have experienced.

                  any tips/suggestions how to update IO::Socket::SSL alternatively?
                  How old is your Max2Play? It could be based on Debian Wheezy, Jessie, Stretch or Buster depending on when it was downloaded.

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

                  Comment


                  • Originally posted by mrw
                    I suspect that space is not the issue, but processing power may be.

                    The Radio's hardware chip does provide for some basic DSP, and it is not used. There is a preconfigured (closed source) software DSP component in the Radio's ALSA chain, which is rather betterer than that, and is probably responsible for the quality of the sound output.

                    I have contemplated the idea of implementing a basic 'bass cut' filter on the hardware chip to quell the occasional sense of "baritone boom" that I hear. Or perhaps one might want a step/baffle type filter to deal with being placed close to a wall. But UI becomes an issue, and I am no audio engineer, so I don't know what curves one might want.

                    I did suss out the DSP filtering actually in use:


                    Perhaps, one day, it could be reimplemented along the lines you suggest. I don't have a Boom, but one of its features is, I think, to automatically extend bass response when volume levels allow. The Radio clearly owes much to the Boom in its audio design, but that feature was not included. It might be nice to have. There again, the risk of overloading the bass driver must increase !
                    Thanks mrw. I do remember your promising post about the DSP filter coefficients. If processing power in the Radio is the issue, then tweaking those filter coefficients in the hardware seems like a useful alternative. I'm sure the Radio has an admirably flat response curve, but I'm not afraid to admit that I'm not a big fan of a flat response curve in all situations! My own personal preference with most audio devices is to try and cut the mid range a bit compared to the bass and (especially) the high frequency components. I believe this is called the 'Rock Smile' :-) The Boom and the Radio seem to have the same driver units (the bass driver certainly, not sure about the tweeter), but to my ears the Boom can be made to sound a lot better, by boosting the bass a little and the treble a little more.

                    I'm not sure what's involved in using Ghidra, but if a Boom would be any use to you in seeing what's been done in its DSP then I'll happily donate one to the cause - just PM me if you want one of my 'spares awaiting refurbishment'.

                    Comment


                    • Originally posted by Man in a van
                      Are you sure you are up to date ?


                      L
                      Click image for larger version

Name:	Schermafbeelding 2020-12-31.png
Views:	1
Size:	12.2 KB
ID:	1570783

                      I believe so :-)

                      LMS gives me:

                      Logitech Media Server Versie: 8.1.1 - 1609139162 @ Mon Dec 28 08:38:56 CET 2020
                      Hostnaam: Hifi
                      IP-adres van server: 192.168.1.***
                      HTTP-poortnummer van server: 9000
                      Besturingssysteem: Debian - NL - utf8
                      Platformarchitectuur: armv7l-linux
                      Perl-versie: 5.20.2 - arm-linux-gnueabihf-thread-multi-64int
                      Audio::Scan: 0.95
                      IO::Socket::SSL: 2.002
                      Databaseversie: DBD::SQLite 1.58 (sqlite 3.22.0)
                      Totaalaantal herkende muziekspelers: 9

                      on a Pi 3B running:
                      ### LINUX-VERSION ####
                      Distributor ID: Raspbian
                      Description: Raspbian GNU/Linux 8.0 (jessie)
                      Release: 8.0
                      Codename: jessie
                      Last edited by MPO; 2020-12-31, 12:53.

                      Comment


                      • Originally posted by MPO
                        [ATTACH]32743[/ATTACH]

                        I believe so :-)

                        LMS gives me:

                        Logitech Media Server Versie: 8.1.1 - 1609139162 @ Mon Dec 28 08:38:56 CET 2020
                        Hostnaam: Hifi
                        IP-adres van server: 192.168.1.***
                        HTTP-poortnummer van server: 9000
                        Besturingssysteem: Debian - NL - utf8
                        Platformarchitectuur: armv7l-linux
                        Perl-versie: 5.20.2 - arm-linux-gnueabihf-thread-multi-64int
                        Audio::Scan: 0.95
                        IO::Socket::SSL: 2.002
                        Databaseversie: DBD::SQLite 1.58 (sqlite 3.22.0)
                        Totaalaantal herkende muziekspelers: 9

                        on a Pi 3B running:
                        ### LINUX-VERSION ####
                        Distributor ID:Raspbian
                        Description:Raspbian GNU/Linux 8.0 (jessie)
                        Release:8.0
                        Codename:jessie
                        Jessie is 5 years old. It might be worth downloading a new Max2Play image.

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

                        Comment


                        • @MPO


                          As Slarti says, get up to date with Buster

                          [URL]https://www.max2play.com/en/download/46152/[/URL

                          groetjes

                          ronnie

                          Comment


                          • Ok, thanks for the suggestion guys!

                            In order not to have to reconfigure all server settings (and for all 9 players..) is there a way to save all plugins and all settings from the current install and reinstate them once the buster version is there?
                            Max2play has a save LMS settings function (it provides a 190mb tar file in my situation). Would that work or do you know of better alternatives?

                            regards/groeten!

                            Comment


                            • Originally posted by MPO
                              Ok, thanks for the suggestion guys!

                              In order not to have to reconfigure all server settings (and for all 9 players..) is there a way to save all plugins and all settings from the current install and reinstate them once the buster version is there?
                              Max2play has a save LMS settings function (it provides a 190mb tar file in my situation). Would that work or do you know of better alternatives?

                              regards/groeten!
                              I found this

                              Hello I am currently running M2P on a Pi 3 version 2.5 on Jessie. I want to upgrade to the latest Buster version and may even bite the bullet and purchase a Pi 4 in the near future. It is used only as a LMS server (7.9.2 – 1560759832) and connects to my music which


                              I do think the M2P have dropped the ball of late (well for quite a while actually )

                              I would suggest:

                              Mahe a copy of your current install using Win32Disk Imager, Apple piBaker or even install Raspberry PI OS on a spare card and use the Image copier facility

                              Use the method described by garym, elsewhere to copy your "favs and prefs" just incase.

                              Whenyou have a copy of the OS you are now using, burn that to a spare card (maybe Santa left a few) for the exercise.

                              Good Luck

                              ronnie

                              Comment


                              • Originally posted by chill
                                Thanks mrw. I do remember your promising post about the DSP filter coefficients. If processing power in the Radio is the issue, then tweaking those filter coefficients in the hardware seems like a useful alternative. I'm sure the Radio has an admirably flat response curve, but I'm not afraid to admit that I'm not a big fan of a flat response curve in all situations! My own personal preference with most audio devices is to try and cut the mid range a bit compared to the bass and (especially) the high frequency components. I believe this is called the 'Rock Smile' :-) The Boom and the Radio seem to have the same driver units (the bass driver certainly, not sure about the tweeter), but to my ears the Boom can be made to sound a lot better, by boosting the bass a little and the treble a little more.

                                I'm not sure what's involved in using Ghidra, but if a Boom would be any use to you in seeing what's been done in its DSP then I'll happily donate one to the cause - just PM me if you want one of my 'spares awaiting refurbishment'.
                                Thank you for the offer ! At this stage, for me to accept it would be to promise way too much.
                                But your post is a timely reminder that just because I think the Radio may lack the power to do much more doesn't mean that it can't...

                                It is worth looking over the possibilities already available, I'm sure life has moved on in the open source world since the Radio firmware was made. I'll look at the pCP offering. And I think @ralphy might have been thinking in that direction.

                                As I don't have a Boom, can you point me at a manual that describes the treble/bass settings available ?

                                In the meantime, I'll practice my "Rock Smile". A new term to me, opinions seem to differ. But I think in reality it may no more or less than what used to be called a "Contour" control. Or do I mean "Tilt" ?

                                But perhaps a small project for the hardware...

                                Comment

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