[SlimDevices: Radio] Bass amp problem

[philippe_44]

Hi - i'm having the same problem on almost all my Radio(s): from time to
time (especially after a pause/ resume) all bass-medium are gone which
seems to indicate that the amp in charge of bass-medium speaker drive is
off and does not resume. A power cycle solves the problem, but this is a
bit strange. Am I the only to observe that ?



LMS 7.7.2 - 5 radio, 3 Boom, 4 Duet, 1 Touch, 1 SB2. Sonos 2xPLAY:1,
PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBMC, Foobar2000, XBoxOne
(sort of)
------------------------------------------------------------------------
philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[reinholdk]

never experienced this on my Radios...


------------------------------------------------------------------------
reinholdk's Profile: http://forums.slimdevices.com/member.php?userid=36070
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[slartibartfast]

Hi - I'm having a problem on almost all my Radio(s): from time to time
(especially after a pause/ resume) all bass-medium are gone which seems
to indicate that the amp in charge of bass-medium speaker drive is off
and does not resume. A power cycle solves the problem, but this is a bit
strange. Am I the only to observe that ?

No, I've noticed this a few times on my newer white radio. Never on my
black radio. It seems to happen when the battery is low but that may be
coincidence. The black radio is normally plugged in and the white radio
is always used on battery which fits the low battery theory.




------------------------------------------------------------------------
slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[philippe_44]

Post by slartibartfast
No, I've noticed this a few times on my newer white radio. Never on my
black radio. It seems to happen when the battery is low but that may be
coincidence. The black radio is normally plugged in and the white radio
is always used on battery which fits the low battery theory.

Mines do that unfortunately whether they are on battery or plugged



LMS 7.7.2 - 5 radio, 3 Boom, 4 Duet, 1 Touch, 1 SB2. Sonos 2xPLAY:1,
PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBMC, Foobar2000, XBoxOne
(sort of)
------------------------------------------------------------------------
philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[Mnyb]

Post by philippe_44
Mines do that unfortunately whether they are on battery or plugged

A battery problem ? Does it happen often enough so that you can
experiment with removing the battery pack from a radio and notice any
differences ?



--------------------------------------------------------------------
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x
MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100 +Rel Stadium 3
sub.
Bedroom/Office: Boom
Kitchen: Touch + powered Fostex PM0.4
Misc use: Radio (with battery)
iPad1 with iPengHD & SqueezePad
(spares Touch, SB3, reciever ,controller )
server HP proliant micro server N36L with ClearOS Linux

http://people.xiph.org/~xiphmont/demo/neil-young.html
------------------------------------------------------------------------
Mnyb's Profile: http://forums.slimdevices.com/member.php?userid=4143
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[philippe_44]

Post by Mnyb
A battery problem ? Does it happen often enough so that you can
experiment with removing the battery pack from a radio and notice any
differences ?

I'll try as it happens frequently enough. The battery is fine, though,
as they all run for hours on battery if needed



LMS 7.7.2 - 5 radio, 3 Boom, 4 Duet, 1 Touch, 1 SB2. Sonos 2xPLAY:1,
PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBMC, Foobar2000, XBoxOne
(sort of)
------------------------------------------------------------------------
philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[chris67]

I'm having the same problem with my Logitech UE radio (reverted to
Squeezebox mode, firmware 7.7.3-r16676). I started playing music
yesterday forgetting I had headphones plugged in. I removed headphones
without stopping the music and ever since, no bass.

I've tried:


- Rebooting the radio (numerous times)
- Removing and reinserting battery
- Performing software update
- Restore factory settings
- Restoring backup copy of server.prefs file

The tinny sound remains whatever I do and it makes no difference whether
the radio's playing through it's own speaker or through headphones.

Any advice/suggestions gratefully received.

Cheers

Chris



It's like, how much more black could this be? And the answer is none.
None more black.
------------------------------------------------------------------------
chris67's Profile: http://forums.slimdevices.com/member.php?userid=19448
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[chris67]

Working perfectly now. The drums kicking in on Metallica's "Enter
Sandman" proved that. Weird. I was sure it consistently sounded wrong
several days ago. Placebo effect?



