Re: [slim] New approach to dead Boom / SB3 (Classic) / Transporter

2022-11-29 Thread alfista


Curious, what's the model number of the device?



alfista's Profile: http://forums.slimdevices.com/member.php?userid=32396
View this thread: http://forums.slimdevices.com/showthread.php?t=117140

___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/discuss


Re: [slim] Darko Audio's recent video tribute to the Squeezebox (GOAT)

2022-11-29 Thread philippe_44


Do you think I should offer him to try a SqueezeAMP? It's tempting but
first it is not a commercial venture (by no means) and second, it is
very unlikely going to fit his expectations of audio quality so it might
be a waste of time with frustration for everybody.



LMS 8.2 on Odroid-C4 - *SqueezeAMP!*, 5xRadio, 5xBoom, 2xDuet, 1xTouch,
1xSB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW,
2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi,  Yamaha
WX-010, AppleTV 4, Airport Express, GGMM E5, RivaArena 1 & 3

philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261
View this thread: http://forums.slimdevices.com/showthread.php?t=117071

___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/discuss


Re: [slim] New modified SqueezeAMP batch?

2022-11-29 Thread philippe_44


MrC wrote: 
> If you have an extra, I would be interested in one.  I'd like to have a
> modern unit to eventually replace a Touch, should one of my 2 devices
> succumb to old age.  I'd like to get a head start coming up to speed on
> the requirements for such a unit.
> 
> I'm not concerned about the cost.  I'd need simultaneous optical and RCA
> out, Ethernet, but don't care about WiFi.  I almost never look at the
> display since it lives in my server cabinet with the whole house audio
> amps and other equipment.  Any reasonable case would be fine.  I run LMS
> on my Mac.
> 
> I'm not a hardware guy, and although competent enough to do assembly,
> I'd prefer to avoid breaking out in cold sweats trying to do anything
> more than snapping parts together and basic wiring.
> 
> I've read through this thread, and the others, but still feel uncertain
> enough that I need to ask - would this unit meet these needs, and what
> would you recommend?

If you need Ethernet, then the SqueezeAMP is not going to work without a
fair bit of hardware tinkering, so I would not recommend it



LMS 8.2 on Odroid-C4 - *SqueezeAMP!*, 5xRadio, 5xBoom, 2xDuet, 1xTouch,
1xSB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW,
2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi,  Yamaha
WX-010, AppleTV 4, Airport Express, GGMM E5, RivaArena 1 & 3

philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261
View this thread: http://forums.slimdevices.com/showthread.php?t=116084

___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/discuss


Re: [slim] New approach to dead Boom / SB3 (Classic) / Transporter

2022-11-29 Thread philippe_44


JoeMuc2009 wrote: 
> Hi all,
> 
> just wanted to let you know that I had some interesting experiences
> recently. It started with a shock when once again I had done SMD
> capacitor replacement on multiple SB3s and the dropout rate was extreme.
> Five separate devices, all would boot but crash and reboot once they
> were commanded to start playback. Three of them "died" somewhere between
> the moment I detached the CPU board to do the capacitor replacement and
> the moment I put it back together to test. Three! They would do what
> every dead SB3 does, show a very dim TOSLINK, no connectivity, no
> display. And that despite the fact I hardly ever touched the CPU board
> at all.
> I still can't explain how it got to this three times in a row  (even
> five times in a row earlier which had me  so depressed I would almost
> quit). I wore a grounding wrist strap all the time. I discharged the
> capacitors before replugging the CPU board. Used current limiting for
> the first startup to ensure that a short won't blow anything up. Used an
> IR camera to look for hotspots during powerup. So that was a bit
> awkward. The devices were sent to me for repair and shortly after the
> repair they would fail and be much worse than they initially were. One
> of them had run a firmware update, then restarted and was normal for a
> short period of time before it failed. Which brought me to an idea.
> Just out of curiosity I extracted the Flash EEPROM from one of them and
> put it in my reader. Compared to a known-working SB3 there were a lot of
> differences, at least in the first blocks and, expectedly, where the
> configuration is held. But I would not assume that the bootloader or
> whatever is read first from the Flash is very different between
> identical devices. So I attempted to flash the working image to the
> EEPROM that was suspected corrupt, with erase first and eventual
> verification of course to ensure that it isn't the chip itself that is
> at fault. Then soldered the chip back in and, what do you know, two out
> of three SB3s were recovered! A Boom PCB is under repair currently, I'll
> try the same thing there as the hardware arrangement around the CPU is
> similar to that of the SB3. It looks like what I used to call "CPU
> death" actually isn't the CPU but the Flash memory for some reason. I
> don't know why it happens. It should only be written to during
> configuration and during firmware updates, but something during the
> repair seems to cause a partial corruption. It's a pity that the EEPROM
> needs to be desoldered and put back in place as this can only be done
> once or twice before the board gets damaged. But it's way better than
> attempting to reflow the CPU which I never succeeded at, and most of the
> time it might not even be the component at fault. The EEPROM is not easy
> to handle thanks to its 0.5mm (or so) pin pitch but way easier than the
> BGA stuff under the CPU.
> I have too little experience yet to document this or proclaim it as one
> of the first measures to fix, and due to the complexity of the operation
> it should rather be considered a last stand, but still. There is a lot
> of new hope for the stack of failed SB3s and Booms I have around, and
> I'll let you know how I fare with it.
> 
> Cheers,
> Joe

