slartibartfast wrote:
> Twice in three years is pretty good particularly with no "fix"
> installed. It used to affect my Radios a lot more than that before I
> installed @mrw 's fix and more recently the community firmware.
>
> Sent from my Pixel 3a using Tapatalk
I hadn't read through this e
agbagb wrote:
> BTW, that previous problem I'd had was back in 2018, and was the first
> time it ever happened. It's happened twice since, today included. And
> always the same Radio, the white one.Twice in three years is pretty good
> particularly with no "fix"
installed. It used to affect m
bpa wrote:
> BBC HLS & DASH streams are AAC 48kHz sample - this includes "Listen
> Again". Same source just different transports.
>
> To ensure they are easily played - the global MP3 streams are 44.1kHz
>
> I think all modern BBC Podcast are 48kHz.
And my "fixer FLAC" was 44.1kHz. I have a
BBC HLS & DASH streams are AAC 48kHz sample - this includes "Listen
Again". Same source just different transports.
To ensure they are easily played - the global MP3 streams are 44.1kHz
I think all modern BBC Podcast are 48kHz.
-
BTW, that previous problem I'd had was back in 2018, and was the first
time it ever happened. It's happened twice since, today included. And
always the same Radio, the white one.
LMS 8.1.2 - 1622353561
Win10
Control: Web GUI; sometimes OrangeSqueeze on Android phones / pads
Machines / devi
slartibartfast wrote:
> You must have forgotten [emoji1787]
> https://forums.slimdevices.com/showthread.php?p=925627
>
> Sent from my Pixel 3a using Tapatalk
Ah-ha! I recalled what other had said, but not what I'd said myself! I
suppose, with Sounds rather than a mish-mash of audio formats,
agbagb wrote:
> Ahh - so it's likely sample-rate related? Odd, but
> sort-of-graspable... I did try switching from the bass-deprived BBC
> R4 on Sounds plug-in to R3 and to France Culture, but that didn't
> work Not sure whether those two sample-rates would be markedly
> different. T
slartibartfast wrote:
> Just changing to a radio station with a different sampling rate also
> works.
>
> Sent from my Pixel 3a using Tapatalk
Ahh - so it's likely sample-rate related? Odd, but
sort-of-graspable... I did try switching from the bass-deprived BBC
R4 on Sounds plug-in to
agbagb wrote:
> Just has this quiet, "tinny" output when strarting a BBC Sounds stream
> this morning - only 2nd or 3rd time in a very long user experience!
> IIRC, I've solved this in the past by a hard reboot, with the battery
> disconnected. But this time - screwdriver and radio in hand - I
Just has this quiet, "tinny" output when strarting a BBC Sounds stream
this morning - only 2nd or 3rd time in a very long user experience!
IIRC, I've solved this in the past by a hard reboot, with the battery
disconnected. But this time - screwdriver and radio in hand - I
recalled a tip someone
mrw wrote:
> I shall continue the quest. But I fear it will take a very large
> lightbulb and painstaking review of kernel sources to actually nail it.It
> seemed a strange time for it to happen. A radio stream was playing
before the restart but I am sure if I did the same again it wouldn't
hap
slartibartfast wrote:
> I just experienced the Bass Amp issue immediately after a plugin update
> and subsequent LMS restart.
I shall continue the quest. But I fear it will take a very large
lightbulb and painstaking review of kernel sources to actually nail it.
--
I just experienced the Bass Amp issue immediately after a plugin update
and subsequent LMS restart.
Sent from my Pixel 3a using Tapatalk
slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609
Vi
AlecSp wrote:
> An awesome track - persumably played by Ken Bruce, as he loves the
> song?Indeed it was Ken although I can't remember ever having heard the song
before. Even Springsteen likes it.
https://powerpop.blog/2019/02/12/raspberries-overnight-sensation-hit-record/
Sent from my Pixel 3a
slartibartfast wrote:
> I just heard a track on Radio 2 that at one point made me think that the
> bass amp issue had returned but it was just the way the track was
> produced. Sigh of relief [emoji1787]. It was a track I had never heard
> before (Overnight Sensation by the Raspberries) and all
mrw wrote:
> I know the feeling. My heart has been sinking a little over the last
> couple of weeks, but then I realized that the relevant Radio is using
> the original firmware.
>
> I have never heard of the Raspberries. Should I have done ?Based on that song
> I would say no but apparently J
slartibartfast wrote:
> I just heard a track on Radio 2 that at one point made me think that the
> bass amp issue had returned but it was just the way the track was
> produced. Sigh of relief [emoji1787]. It was a track I had never heard
> before (Overnight Sensation by the Raspberries) and all
I just heard a track on Radio 2 that at one point made me think that the
bass amp issue had returned but it was just the way the track was
produced. Sigh of relief [emoji1787]. It was a track I had never heard
before (Overnight Sensation by the Raspberries) and all of a sudden all
the instrumenta
mrw wrote:
> Be aware that the modifications to -jive_alsa- are present in the
> Community Firmware release announced yesterday.I saw that. Have you installed
> it?
Sent from my Pixel 3a using Tapatalk
slartibartfast'
slartibartfast wrote:
> Since installing your jive alsa I haven't seen the issue at all
Be aware that the modifications to -jive_alsa- are present in the
Community Firmware release announced yesterday.
mrw's Profile: htt
mrw wrote:
> Update December 2020: I find that the problem may still occur, so
> elimination of ALSA under-runs does not entirely cure the issue. But it
> has helped. I've had one instance in the last 10 months, flagged in the
> system log as follows:
> >
Code:
> >
>
mrw wrote:
> Having investigated the issue further over the last few months, somewhat
> sporadically, I have pursued an alternative approach to the problem. It
> appears to be effective, and has, in some form, been running on my
> Radios for the last five months or so without any obvious adverse
I've come late to this thread, but also periodically experience the
problem. While I used to perform a reboot of the radio to resolve it, I
then found that playing a mp3 track from my music library appears to
reset things just fine and dandy.
Not perfect, but much quicker than rebooting the rad
mrw wrote:
> Thanks for the feedback.
>
> Provided you see the line with -This is a modified version of jive_alsa
> that mitigates against 'bass drop out'-, all is well. This is the line
> that verfies that we are, indeed, running the modified -jive_alsa-,
> which is what I seek to confirm.
>
slartibartfast wrote:
> Everything seemed to go OK until I got to the final check where I didn't
> see these two lines
>
> Jul 10 13:19:45 squeezeplay: pcm_test:855 max sample rate 48000
> Jul 10 13:19:45 squeezeplay: audio_thread_execute:882
> audio_thread_execute
Thanks for the feedback.
Pr
mrw wrote:
> Let me know how you get on. Always helpful to know that the
> 'installation instructions' work for someone other than me.
Everything seemed to go OK until I got to the final check where I didn't
see these two lines
Jul 10 13:19:45 squeezeplay: pcm_test:855 max sample rate 48000
Ju
slartibartfast wrote:
> Simply disabling AAC hasn't fixed the bass amp issue so the next step is
> to try your Alsa fix.
Let me know how you get on. Always helpful to know that the
'installation instructions' work for someone other than me.
-
Simply disabling AAC hasn't fixed the bass amp issue so the next step is
to try your Alsa fix.
Sent from my Pixel 3a using Tapatalk
slartibartfast's Profile: http://forums.slimdevices.com/member.php?userid=35609
View th
mrw wrote:
> Yes.Oops so does mine. I could have sworn I looked there but obviously not.
Let's see if it helps now.
Sent from my Pixel 3a using Tapatalk
slartibartfast's Profile: http://forums.slimdevices.com/member.ph
slartibartfast wrote:
> Does the LMS now playing screen say the stream has been converted?
Yes.
+---+
|Filename: Safari - 10 Jul 2020 at 23:25.pdf|
|Download: http://forums.slimdevices.com/attachment.php?
mrw wrote:
> See attached.I did the same and no transcoding took place as far as I could
> see. Does
the LMS now playing screen say the stream has been converted?
Sent from my Pixel 3a using Tapatalk
slartibartfast's
slartibartfast wrote:
> Which AAC did you disable? My stream is still reported as 320kbps AAC
> when I disable AAC or MPEG-4.
See attached.
+---+
|Filename: Safari - 10 Jul 2020 at 22:54.pdf|
|Download: ht
mrw wrote:
> Perhaps a "post start up glitch" at the BBC, or perhaps something else.
> BBC iPlayer setting -Seconds to delay start live stream- ? Mine is at 10
> seconds.
>
> As an aside, I find the Radio menu navigation noticeably sluggish when
> streaming BBC 320kbs AAC.
>
> I have recently
mrw wrote:
> Perhaps a "post start up glitch" at the BBC, or perhaps something else.
> BBC iPlayer setting -Seconds to delay start live stream- ? Mine is at 10
> seconds.
>
> As an aside, I find the Radio menu navigation noticeably sluggish when
> streaming BBC 320kbs AAC.
>
> I have recently
slartibartfast wrote:
> The strange thing is it plays normally for a few seconds before the bass
> disappears.
Perhaps a "post start up glitch" at the BBC, or perhaps something else.
BBC iPlayer setting -Seconds to delay start live stream- ? Mine is at 10
seconds.
As an aside, I find the Radio
mrw wrote:
> Quite possibly contributory, because more decoding work. But then
> again...
>
> Possibly delays in stream start up at the BBC end. I've found it
> impossible to diagnose, I end up speculating.The strange thing is it plays
> normally for a few seconds before the bass
disappears.
slartibartfast wrote:
> Could it be because the stream is 320kbps? Then again it always has
> been.
Quite possibly contributory, because more decoding work. But then
again...
Possibly delays in stream start up at the BBC end. I've found it
impossible to diagnose, I end up speculating.
---
mrw wrote:
> My guess is that you are seeing what I think have seen, that increasing
> the buffer size just does not seem to be as effective when a stream is
> first started up. I won't attempt to speculate on why you have been
> recently "afflicted".
>
> See my previous post today for an addit
slartibartfast wrote:
> This is happening a lot now invariably when I press the Radio 2 preset
> with the dash iPlayer stream after a restart. I will try a buffer of
> 40ms to see if it improves.
My guess is that you are seeing what I think have seen, that increasing
the buffer size just does no
Having investigated the issue further over the last few months, somewhat
sporadically, I have pursued an alternative approach to the problem. It
appears to be effective, and has, in some form, been running on my
Radios for the last five months or so without any obvious adverse
effects.
This "sol
mrw wrote:
> I've not had it for a long while. Is your ALSA buffer size set to 30ms
> ?
>
> I've been running a different 'solution' for the last four months or so
> (a modified -jive_alsa- binary) which seems to be fine and absolutely
> stops the bass drop out. Perhaps it's time to offer it up
mrw wrote:
> I must check how the patch installer applet handles modified binaries.
Well, the answer is that it won't handle a modified -jive_alsa-. So a
little installation applet and/or a "do it by hand" instruction is
required.
---
mrw wrote:
> I've not had it for a long while. Is your ALSA buffer size set to 30ms
> ?
>
> I've been running a different 'solution' for the last four months or so
> (a modified -jive_alsa- binary) which seems to be fine and absolutely
> stops the bass drop out. Perhaps it's time to offer it up
slartibartfast wrote:
> Just happened again. Turned on Radio then pressed the preset for Radio 2
> and for the first few seconds sound was normal then the bass dropped
> out.
I've not had it for a long while. Is your ALSA buffer size set to 30ms
?
I've been running a different 'solution' for t
slartibartfast wrote:
> After months with no issues I have had the bass issue a couple of times
> over the past few days. This morning playback started normally then the
> bass disappeared after a couple of seconds. Strange.
>
> Sent from my Pixel 3a using TapatalkJust happened again. Turned on
After months with no issues I have had the bass issue a couple of times
over the past few days. This morning playback started normally then the
bass disappeared after a couple of seconds. Strange.
Sent from my Pixel 3a using Tapatalk
--
I have updated this Applet to work around a problem encountered with
playback of 22050 Hz sample rate streams, which was reported a while
back.
You may be asked to restart your Radio after installing the update.
There are no other changes, so need to rush unless you use a 22050 Hz
stream.
Orig
mrw wrote:
>
> Should this subject be moved to another thread ?
Yes, I thought the same thing when I last replied.
Created 'Community Build Radio Firmware'
(https://forums.slimdevices.com/showthread.php?111663-Community-Build-Radio-Firmware)
thread and replied there.
Ralphy
*1*-Touch, *5*
ralphy wrote:
> Could you provide details on the change(s) the next time you have the
> aws instance running?
Will do. But expect patchy responses as I have some family matters to
deal with over the next few weeks.
ralphy wrote:
>
> It would be great to have others test as well.
>
I'll load
mrw wrote:
> I recall that jive_alsa was "bit perfect" (subject to 4 debug hash bytes
> of no significance), and that libasound.so.2.0.0 was bit perfect (I was
> trying out a few later versions). I did have to define the original
> build directory, somewhere in the poky conf file, I think, to ge
mrw wrote:
> My own project, if I get to it, was to simply move the 'baby' onto
> Squeezeplay 7.8.
>
> It hadn't occurred to me to consider Squeezelite as a way to go. I'm not
> sufficiently familiar with it.
>
> As far as I can see, the only binary change is to take up ogg/flac, and
> perhaps
mherger wrote:
> As it's basically a back-port of a change already in the 7.8 branch, you
> wouldn't have to take care of that.
Thank you, I see that now.
mherger wrote:
> most Touch devices probably already run 7.8 firmware, which we never
> built for the Radio.
I guess native ogg/flac migh
I have no knowledge of the "lua random albums menu" and "lms 8.0
compatibility fixes" that you refer to, something to look into.
As mentioned above the "LMS 8.0 compatibility fixes" are available as a
patch on the Radio 7.7 firmware. As it's basically a back-port of a
change already in the 7.8
mrw wrote:
> I can see that there are quite a number of lua script changes that would
> need to be gone through to check that nothing breaks (upgrade
> compatibility for example, and perhaps restoration of firmware), but I'm
> not sufficiently familiar at present.
Well, I think the thing to do
slartibartfast wrote:
> Michael has a patch to fix the LMS 8.0 compatibility issue.
> https://forums.slimdevices.com/showthread.php?p=963365
Excellent, thank you. Looks like a simple fix. Version
comparison/tinkerings thereto was already on my watchlist...
mrw wrote:
> My own project, if I get to it, was to simply move the 'baby' onto
> Squeezeplay 7.8.
>
> It hadn't occurred to me to consider Squeezelite as a way to go. I'm not
> sufficiently familiar with it.
>
> As far as I can see, the only binary change is to take up ogg/flac, and
> perhaps
My own project, if I get to it, was to simply move the 'baby' onto
Squeezeplay 7.8.
It hadn't occurred to me to consider Squeezelite as a way to go. I'm not
sufficiently familiar with it.
As far as I can see, the only binary change is to take up ogg/flac, and
perhaps some version numbering twea
I have to decided what's the best way to proceed.
Update the bitbake squeezeplay recipe to use my current squeezeplay
sources or backport acc and maybe ogg/flac, and apply the lua random
albums menu and lms 8.0 compatibility fixes or just disable the
squeezeplay player and use squeezelite.
I'm
ralphy wrote:
> I've managed to build the radio firmware using a workaround for the
> private babydsp sources with 'these steps'
> (https://forums.slimdevices.com/showthread.php?98835-Compile-SqueezeOS-for-quot-Baby-quot-missing-babydsp-so-(BB-Poky-recipe-Private_SVN)&p=963718&viewfull=1#post963
mrw wrote:
> I finally found some time for this, thank you for the encouragement to
> proceed, and the tips. I knew less than nothing of 'poky' the day before
> yesterday, now just nothing.
>
> But I have generated an 'almost bit perfect' build of -jive_alsa-.
> Meaning that I have recreated th
mrw wrote:
> I'll have to see if there is some other reasonable combination that can
> work for all sample rates encountered, in place of 30ms.
Well, there is. For 30ms we can use 29991 instead of 3. And for 50ms
we can use 49990 instead of 5.
I have tested these with all sample rates
Thanks mrw. That makes a lot of sense and explains why 40 works fine.
I've been using 40ms since my last post and so far have had no
problems.
It is surprising the fractional part gives a problem. I'll have a look
through my library and see what other sample rates I have to see if i
can find on
pzyvbv wrote:
> I installed the applet and all seemed to be okay , but I recently tried
> to play an mp3 audio track with a sample rate of 22050Hz and it just
> refused to play with a buffer size of 30ms. In fact it crashed the
> player which became unresponsive and eventually rebooted.
>
> Tra
pzyvbv wrote:
> Hi.
>
> I installed the applet and all seemed to be okay , but I recently tried
> to play an mp3 audio track with a sample rate of 22050Hz and it just
> refused to play with a buffer size of 30ms. In fact it crashed the
> player which became unresponsive and eventually rebooted.
ralphy wrote:
> 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 finally found some time for this, thank you for the encouragement to
proceed, and th
rickwookie wrote:
> So glad I found this thread!
The alternative to rebooting, should it strike again, is to switch to
another stream (or music in your library) which broadcasts at a
different sample rate[1]. So, if I get the issue (usually BBC, 48,000
samples/sec), I switch to Classic FM (44,1
So glad I found this thread!
I bought a second-hand Radio off fleaBay last week to add to our home's
collection of Boxen, and after setting it up the bass and mid-ranged
dropped out after only about two minutes listening (it was just after
switching from playing BBC Radio 2 to BBC 6 Music). Was
frankd wrote:
> For me no drop-out anymore for the last 5 months using several radios...
>
> Great work!
Thanks for the report. I'm pleased that it has had a good effect.
I've had one further 'drop-out', again after the particular radio had
been silent for some time.
---
mrw wrote:
> Thanks. I can't see an 'obvious' reason for that.
>
> I have, myself, experienced one drop out on each of my two radios. I
> hypothesized at the time that this was because the radios had been
> silent for some time, so the (larger) alsa buffer hadn't had time to
> fill and ride ove
slartibartfast wrote:
> Three months later update. I was listening to Radio 2 while searching in
> the Spotty App and when I selected "Artists" in the search results the
> bass dropped out. When I played the Spotify tracks the bass returned.
> This is the first occurrence since installing the ap
slartibartfast wrote:
> I have added the applet to both my Radios and will give feedback if
> necessary. Hopefully I won't need to. It was a rare occurrence on mine
> anyway but if it never happens again I'll be happy. Good work.
>
> Sent from my SM-G900F using TapatalkThree months later update
mrw wrote:
> Further to investigations over the last two/three weeks, I have found
> that increasing the Radio's ALSA buffer size to 30 milliseconds is
> proving to be an effective work-around to the problem. Since making this
> change, I have had no instances of "Bass drop-out" in circumstances
frankd wrote:
> Thanks a lot for all your work.
> I experienced the same problem with my set of radios. I have just
> installed your applet, set all to 30ms and I will report back if it
> works (this may take some time as I will test them as they are, not
> provoke any bass amp problems - the
Thanks a lot for all your work.
I experienced the same problem with my set of radios. I havejust
installed your applet, set all to 30ms and I will report back if it
works (this may take some time as I will test them as they are, not
provoke any bass amp problems - the failures felt pretty rando
Further to investigations over the last two/three weeks, I have found
that increasing the Radio's ALSA buffer size to 30 milliseconds is
proving to be an effective work-around to the problem. Since making this
change, I have had no instances of "Bass drop-out" in circumstances
where I would hithe
ralphy wrote:
> I can re-run the tests of interest again with the signal generator for
> whatever duration if you'd like.
Well, I re-ran mine using a flac file instead of the pcm that the signal
generator gives.
I still observed plenty of bass drop-outs with both the stock jive_alsa
and R1.4.
I can re-run the tests of interest again with the signal generator for
whatever duration if you'd like.
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?cm
mrw wrote:
> I should remark that I have the same outcome with R1.3 of jive_alsa. I
> haven't tried with R1.4.
I've now made some tests with R1.4, seeking to replicate your own tests
(#1 and #3) with the stock buffer size and period count. I used a 48kHz
16bit Raw PCM stream provided by the LMS
mrw wrote:
> I should remark that I have the same outcome with R1.3 of jive_alsa. I
> haven't tried with R1.4.
The are no functional changes between 1.3 and 1.4, only 'more logging'
(https://github.com/ralph-irving/radiojivealsa/commit/02034a0711180451ae880bbe74037d6c44060ba0).
See 'post #48'
(
mrw wrote:
> It will sound off a customized sound effect about every 1.5 seconds.
> When I am playing a 48kHz sample rate stream on each of my two rev 5
> radios, with default software and default jive_alsa settings, I find
> that, after a few minutes, bass drop-out reliably occurs. It may take
ralphy wrote:
> Interesting results with my UE rev.0007 radio.
Very interesting. My quick take is that the UE Radios are probably as
susceptible to Bass drop-out as are the rev 0005s. I have had your #1
"instantaneous" experience on occasion. Actually on the first occasion,
just like you did. B
Interesting results with my UE rev.0007 radio.
All tests were done playing 48Khz 16bit flac files via wireless
Test#1
Firmware jive_alsa buffer size 2 buffer count 2
I HAD THE BASS DROPOUT ALMOST IMMEDIATELY AND IT DID RECOVER A BIT
LATER.
First time I've ever noticed that happen. Howeve
I have made a simple "Provocation" applet that automates my earlier
manual testing.
It will sound off a customized sound effect about every 1.5 seconds.
When I am playing a 48kHz sample rate stream on each of my two rev 5
radios, with default software and default jive_alsa settings, I find
that,
Hi,
the rev 7 and rev 5 have identical /proc/cpuinfo here,.. if the rev 7
soc is advanced in any
way than at least it is not documented in the cpuinfo, maybe that only
same errors were ironed out ?, as it is the normal way with cpu's,..
and thanks for the info, so a change of values in Squeezeb
mrw wrote:
> Yes. But be aware that if you then shut down the Radio (jive) in a
> controlled manner, it will overwrite your good work with its own cached
> values as it closes. So requires a rather more firm approach. Perhaps
> just plain 'reboot'. Or 'kill -9 jive'. I don't know what is best, o
pbg4 wrote:
>
> in the dmesg the only difference between the two board revisions 7 and 5
> is the soc revision,
> >
Code:
> > CPU is i.MX0 Revision 0.7 CPU is i.MX0 Revision 0.5
> >
On each of two rev 0005 Radios I have:
Code:
---
Hi
in order to track this down further a little bit, now I have three
radios playing for testing, two rev 5, one with jive_alsa r1.3, the
other with r1.4,
the rev 7 is playing unaltered, no glitch so far,..
in the dmesg the only difference between the two board revisions 7 and 5
is the soc revi
ralphy wrote:
> The 'EDO applet for the touch'
> (https://github.com/ralph-irving/EnhancedDigitalOutput) might be a good
> starting point for an applet to change the buffer period count and time
> for the radio.
>
> It doesn't allow you to enter values but rather supplies a list of
> options to
Hi,
thanks for the new version Ralphy, ging to test it this evening,...
concerning the hw revision I have the same observations here, two radios
are hw rev 5,
two are hw rev 7 (one UE-radio converted, the other came with
squeezeos),
the rev 5 ones have the bass dropout glitches, but were not o
The 'EDO applet for the touch'
(https://github.com/ralph-irving/EnhancedDigitalOutput) might be a good
starting point for an applet to change the buffer period count and time
for the radio.
It doesn't allow you to enter values but rather supplies a list of
options to choose from and the kernel u
mrw wrote:
> I have made a modified sound effect. Using the on-board sound effect
> bump.wav as a base, I made one lasting for about one second. Then,
> while playing a 48,000 sample rate stream, I repeatedly press the back
> key and generate lots of (longer) bumps. At the same time, looking
pbg4 wrote:
> Itried for quite a while today to produce the bass amp dropout with
> different audio material on this radio,
> but even after quite some time of testing could not provoke it, next
> step here will be to put the patch on all the radios,
> and check the hw version,..
I have made a mo
Hi,
just to be precise - as I have four radios in the house - the one where
I did the successfull test with jive_alsa from Ralphy
has squeezeos 7.7.3r16676 and Hardware version 5, perhaps it is also
dependend on the hardware version,..
after I read your reply I tried for quite a while today to
pbg4 wrote:
> but the solution for the bass amp problem is already in this thread, see
> jive_alsa download from Ralphy above, since I have installed
> his new jive_alsa version the problems here have nearly vanished
> completely,..
>
Well, I'm very pleased for you ! But I do not share your f
Hi,
but the solution for the bass amp problem is already in this thread, see
jive_alsa download from Ralphy above, since I have installed
his new jive_alsa version the problems here have nearly vanished
completely,..
nearly because there was only one bass amp hickup here after playing
full res
mrw wrote:
> I won't pretend to be any wiser, but it may offer a clue as to where to
> start looking.
I've had a further look, and made some experimentation.
My draft conclusions are:
- The problem arises when there are under-runs between jive_alsa and
the ALSA sub-system.
- The Rad
slartibartfast wrote:
> WinSCP was the answer. Can you see anything?
I think so. I've snipped away a bit to highlight an error reported 10
seconds or so before you switched over to Virgin:
Code:
Jan 23 10:04:31 squeezeplay: audio_thread_execute:1025 xrun
(snd_pcm_mma
mrw wrote:
> After you have logged in to the radio, you should be able to view the
> log on screen with the command:>
Code:
> > cat /var/log/messages
> >
>
> I have never used putty. On a Mac or Linux box one can do (from a
> terminal prompt): >
mrw wrote:
> After you have logged in to the radio, you should be able to view the
> log on screen with the command:>
Code:
> > cat /var/log/messages
> >
>
> I have never used putty. On a Mac or Linux box one can do (from a
> terminal prompt): >
slartibartfast wrote:
> I can't remember how to download the log. I have logged in with putty
> and found the file, but now what?
>
> Edit. First time I logged in and used the command ls I could see files
> and directories. Second time I logged I couldn' t see anything.
> Confused.
>
> Sent f
1 - 100 of 137 matches
Mail list logo