It's like, how much more black could this be? And the answer is none.
None more black.
------------------------------------------------------------------------
chris67's Profile: http://forums.slimdevices.com/member.php?userid=19448
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[philippe_44]

Post by chris67
Working perfectly now. The drums kicking in on Metallica's "Enter
Sandman" proved that. Weird. I was sure it consistently sounded wrong
several days ago. Placebo effect?

I don't think its placebo - it happens once every other week on most of
my Radios



LMS 7.7.5 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos 2xPLAY:1,
PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBMC, Foobar2000, XBoxOne,
JRiver 21, Chromecast Audio, Chromecast v1, Pi B2, Pi B+, 2xPi A+,
Odroid-C1, Cubie2
------------------------------------------------------------------------
philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[markr]

Post by philippe_44
I don't think its placebo - it happens once every other week on most of
my Radios

Yeah, I have it once in a while, since I bought the unit severals years
ago. I get the feeling it recently got worse. Alas, no one seem to have
found a solution. So I reboot the radio and it will work fine again for
some time.



Mark Ruys
------------------------------------------------------------------------
markr's Profile: http://forums.slimdevices.com/member.php?userid=422
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[Humpfrid]

I have the same kind of problem on my radio. Seems it only happens on
the SB software and not UE software

Skickat från min D5803 via Tapatalk




------------------------------------------------------------------------
Humpfrid's Profile: http://forums.slimdevices.com/member.php?userid=66300
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[Mushroom_3]

I'm wondering if anyone has found a solution to this problem.

I have 3 radios; One has had this problem for a couple of months and
another (a UE conversion) has just started showing the same symptoms.
The third is fine.

I can cure it by rebooting as stated above and the sound goes tinny
again usually after I touch another button i.e. another preset or the
back button. I'm no expert but it seems to me to be software related.

Very annoying as the Radio (the portable aspect) is the one model of SB
hardware that can't be replaced by a RPi or such.


------------------------------------------------------------------------
Mushroom_3's Profile: http://forums.slimdevices.com/member.php?userid=13434
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[StephenC]

Hi,

I'm also getting this on at least two SB Radios. Could be software. Or
perhaps capacitors drying out? No idea. A power cycle fixes it, but it's
quite annoying. Doesn't happen on my Touches, Booms or SB3s. Only the
Radio.

Stephen.


------------------------------------------------------------------------
StephenC's Profile: http://forums.slimdevices.com/member.php?userid=63278
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[mrw]

The problem seems to have 'gone away' for me. But I can't be sure, it
was always relatively infrequent. Too infrequent to keep notes.

I have two radios, both of which exhibited it.


------------------------------------------------------------------------
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[slartibartfast]

Post by mrw
The problem seems to have 'gone away' for me. But I can't be sure, it
was always relatively infrequent. Too infrequent to keep notes.
I have two radios, both of which exhibited it.It seems fairly random. It may happen every day for a week now. Mine

have not suffered recently either, but just like the failure to charge
after plugging in the power connector it is waiting to bite you.[emoji3]

Sent from my SM-G900F using Tapatalk




------------------------------------------------------------------------
slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[agbagb]

Just thought I'd keep this thread live..... Had the same problem today
for the very first time with one of the Radios (SB/LMS; White). It had a
battery which is fully charged: it usually runs off the mains anyway. A
Power Cycle fixed the issue. Apart from selecting presets and turning
the volume up and down (and those often via OrangeSqueeze) the thing has
scarcely been physically touched or updated. Indeed, it probably hasn't
even been Power Cycled for 6 months or so. "Old Reliable" I (usually)
call the radios!

I don't know much about the innards of a Radio. Any new ideas out
there?



AGB

Logitech Media Server Version: 7.7.6 - 1521467459 @ Thu Mar 29 16:46:01
WEDT 2018
Operating system: Windows 10
Music Library: external SD, exFAT (FLAC music; mp3 voice)

USA:
LinkSys WRT54GS Router, WPA2
1 x Touch, LAN (Firmware:7.7.3-r16676)
Controller: 7.7.2-r9663