That's excellent news! I wrongly thought that you already compared flash
content in the past. I don't have my programmer here but I'll try as
soon as I can get it



LMS 8.2 on Odroid-C4 - *SqueezeAMP!*, 5xRadio, 5xBoom, 2xDuet, 1xTouch,
1xSB3. Sonos PLAY:3, PLAY:5, Marantz NR1603, Foobar2000, ShairPortW,
2xChromecast Audio, Chromecast v1 and v2, Squeezelite on Pi,  Yamaha
WX-010, AppleTV 4, Airport Express, GGMM E5, RivaArena 1 & 3

philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261
View this thread: http://forums.slimdevices.com/showthread.php?t=117140

___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/discuss


Re: [slim] Darko Audio's recent video tribute to the Squeezebox (GOAT)

2022-11-29 Thread Fahzz


Also don't forget that we also have this vital forum and community of
music fans, hi-fi enthusiasts and technology hobbyists that keeps our
Squeezeboxen running!



Pi4 w/Allo Boss 2 Player (Wired), Max2Play w/LMS Server 8.2
Router: Netgear R700P
File Storage: Samsung T5 SSD
Music Service: Qobuz
Logitech Boom

Fahzz's Profile: http://forums.slimdevices.com/member.php?userid=12585
View this thread: http://forums.slimdevices.com/showthread.php?t=117071

___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/discuss


Re: [slim] Darko Audio's recent video tribute to the Squeezebox (GOAT)

2022-11-29 Thread ModelCitizen


mightaswell wrote: 
> 
> I could rant and rave about how happy I am I got into LMS.

So could I but I'm a little understated.



Take care of your tongue. It is in a wet place and can easily slip.

Lounge: Naim NDX with Touch as controller, Naim NAP 180, NAC 82, NAPSC,
HiCap, Shahinian Arc speakers
Kitchen/outside: Chromecast audio, Azatom iBigBoy 2 (500W)
And... SB+, radios & tons of Chromecasts... all run from LMS and
controlled via Material Skin on any nearby device and a couple of
Touchs.

ModelCitizen's Profile: http://forums.slimdevices.com/member.php?userid=446
View this thread: http://forums.slimdevices.com/showthread.php?t=117071

___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/discuss


Re: [slim] Darko Audio's recent video tribute to the Squeezebox (GOAT)

2022-11-29 Thread amey01


mightaswell wrote: 
> Coming from someone without any Squeezebox hardware, not only does LMS
> serve as an economical alternative to Roon, it also beats Roon in a few
> areas.
> 

It beats Roon in virtually every area.

The only obvious advantage of Roon is (slightly) less requirement for
technical nous. 

LMS does require a very small amount of technical ability in terms of
installing plugins, configuring them to work together, building RasPi
endpoints from PiCorePlayer, etc. 

Roon has got "plug 'n' play" a little more polished. 

But that's it as far as I'm concerned!



amey01's Profile: http://forums.slimdevices.com/member.php?userid=11274
View this thread: http://forums.slimdevices.com/showthread.php?t=117071

___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/discuss


[slim] New approach to dead Boom / SB3 (Classic) / Transporter

2022-11-29 Thread JoeMuc2009


Hi all,