France:
Sagem Livebox 2FR, or Freebox
1 x SB3, wireless. (Firmware 137)
2 x Touch, 1 wireless, 1 LAN. (Firmware:7.8.0-r16754)
Controller: 7.7.1-r9557
3 x SB Radios [2 wireless, 1 usually LAN]: 7.7.3-r16676
------------------------------------------------------------------------
agbagb's Profile: http://forums.slimdevices.com/member.php?userid=7034
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[mrw]

Any new ideas out there?

No new ideas, but an observation: switching to a stream with a different
sample rate is enough to reset the audio chip and restore the base.
Quicker than a power cycle.

I happen to have some presets playing streams that deliver 48,000
samples per second, and others that deliver 44,100. So it's easy for me
to do that. But I don't think LMS readily reports the sample rate, so
figuring out what each stream delivers might be a challenge. Perhaps
worth trying a few random prods at your presets next time.


------------------------------------------------------------------------
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[agbagb]

Post by mrw
No new ideas, but an observation: switching to a stream with a different
sample rate is enough to reset the audio chip and restore the base.
Quicker than a power cycle.
I happen to have some presets playing streams that deliver 48,000
samples per second, and others that deliver 44,100. So it's easy for me
to do that. But I don't think LMS readily reports the sample rate, so
figuring out what each stream delivers might be a challenge. Perhaps
worth trying a few random prods at your presets next time.

Oh, that's interesting. And easy enough to do (not least as a few of my
favorite BBC presets come in alternative formats, so I can just make
sure I have some at one rate and some at the other: makes very little
actual difference on the ear). Any idea on how that works, from both
angles? How does the chip lose its bearings, and how does a rate-switch
fix it?



AGB

Logitech Media Server Version: 7.7.6 - 1521467459 @ Thu Mar 29 16:46:01
WEDT 2018
Operating system: Windows 10
Music Library: external SD, exFAT (FLAC music; mp3 voice)

USA:
LinkSys WRT54GS Router, WPA2
1 x Touch, LAN (Firmware:7.7.3-r16676)
Controller: 7.7.2-r9663

France:
Sagem Livebox 2FR, or Freebox
1 x SB3, wireless. (Firmware 137)
2 x Touch, 1 wireless, 1 LAN. (Firmware:7.8.0-r16754)
Controller: 7.7.1-r9557
3 x SB Radios [2 wireless, 1 usually LAN]: 7.7.3-r16676
------------------------------------------------------------------------
agbagb's Profile: http://forums.slimdevices.com/member.php?userid=7034
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[pbg4]

Hi,

it is most probably a software problem, if I switch the radio to
tvheadend sat radio streams with 48khz and 320Kbit/s mp2
a couple of times, this is what I get in /var/log/messages when ssh'ed
to the radio:

Nov 14 12:47:21 squeezeplay: audio_thread_execute:1025 xrun
(snd_pcm_mmap_commit) err=-32
Nov 14 12:47:21 kernel: [14577.151780] ssi1_irq SISR 11a0 SIER 180100
fifo_errs=1

switching back to a radio station with 128kbit/s and CBR brings back
normal operation,..

best wishes pbg4


------------------------------------------------------------------------
pbg4's Profile: http://forums.slimdevices.com/member.php?userid=62543
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[d6jg]

Post by pbg4
Hi,
it is most probably a software problem, if I switch the radio to
tvheadend sat radio streams with 48khz and 320Kbit/s mp2
a couple of times, this is what I get in /var/log/messages when ssh'ed
Nov 14 12:47:21 squeezeplay: audio_thread_execute:1025 xrun
(snd_pcm_mmap_commit) err=-32
Nov 14 12:47:21 kernel: [14577.151780] ssi1_irq SISR 11a0 SIER 180100
fifo_errs=1
switching back to a radio station with 128kbit/s and CBR brings back
normal operation,..
best wishes pbg4

Coming to this late but my Radio displays the Bass issue from time to
time.

Are we saying that rather than a reboot a simple temporary switch of
audio formats from say 16/44 FLAC to 320kbps MP3 or vice versa will sort
the issue ?



VB2.4[/B] STORAGE *QNAP TS419P (NFS)
[B]Living Room* - Joggler & SB3 -> Onkyo TS606 -> Celestion F20s
*Office* - Pi3+Sreen -> Sony TAFE320 -> Celestion F10s / Pi2+DAC & SB3
-> Onkyo CRN755 -> Wharfedale Modus Cubes
*Dining Room* -> SB Boom
*Kitchen* -> UE Radio (upgraded to SB Radio)
*Bedroom (Bedside)* - Pi2+DAC ->ToppingTP21 ->AKG Headphones
*Bedroom (TV)* - SB Touch ->Sherwood AVR ->Mordaunt Short M10s
Everything controlled by iPeng
------------------------------------------------------------------------
d6jg's Profile: http://forums.slimdevices.com/member.php?userid=44051
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[pbg4]

Hi,

no reboot, only set a low bitrate radio i.e. 128 Bkit/s CBR on a preset,
switch to that radio station and
the squeezeplay audio.decode thread of the radio continues, until it
happens again,.. at least that is my experience here,

the radio is slow and also always tight on memory, my interpretation of
the error in the log posted above simply is,
that the audio.decode thread wanted to commit a number of pcm audio
samples of a high bitrate stream with an
alsa direct access mmap function call, but get's an error and than a
fifo overrun occurs,

if you switch than to a low bitrate radio you can see in the logs that
the audio decode thread reinits the decode_start_handler:279 init
decoder mp3
and continues,..

best wishes pbg4


------------------------------------------------------------------------
pbg4's Profile: http://forums.slimdevices.com/member.php?userid=62543
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[agbagb]

Post by pbg4
Hi,
no reboot, only set a low bitrate radio i.e. 128 Bkit/s CBR on a preset,
switch to that radio station and
the squeezeplay audio.decode thread of the radio continues, until it
happens again,.. at least that is my experience here,
the radio is slow and also always tight on memory, my interpretation of
the error in the log posted above simply is,
that the audio.decode thread wanted to commit a number of pcm audio
samples of a high bitrate stream with an
alsa direct access mmap function call, but get's an error and than a
fifo overrun occurs,
if you switch than to a low bitrate radio you can see in the logs that
the audio decode thread reinits the decode_start_handler:279 init
decoder mp3
and continues,..
best wishes pbg4

So it's at least possible that an occasional power-cycle may avert the
problem ever occurring.... With a bit-rate switch being an easy way of
fixing it if and when it does occur. I'm guessing that a lot of Radios
are very, very rarely power-cycled at all. Almost the only time I use
the power button on the radio itself is if I'm going away on a long trip
and am doing a general power-down. I sometimes - but not often - use
the power button on the remote or on LMS / OrangeSqueeze: but maybe that
doesn't do a full reboot in the way that the physical button on the
radio does.

Anyway, thanks to all. When it happened - first ever time - I
sort-of-assumed that something terminal had happened to a rather old
piece of kit.



AGB

Logitech Media Server Version: 7.7.6 - 1521467459 @ Thu Mar 29 16:46:01
WEDT 2018
Operating system: Windows 10
Music Library: external SD, exFAT (FLAC music; mp3 voice)

USA:
LinkSys WRT54GS Router, WPA2
1 x Touch, LAN (Firmware:7.7.3-r16676)
Controller: 7.7.2-r9663

France:
Sagem Livebox 2FR, or Freebox
1 x SB3, wireless. (Firmware 137)
2 x Touch, 1 wireless, 1 LAN. (Firmware:7.8.0-r16754)
Controller: 7.7.1-r9557
3 x SB Radios [2 wireless, 1 usually LAN]: 7.7.3-r16676
------------------------------------------------------------------------
agbagb's Profile: http://forums.slimdevices.com/member.php?userid=7034
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[mrw]

With a bit-rate switch being an easy way of fixing it if and when it
does occur.

Sample rate switch is my finding. Bit rate switch does not imply change
of sample rate. Many "low bit rate" & "high bit rate" streams just use
44,100 sample rate.
From memory, Jive-alsa is getting the decoded stream.


------------------------------------------------------------------------
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[d6jg]