just wanted to let you know that I had some interesting experiences
recently. It started with a shock when once again I had done SMD
capacitor replacement on multiple SB3s and the dropout rate was extreme.
Five separate devices, all would boot but crash and reboot once they
were commanded to start playback. Three of them "died" somewhere between
the moment I detached the CPU board to do the capacitor replacement and
the moment I put it back together to test. Three! They would do what
every dead SB3 does, show a very dim TOSLINK, no connectivity, no
display. And that despite the fact I hardly ever touched the CPU board
at all.
I still can't explain how it got to this three times in a row  (even
five times in a row earlier which had me  so depressed I would almost
quit). I wore a grounding wrist strap all the time. I discharged the
capacitors before replugging the CPU board. Used current limiting for
the first startup to ensure that a short won't blow anything up. Used an
IR camera to look for hotspots during powerup. So that was a bit
awkward. The devices were sent to me for repair and shortly after the
repair they would fail and be much worse than they initially were. One
of them had run a firmware update, then restarted and was normal for a
short period of time before it failed. Which brought me to an idea.
Just out of curiosity I extracted the Flash EEPROM from one of them and
put it in my reader. Compared to a known-working SB3 there were a lot of
differences, at least in the first blocks and, expectedly, where the
configuration is held. But I would not assume that the bootloader or
whatever is read first from the Flash is very different between
identical devices. So I attempted to flash the working image to the
EEPROM that was suspected corrupt, with erase first and eventual
verification of course to ensure that it isn't the chip itself that is
at fault. Then soldered the chip back in and, what do you know, two out
of three SB3s were recovered! A Boom PCB is under repair currently, I'll
try the same thing there as the hardware arrangement around the CPU is
similar to that of the SB3. It looks like what I used to call "CPU
death" actually isn't the CPU but the Flash memory for some reason. I
don't know why it happens. It should only be written to during
configuration and during firmware updates, but something during the
repair seems to cause a partial corruption. It's a pity that the EEPROM
needs to be desoldered and put back in place as this can only be done
once or twice before the board gets damaged. But it's way better than
attempting to reflow the CPU which I never succeeded at, and most of the
time it might not even be the component at fault. The EEPROM is not easy
to handle thanks to its 0.5mm (or so) pin pitch but way easier than the
BGA stuff under the CPU.
I have too little experience yet to document this or proclaim it as one
of the first measures to fix, and due to the complexity of the operation
it should rather be considered a last stand, but still. There is a lot
of new hope for the stack of failed SB3s and Booms I have around, and
I'll let you know how I fare with it.

Cheers,
Joe



PN me if your Boom / Classic / Transporter display has issues!

Blog:
https://www.blogger.com/blogger.g?rinli=1=1=5053304027701850753#allposts

JoeMuc2009's Profile: http://forums.slimdevices.com/member.php?userid=23131
View this thread: http://forums.slimdevices.com/showthread.php?t=117140

___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/discuss


Re: [slim] Darko Audio's recent video tribute to the Squeezebox (GOAT)

2022-11-29 Thread mightaswell


Coming from someone without any Squeezebox hardware, not only does LMS
serve as an economical alternative to Roon, it also beats Roon in a few
areas.

UPNP/DLNA RENDERER COMPATIBILITY
Lots of good audio hardware out there that only supports UPnP streaming.
Generally, the user experience controlling these devices ranges from
acceptable to infuriatingly awful, particularly on iOS. LMS allows us to
ditch ugly, poorly implemented OEM apps, and featureless, aging
third-party controllers, and instead use Material UI, a centralized
library, and standard playlists. While Roon intentionally does not
support these endpoints for dogmatic reasons, the fact is that there is
a very strong use-case for the Roon-like experience while streaming to a
single device, bit-perfectly. And on many devices that support Airplay
and UPnP (HEOS for one), only UPnP will allow hi-res and DSD, whereas
the "Roon tested" workaround using Airplay will not.

MULTI-ENDPOINT
Continuing the previous point, LMS is nearly agnostic when it comes to
endpoints. I haven't found another system that will "bridge" this
variety of endpoints, not only allowing music to be played on a variety
of hardware, but exposing that hardware into other ecosystems (like
creating an Airplay speaker from a chromecast, or UPnP renderer from an
airport express.)

I can't stress this point enough. Running LMS allows my family to use
Apple Music on Airplay speakers around the house, while allowing me to
stream local content to those same speakers. In comparison to literally
any other multi-room system, either DIY (snapcast, Volumio) or
off-the-shelf (Sonos, HEOS, MusiCast), I'm not locked into any one
vendor and can simply piggyback off existing speakers. I find that
airplay + LMS is a great match for setting up whole home audio on the
cheap.


I could rant and rave about how happy I am I got into LMS. Hopefully
it's around a long time.



mightaswell's Profile: http://forums.slimdevices.com/member.php?userid=71951
View this thread: http://forums.slimdevices.com/showthread.php?t=117071

___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/discuss


Re: [slim] text editor in piCore

2022-11-29 Thread strebor56


The secret to getting to love vi is to use ed for a few days:rolleyes:

Nano is available as an extension for those sick of typing q!

Bonne chance S



strebor56's Profile: http://forums.slimdevices.com/member.php?userid=65828
View this thread: http://forums.slimdevices.com/showthread.php?t=117137

___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/discuss