Post by pbg4
Hi,
no reboot, only set a low bitrate radio i.e. 128 Bkit/s CBR on a preset,
switch to that radio station and
the squeezeplay audio.decode thread of the radio continues, until it
happens again,.. at least that is my experience here,
the radio is slow and also always tight on memory, my interpretation of
the error in the log posted above simply is,
that the audio.decode thread wanted to commit a number of pcm audio
samples of a high bitrate stream with an
alsa direct access mmap function call, but get's an error and than a
fifo overrun occurs,
if you switch than to a low bitrate radio you can see in the logs that
the audio decode thread reinits the decode_start_handler:279 init
decoder mp3
and continues,..
best wishes pbg4

Thanks.
What I was considering was setting a button to play a predefined
playlist that contains a single very short 20 seconds or so low bitrate
file of silence and then the radio station I actually want. (Now
wondering if you can add a radio station to a playlist. Only one way to
find out.)



VB2.4[/B] STORAGE *QNAP TS419P (NFS)
[B]Living Room* - Joggler & SB3 -> Onkyo TS606 -> Celestion F20s
*Office* - Pi3+Sreen -> Sony TAFE320 -> Celestion F10s / Pi2+DAC & SB3
-> Onkyo CRN755 -> Wharfedale Modus Cubes
*Dining Room* -> SB Boom
*Kitchen* -> UE Radio (upgraded to SB Radio)
*Bedroom (Bedside)* - Pi2+DAC ->ToppingTP21 ->AKG Headphones
*Bedroom (TV)* - SB Touch ->Sherwood AVR ->Mordaunt Short M10s
Everything controlled by iPeng
------------------------------------------------------------------------
d6jg's Profile: http://forums.slimdevices.com/member.php?userid=44051
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[mrw]

Post by agbagb
Oh, that's interesting. And easy enough to do (not least as a few of my
favorite BBC presets come in alternative formats, so I can just make
sure I have some at one rate and some at the other: makes very little
actual difference on the ear). Any idea on how that works, from both
angles? How does the chip lose its bearings, and how does a rate-switch
fix it?

I don't know how/when the chip loses its bearings, if that's what's
afoot. It would require some detailed output logging, for possibly
several weeks, until the next time the problem is encountered. With no
guarantee that the log will show anything useful. In my case, probably
several weeks/months. So I haven't tried.

Changing the sample rate generates something of a chip reset/re-program,
in jive-alsa, to cater for the new sample rate, and seems to be enough
to restore normal operation. It's been some long while since I looked at
the code.

Last time I looked was in connection with a Joggler (remember those?),
whose on-board chip had a habit of failing after some hours of
continuous playback. I was lucky enough to find an old reference on
tinternet to some kind of overflow within said chip. Turned out to be
easily detectable in jive-alsa once one knew what to look for (I don't
recall that logging helped). Chip reset/re-program cured that. I seem to
recall getting a corrective patch taken up in one of the Joggler
jive-alsa distributions. But doesn't help this problem !


------------------------------------------------------------------------
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[ralphy]

Post by mrw
I don't know how/when the chip loses its bearings, if that's what's
afoot. It would require some detailed output logging, for possibly
several weeks, until the next time the problem is encountered. With no
guarantee that the log will show anything useful. In my case, probably
several weeks/months. So I haven't tried.
Changing the sample rate generates something of a chip reset/re-program,
in jive-alsa, to cater for the new sample rate, and seems to be enough
to restore normal operation. It's been some long while since I looked at
the code.
Last time I looked was in connection with a Joggler (remember those?),
whose on-board chip had a habit of failing after some hours of
continuous playback. I was lucky enough to find an old reference on
tinternet to some kind of overflow within said chip. Turned out to be
easily detectable in jive-alsa once one knew what to look for (I don't
recall that logging helped). Chip reset/re-program cured that. I seem to
recall getting a corrective patch taken up in one of the Joggler
jive-alsa distributions. But doesn't help this problem !

Here is the 'joggler squeezeplay patch'
(https://birdslikewires.net/download/openframe/squeezeplay/compile/squeezeplay_v5.patch)
that contains the fix for no audio after 5 hours of playback.
It's actually a change in how jive-alsa handles/recovers from buggy alsa
drivers, it's not specfic to the STAC9202 in the joggler. Hmmm.



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.
------------------------------------------------------------------------
ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[mrw]

Post by ralphy
Here is the 'joggler squeezeplay patch'
(https://birdslikewires.net/download/openframe/squeezeplay/compile/squeezeplay_v5.patch)
that contains the fix for no audio after 5 hours of playback.
It's actually a change in how jive-alsa handles/recovers from buggy alsa
drivers, it's not specfic to the STAC9202 in the joggler. Hmmm.

Well, that's my patch. (The bit that relates to decode_alsa_backend.c).

I found my original patch, attached. There are a few additional notes in
it, suggesting that it was not an overflow in the chip (as I seem to
have mis-remembered) but in the alsa driver. I don't know how specific
the alsa driver is to the chipset, and I have no record of the original
source that put me on track.

Note that only one channel disappears in our Radio, not both.


+-------------------------------------------------------------------+
|Filename: 0001-Fix-sound-disappears-after-a-few-hours-when-using-al.patch|
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=26001|
+-------------------------------------------------------------------+

------------------------------------------------------------------------
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[ralphy]

I managed to create a squeezeos/poky build VM, something I've been
wanting to do for a long time, for another project I had in mind. Turns
out it was a lot easier than I thought.

I've applied your patch and rebuilt jive_alsa for the radio and have
been using it for the last two days without issue. Yesterday, I played
a flac stream for nearly 9 hours before I needed to use the Radio for
it's real purpose. I've never had the Bass amp problem on my Radio but
it's a UE Radio and there have been several hardware revisions of the
Radio, so perhaps not all are affected. We really don't know if the
change will help but at least we can try to track it down. Perhaps
updating jive_alsa to close the device after being idle for a time, like
the -C option in squeezelite may be enough to avoid the problem.

I created a Patch Installer package for the updated jive_alsa program,
but the file is locked while squeezeplay is running and there's no way
that I've found to run scripts as part of the patch. If you kill the
jive_alsa process the watchdog timer kicks in reboots the Radio, so it
will need to be an applet install like edo which I will do if we manage
to track down the Bass amp issue.

So for now, you'll have to ssh into the Radio and download, install the
update manually. Ideally, you shouldn't be playing anything on the
Radio while doing the update. The reboot at the end restarts the radio
immediately so you'll loose your connection.

Code:
--------------------
ssh -l root radio

cd /usr

wget http://ralph-irving.users.sourceforge.net/extensions/RadioJiveAlsa-1.0.tgz

# backup the original, don't use copy as the file is in use.
mv bin/jive_alsa bin/jive_alsa.bak

tar xzf RadioJiveAlsa-1.0.tgz

rm RadioJiveAlsa-1.0.tgz

reboot

--------------------



Now that I can rebuild bits or the entire firmware, minus the private
logitech parts I'm also able to run squeezelite on the radio...but
that's off topic.



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.
------------------------------------------------------------------------
ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[mrw]

Post by ralphy
I managed to create a squeezeos/poky build VM, something I've been
wanting to do for a long time, for another project I had in mind. Turns
out it was a lot easier than I thought.
<snip>
Now that I can rebuild bits or the entire firmware, minus the private
logitech parts I'm also able to run squeezelite on the radio...but
that's off topic.

Well done ! In the fullness of time I'd be interested to browse any
notes/do's/don'ts that you have prepared.

Do you know if the private parts include the Alsa crossover component ?
I think it may be called something like baby_dsp, presumably in the
kernel, but I don't know. I couldn't locate an obvious source file.

I ask because I assume that this is the piece of the alsa playback chain
that divides a (presumably mono by now) stream into bass & treble
speaker components, and it's only the base that disappears. Just a wild
speculation, really.

Note to self: next time the problem occurs (if it does), plug a
headphone in (which turns off the crossover) and see if anything can be
discerned. Fortunately/unfortunately I don't seem to be meeting the
problem any more.


------------------------------------------------------------------------
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[ralphy]

I see you discovered that the dsp bits are private.

The biggest issue is that the Ubuntu 10.4.04 ssl libraries are dated and
many sites no longer allow connections with the known unsecure ssl
protocols. I used the i386 iso to create the VM.

I had to rename the fakeroot_1.9.4.bb to fakeroot_1.9.5.bb and update
the source url, change the source url in qemu_0.9.1.bb to a valid
location and download libpng-1.2.43.tar.bz2 into the poky/sources folder
because SF doesn't allow the old ssl protocols, before bitbake
squeezeos-image ran to completion.

I updated poky/build/conf/local.conf so bitbake uses all 4 cpus during
the build/make process.

BB_NUMBER_THREADS = "4"
PARALLEL_MAKE = "-j 4"

Then build the image.

bitbake squeezeos-image

Afterware, rebuilding just decode_alsa_backend.c is a bit special.

Change the code once you find it!


Code:
--------------------
/home/ralphy/source/squeezeos/poky/build/tmp-jive/work/armv5te-none-linux-gnueabi/squeezeplay-7.8+svnr0+49f41e48311ade3a4a879b4b27283036363724b5-r24/squeezeplay/src/audio/decode
--------------------


Recompile just the changes.

bitbake -f -c compile squeezeplay

Rebuild the image

bitbake squeezeos-image

Grab the file from the image at


Code:
--------------------
/home/ralphy/source/squeezeos/poky/build/tmp-jive/rootfs/usr/bin
--------------------



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.
------------------------------------------------------------------------
ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[ralphy]

I started cherry picking Triode's EDO and my jive_alsa fixes but
eventually decided it would be better to keep the code as close to each
other as possible. There are new features that are useless to the radio
but cause no harm either.

So I took the latest decode_alsa_backend.c from my 'squeezeplay
repository' (https://github.com/ralph-irving/squeezeplay) with the patch
to reopen the ALSA device if the number of available frames exceeds the
total number of frames in the buffer applied as well and ended up with
v1.3.

I changed these modules from INFO to WARN on the Radio in
settings->advanced->logging.
["audio.codec"]="WARN"
["audio.decode"]="WARN"
["audio.output"]="WARN"

The error reporting is much better in the updated version, so if/when
you experience an issue, login to the radio and look at
/var/log/messages

The code is available on 'my github site'
(https://github.com/ralph-irving/radiojivealsa.git)

To update jive_alsa to 1.3

Code:
--------------------
ssh -l root radio

cd /usr

wget http://ralph-irving.users.sourceforge.net/extensions/RadioJiveAlsa-1.3.tgz

# backup the older version, don't use copy as the file is in use.
# you must move it out of the way for the new file to be extracted from the tarball.
mv bin/jive_alsa bin/jive_alsa-1.0

tar xzf RadioJiveAlsa-1.3.tgz

rm RadioJiveAlsa-1.3.tgz

reboot
--------------------


After the reboot you can delete /usr/bin/jive_alsa-1.0 if you want, but
don't delete the original jive_alsa.bak logitech build.

From the radio, you can confirm the version after the reboot.


Code:
--------------------
/usr/bin/jive_alsa -?
Usage: /usr/bin/jive_alsa *ri1.3* [-v] -d <playback_device> [-c <capture_device>] [ -t <pcm_timeout>] [ -s <sample_size>] -b <buffer_time> -p <period_count> -f <flags>
--------------------



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.
------------------------------------------------------------------------
ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[mrw]

@ralphy
Many thanks for the notes.

I didn't realize how much you have 'advanced' Squeezeplay. I may have a
few other (cosmetic, I suspect) patches that I've built up over time. If
any still seem to be relevant I'll pass them on.


------------------------------------------------------------------------
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread: http://forums.slimdevices.com/showthread.php?t=104141

[ralphy]

Thank you, that would be great!

I've added the patch we discussed here to the squeezeplay git repo.



Ralphy

*1*-Touch, *5*-Classics, *3*-Booms, *1*-UE Radio
'Squeezebox client builds'
(https://sourceforge.net/projects/lmsclients/files/) 'donations'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=LL5P6365KQEXN&lc=CA&item_name=Squeezebox%20client%20builds&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted)
always appreciated.
------------------------------------------------------------------------
ralphy's Profile: http://forums.slimdevices.com/member.php?userid=3484
View this thread: http://forums.slimdevices.com/showthread.php?t=104141