today I tried to upgrade my Touch, but it did not work until now. When I
look in the Plugin files I see that the firmware file should come from
https://ralph_irving.gitlab.io/lms-community-firmware/update/firmware/
When I try to find it via my Browser I get a "404/The page you're
looking for co
tw99 wrote:
> The only patch on my Radio is the one that allows it to work correctly
> with an LMS 8 server. So if I reset it back to factory settings, and
> then for some reason the upgrade doesn't work, does that mean I'd need
> to find a 7.x server in order to get it going again ? This is
Michael
Tried to upgrade the IO::Socket::SSL version and it upgrade nicely to
v2.068
But when I restart Squeezeboxserver, it still says i'm running on a old
version v1.94
You might have different versions of Perl installed? What does the
following tell you?
`which perl` -v
And what about
mherger wrote:
> > 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
Tried to upgrade the IO::Socket::SSL version and it upgr
The only patch on my Radio is the one that allows it to work correctly
with an LMS 8 server. So if I reset it back to factory settings, and
then for some reason the upgrade doesn't work, does that mean I'd need
to find a 7.x server in order to get it going again ? This is the only
thing that's
slartibartfast wrote:
> I thought you could just long press on the "left" button to avoid an
> immediate upgrade.
Goodness me ! So you can.
So, there's another "unapparent way out".
mrw's Profile: http://forums.slimdevic
mrw wrote:
> "No apparent way out" is, I suspect, because LMS considers this to be
> "forced" upgrade. The revision on the new firmware is later than the
> revision present on the device. See
> -Slim::Utils::Firmware::need_upgrade-.
> https://github.com/Logitech/slimserver/blob/public/8.1/Slim/U
Heuer wrote:
> When I rebooted the devices they went straight into the upgrade menu
> with no apparent way out!
"No apparent way out" is, I suspect, because LMS considers this to be
"forced" upgrade. The revision on the new firmware is later than the
revision present on the device. See
-Slim::U
Ditto. Upgraded two Radio's and a Controller (twice as another version
was released) without problems. I was getting worried as I did not do a
factory reset as suggested on any of them before switching the
'download' on in LMS. When I rebooted the devices they went straight
into the upgrade menu
As another checkpoint:
Just updated 2 x Touch, 2 x Radio and a controller to the current v8
firmware. Did not experience any problems so far.
Very nice work!
NeverSimple's Profile: http://forums.slimdevices.com/member.p
rfunk wrote:
>
> I'm not sure I wouldn't describe this as "a small click", but more
> like dropouts happening at a regular high frequency, happening every day
> but *only* when starting from the alarm function. (When I say "high
> frequency" that's to say many times per second as opposed to
rfunk wrote:
> Maybe I should try the Buffer Size applet. I'm also curious about the
> 22kHz problem that required updating that applet.
Well, I was going to experiment with the buffer size, but first the
radio wanted to upgrade to the latest firmware (8.0.1-r16824). So I
tested alarms with tha
Thanks for trying it out!
mrw wrote:
> The "old" firmware was unable to connect, and played out the fall-back
> alarm track instead. Apparently it only allows 25 seconds before
> deciding that a station is "bad", and playing out the fall-back alarm.
> ...
> So, based on my very limited trial, I
rfunk wrote:
> Ever since upgrading my bedroom Squeezebox Radio to this firmware, my
> 6am alarm starting an internet radio stream has sounded really bad. It's
> hard to describe, but it's rough and quiet, almost like maybe it's only
> playing half of each sample.
I played out your station last
Ever since upgrading my bedroom Squeezebox Radio to this firmware, my
6am alarm starting an internet radio stream has sounded really bad. It's
hard to describe, but it's rough and quiet, almost like maybe it's only
playing half of each sample. If I switch to another station it sounds
fine; then I
Yes. Martin and I fixed a few issues with the previous release. The
'changelog'
(https://ralph_irving.gitlab.io/lms-community-firmware/changelog.html)
lists what's new.
Oh, ok, cool!
--
Michael
___
plugins mailing list
plugins@lists.slimdevices.com
mherger wrote:
> > Yes, the current community firmware 8.0.1r16824 is available at
> > https://sourceforge.net/projects/lmsclients/files/squeezeos/.
>
> Did you release a new build recently? A few of my devices offered
> another update today.
>
> --
>
> Michael
Yes. Martin and I fixed a f
avr300 wrote:
> Yes, blue icon means connected to wifi but no connection to the selected
> LMS.
>
> It works as expected in Version 8.0.1 r16824You just made me realise there
> was an update [emoji3]
Sent from my Pixel 3a using Tapatalk
mherger wrote:
> > Yes, the current community firmware 8.0.1r16824 is available at
> > https://sourceforge.net/projects/lmsclients/files/squeezeos/.
>
> Did you release a new build recently? A few of my devices offered
> another update today.
>
> --
>
> Michael
I updated to r16824 today.
Yes, the current community firmware 8.0.1r16824 is available at
https://sourceforge.net/projects/lmsclients/files/squeezeos/.
Did you release a new build recently? A few of my devices offered
another update today.
--
Michael
___
plugins mailing lis
slartibartfast wrote:
> Since I followed your instruction to enable the blue icon every time
> there has been a short disconnection the icon has been red so it
> probably isn't critical to have. Did blue mean connected to WiFi/network
> but not connected to LMS?
>
> Sent from my Pixel 3a using
JJZolx wrote:
> Can the firmware be just be downloaded manually into the LMS folder? I'd
> like to get it upgraded and done with.
Yes, the current community firmware 8.0.1r16824 is available at
https://sourceforge.net/projects/lmsclients/files/squeezeos/.
Ralphy
*1*-Touch, *5*-Classics, *3*
expectingtofly wrote:
> I've done some further tracing.
> Both old and new firmware are getting the data quite happily from the
> BBC Sounds protocol handler.They both ask for 32768 Bytes at a time.
> The BBC data is available in 6.4 second chunks and it gets that in a
> sprightly 0.3 of a s
Can the firmware be just be downloaded manually into the LMS folder? I'd
like to get it upgraded and done with.
JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10
View this thread: http://forums.slimdevic
mrw wrote:
> I will add that when I play out BBC Radio 3 from BBC Sounds app I also
> see distinctly "healthier" stream buffer fullness. In distinct contrast
> to playing the BBC Radio 3 stream directly from the BBC. So
> @expectingtofly's comment about masses of buffering might be in play !
>
mrw wrote:
> Compare this with, say, a Touch (I don't have one, so I can't, but would
> be interested to see the results), or an MP3 stream.
The only AAC-320 stream I could find was radio paradise. From my touch
8.0.1r16824.
Code:
Jan 7 14:34:17 squeezeplay: INFO
mrw wrote:
> Distinctly "healthier" than what I was seeing. If "health" correlates to
> >2% stream buffer fullness. You seem to vary from 0% to 6/7%.
> What stream is being played ? Presumably this is on a Radio.
I will add that when I play out BBC Radio 3 from BBC Sounds app I also
see distinc
mrw wrote:
> Distinctly "healthier" than what I was seeing. If "health" correlates to
> >2% stream buffer fullness. You seem to vary from 0% to 6/7%.
> What stream is being played ? Presumably this is on a Radio.Radio 2 live on a
> Radio.
Sent from my Pixel 3a using Tapatalk
--
mrw wrote:
> Or perhaps not.
>
> What is easy to overlook is "how stressed" the Radio seems to be when
> decoding aac streams. I've never looked into it in any detail, but an
> indication can be obtained by setting the 'audio.decode' logging level
> on the Radio to debug. You'll see a line, eac
slartibartfast wrote:
> FWIW these are my figures]
Distinctly "healthier" than what I was seeing. If "health" correlates to
>2% stream buffer fullness. You seem to vary from 0% to 6/7%.
What stream is being played ? Presumably this is on a Radio.
---
mrw wrote:
> Or perhaps not.
>
> What is easy to overlook is "how stressed" the Radio seems to be when
> decoding aac streams. I've never looked into it in any detail, but an
> indication can be obtained by setting the 'audio.decode' logging level
> on the Radio to debug. You'll see a line, eac
mrw wrote:
> >
Code:
> > tail -F /var/log/messages
> > is probably your best bet when logged in. It will give a rolling
> output. Ctrl C to stop.
>
> But I'm much less sure of my hypothesis, now, see EDIT to earlier
> post. I may have inadvertentl
slartibartfast wrote:
> How do I get to the messages file in the Radio? I am pretty sure I have
> done this before but it was long ago. I can SSH in using putty but what
> next? With WinSCP I get "Remote side unexpectedly closed network
> connection"
Code:
tail -F /var/
mrw wrote:
> Or perhaps not.
>
> What is easy to overlook is "how stressed" the Radio seems to be when
> decoding aac streams. I've never looked into it in any detail, but an
> indication can be obtained by setting the 'audio.decode' logging level
> on the Radio to debug. You'll see a line, eac
expectingtofly wrote:
> So it seems that there is something incompatible with the way BBC Sounds
> provides the data for the new AAC decoder, that was fine on the old
> decoder.
Or perhaps not.
What is easy to overlook is "how stressed" the Radio seems to be when
decoding aac streams. I've nev
mrw wrote:
> There have been changes to the alarm handling code, but, as far as I am
> aware, only those that Logitech made between SqueezePlay versions 7.7
> and 7.8. Recall that v7.8 was never released for the Radio. So I would
> now expect the alarm handling on the Radio to match that on a To
slartibartfast wrote:
> I updated to the latest LMS 8.1.1 while my Radio was still playing my
> alarm radio station. Normally if I do this then the default alarm sound
> is triggered when LMS shuts down but not this time. This is probably the
> first time I have done this since updating the firm
I updated to the latest LMS 8.1.1 while my Radio was still playing my
alarm radio station. Normally if I do this then the default alarm sound
is triggered when LMS shuts down but not this time. This is probably the
first time I have done this since updating the firmware so has something
changed?
mrw wrote:
> They are very relevant. They imply that the Radio has been running out
> of decoded audio. My questions are: "why" ?, and "why just aac" ?
>
> I had a few of this morning on my Radio, and I'm noticing a number of
> occasions when the stream has stopped and restarted.
>
> I don't
mrw wrote:
> They are very relevant. They imply that the Radio has been running out
> of decoded audio. My questions are: "why" ?, and "why just aac" ?
>
> I had a few of this morning on my Radio, and I'm noticing a number of
> occasions when the stream has stopped and restarted.
>
> I don't
expectingtofly wrote:
> I've upgraded the radios again and looked at the var/log/messages log.
>
> I get these 'Audio underun' and 'OUTPUT UNDERRUN'messages that seem to
> coincide with the juddering and micro stuttering when playing BBC Sounds
> AAC streams. Are they relevant? I don't get si
mrw wrote:
> I should have remarked that my experience has been with LMS 8.0.1. A
> point of detail that had passed me by.
>
> I installed LMS 8.1 on a 'spare' server this morning (macOS - plenty
> power). And I think that I might have experienced something of the same.
> As in a certain amount
mrw wrote:
> I should have remarked that my experience has been with LMS 8.0.1. A
> point of detail that had passed me by.
>
> I installed LMS 8.1 on a 'spare' server this morning (macOS - plenty
> power). And I think that I might have experienced something of the same.
> As in a certain amount
expectingtofly wrote:
> Interestingly, it happens repeatedly and reliably for me for all BBC
> Sounds streams (yes you are right LMS is fetching them, they are dash
> streams that are stitched together by the plugin.). There is a lot of
> stuttering at the start of the stream, and intermittent
Last weekend I installed the latest version of the Community Firmware on
2 Radios, 2 Controllers and one Touch without any problems. It just
worked via Michaels plugin. I did a factory reset on each device before
installing the new firmware. LMS is version 8.1 on max2play. All of my
devices are wo
mrw wrote:
> I've done a little investigation over the last couple of days.
I am not sure how to say anything except 'wow' at this point :)
Again, I was thinking it might have been as easy (for you guys more like
trivial, compared to all the other efforts) to replace some synching
code with a n
nenu wrote:
> I don't see this mentioned in the changelog, but would the new firmware
> improve synchronization for Duet Controllers used as players? That
> wasn't working (or not implemented) with the official firmware, but
> maybe now it is?
I've done a little investigation over the last coup
mrw wrote:
> Well remembered ! Fortunately I did remember to check the point before
> commenting...
>
> It does seem to make the menus more responsive, but for some reason, I
> forget what, I reverted back to "native AAC" quite a while ago. Probably
> to check the new firmware. So my observatio
slartibartfast wrote:
> Didn't you turn off native AAC at some point? I think you said it made
> the Radio menu more responsive.
Well remembered ! Fortunately I did remember to check the point before
commenting...
It does seem to make the menus more responsive, but for some reason, I
forget wha
mrw wrote:
> I've been using this firmware, or a variant, for some little time now
> and do not recognize the symptoms you describe. One of my Radios is
> constantly playing BBC AAC streams, either from BBC Sounds or BBC
> iPlayer, at 320k/48k.
>
> Are you able to provide me with a stream that
sbp wrote:
> In my TIDAL log file (se download link above) I often see this. Do you
> think that is the cause of the problems
>
> >
Code:
> >
> [21-01-05 14:07:24.5057]
Slim::Player::StreamingController::playerOutputUnderrun (2239)
00:04:20:2a:d8:53: decoder: 155
expectingtofly wrote:
> The LMS that my radios are connecting to is on a very low powered
> raspberry pi model 1b, so I actually wondered if that is the problem.
I'm using a SheevaPlug, also quite low power...
mrw's Pro
mrw wrote:
> I've been using this firmware, or a variant, for some little time now
> and do not recognize the symptoms you describe. One of my Radios is
> constantly playing BBC AAC streams, either from BBC Sounds or BBC
> iPlayer, at 320k/48k.
>
> Are you able to provide me with a stream that
In my TIDAL log file (se download link above) I often see this. Do you
think that is the cause of the problems
Code:
[21-01-05 14:07:24.5057]
Slim::Player::StreamingController::playerOutputUnderrun (2239)
00:04:20:2a:d8:53: decoder: 1552148 / output: 0[21-01-05 14:07
expectingtofly wrote:
> I meant to raise this a few days ago also, I was going to do a bit of
> investigation. The new firmware has the same problems with the AAC
> streams on BBC Sounds. There is kind of a micro stutter and warble when
> playing AAC streams on the Squeezebox Radio, its as i
AAC is 320k CBR
Here is a log file with stuttering when I started the stream - then I
paused the stream after a few seconds.
https://www.dropbox.com/t/AuMG9Zyzn3slIyjs
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: 'https://www.picoreplayer.org' (https://www.picoreplaye
ralphy wrote:
> Could be high CPU usage at the start of the stream.
>
> The AAC support in the community firmware is not the same as the
> Logitech firmware since the source code and decoder are not available.
>
> What does LMS report as the bit rate and sample frequencies of the AAC
> stream(
sbp wrote:
> Hi Ralphy.
>
> I have an issue with playing AAC from TIDAL using the new firmware on a
> Squeezebox Radio.
> All tracks plays nicely on another Radio with the old firmware.
> If I disable AAC in the file format - then the Radio with the new
> Community Firmware plays without stutt
sbp wrote:
> Hi Ralphy.
>
> I have an issue with playing AAC from TIDAL using the new firmware on a
> Squeezebox Radio.
> All tracks plays nicely on another Radio with the old firmware.
> If I disable AAC in the file format - then the Radio with the new
> Community Firmware plays without stutt
Hi Ralphy.
I have an issue with playing AAC from TIDAL using the new firmware on a
Squeezebox Radio.
All tracks plays nicely on another Radio with the old firmware.
If I disable AAC in the file format - then the Radio with the new
Community Firmware plays without stutter.
See description here:
If I recall correctly, the Controller has "on" and "off" states that are
not entirely intuitive and not consistent with the behavior of the Touch
and Radio. This may or may not be related to what you are seeing.
Mark Miks
mrw wrote:
> Uptime ?
> Meaning, might it have rebooted itself in the interim ? Just a wild
> thought.Hmm only 11 hours so it would have rebooted this morning. I noticed
> the
full brightness yesterday though. I will keep an eye on the uptime
though to see if it is rebooting more often than the
slartibartfast wrote:
> I just checked my Controller again and sure enough it is back to full
> brightness. I haven't even touched it since I last reduced the
> brightness.
Uptime ?
Meaning, might it have rebooted itself in the interim ? Just a wild
thought.
--
mrw wrote:
> Well, it certainly does try. Unless you've set the Controller player
> synchronization setting to "Don't maintain synchronization".
No, it is set to maintain synchronization.
For the other players, synchronization has been working well, both wired
and wireless with a mix of Radios
nenu wrote:
> To me it seems that the controller never tries to correct for any sync
> difference after it has been started.
Well, it certainly does try. Unless you've set the Controller player
synchronization setting to "Don't maintain synchronization".
But, of course, it is isn't entirely suc
mrw wrote:
> I have not been able to "relate" to any of that, I'm still not sensitive
> to the issue raised. Unless/until it can be reliably reproduced it will
> be rather diffult to track down. I'll keep an eye on my Controller.I just
> checked my Controller again and sure enough it is back to
mrw wrote:
> Are there any hints in those old 2008 threads as to where the problem
> may lie ?
No, unfortunately not.
The Wiki entry is here:
'Squeezebox_Controller_Audio_Playback'
(https://wiki.slimdevices.com/index.php/Squeezebox_Controller_Audio_Playback.html)
note at the bottom: 'Synchron
Tony T wrote:
> Wheee? I dont see it.
Here!
32793
+---+
|Filename: here.jpg |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=32793|
+
devilsfun wrote:
> really hard to find in the first post
Wheee? I dont see it.
Tony
SBTouch ♪ SBRadio ♬
Tony T's Profile: http://forums.slimdevices.com/member.php?userid=34544
View this thread: http://forums.slimdev
nenu wrote:
> So yes, it does seem to work at first, but it gets out of sync very
> soon.
Are there any hints in those old 2008 threads as to where the problem
may lie ? Do have a reference to the WIKI page ?
I agree, my Controller does seem to play back noticeably faster than the
Radio, and w
I posted this a while ago (to no reaction, but I figured this might be
worth to bring up again):
https://forums.slimdevices.com/showthread.php?112245-Duet-Controller-sync
I'll just repeat with added emphasis:
>
> After some years of slight disappointment and wondering if it has
> anything to do
mrw wrote:
> Blimey, I've never thought to try that.
> I have just synchronized my Controller (used as a player), with a Radio.
> It seems to work. But not as a result of the new firmware. So I don't
> know what problem you see.Haven't done it for a long time but does it stay in
> sync?
Sent f
nenu wrote:
> I don't see this mentioned in the changelog, but would the new firmware
> improve synchronization for Duet Controllers used as players? That
> wasn't working (or not implemented) with the official firmware, but
> maybe now it is?
Blimey, I've never thought to try that.
I have just
nenu wrote:
> I don't see this mentioned in the changelog, but would the new firmware
> improve synchronization for Duet Controllers used as players? That
> wasn't working (or not implemented) with the official firmware, but
> maybe now it is?
There has been no effort to address this in the Com
Man in a van wrote:
> I found this
>
> https://www.max2play.com/en/forums/topic/restoring-lms-settings-to-new-installation/
>
>
> 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 Win32D
bayard1music wrote:
> Hello,
>
> I'm obviously doing something wrong here ?
>
> I've upgraded the server to LMS 8.0.1 and have selected the community
> firmware plug in and enabled in 'Advanced' tab.
>
> Now on the Squeezebox Radio I've installed the 'Patch Installer' and
> attempted to selec
I've upgraded the server to LMS 8.0.1 and have selected the community
firmware plug in and enabled in 'Advanced' tab.
Now on the Squeezebox Radio I've installed the 'Patch Installer' and
attempted to select the 'compare versions check' (I understand necessary
to correctly compute that there is a
Hello,
I'm obviously doing something wrong here ?
I've upgraded the server to LMS 8.0.1 and have selected the community
firmware plug in and enabled in 'Advanced' tab.
Now on the Squeezebox Radio I've installed the 'Patch Installer' and
attempted to select the 'compare versions check' (I under
I don't see this mentioned in the changelog, but would the new firmware
improve synchronization for Duet Controllers used as players? That
wasn't working (or not implemented) with the official firmware, but
maybe now it is?
---
kidstypike wrote:
> https://ralph_irving.gitlab.io/lms-community-firmware/changelog.html
really hard to find in the first post
1-Touch, 3-Classics, 1-UE Radio
Raspberry Pi 4 / 4gb - piCorePlayer v7.0.0 - LMS 8.1.0
devil
Thanks!
Tony
SBTouch ♪ SBRadio ♬
Tony T's Profile: http://forums.slimdevices.com/member.php?userid=34544
View this thread: http://forums.slimdevices.com/showthread.php?t=113479
Tony T wrote:
> Good to see the development of the Community Firmware and I'm
> considering to now use it now that I see there's a plug-in to assist in
> installation (I'm running pCP with LMS 8.1.0), but not sure if I need
> it.
> Is there a list of the additions/benefits from the original firm
Good to see the development of the Community Firmware and I'm
considering to now use it now that I see there's a plug-in to assist in
installation (I'm running pCP with LMS 8.1.0), but not sure if I need
it.
Is there a list of the additions/benefits from the original firmware?
Tony
SBTouch
kidstypike wrote:
> Here . .
>
> 32777
OK got it! Sorry just hardly ever used these plugins , once every 3
years ;-) or so. I've ticked that now. Thanks , will try that.
bayard1music's Profile: http://forums.slimdevice
bayard1music wrote:
> Hello,
>
> Not sure where you mean ? I've enabled the community radio firmware
> plugin as shown below:
>
> Are you referring to some thing else ?
Here . .
32777
+---+
|Filename: tickit.jpg
slartibartfast wrote:
> There is a tick box in the community Radio firmware plugin.
>
> Sent from my Pixel 3a using Tapatalk
Hello,
Not sure where you mean ? I've enabled the community radio firmware
plugin as shown below:
Are you referring to some thing else ?
3277632776
+-
bayard1music wrote:
> Hello,
>
> Forgive me if this is already covered.
>
> I've just replaced my rasberry pi server with Logitech Media Server
> Version: 8.0.1 - 1608617100
>
> I've installed the community radio plugin on the server.
>
> I've also installed the 'Version Comparison' Patch o
Hello,
Forgive me if this is already covered.
I've just replaced my rasberry pi server with Logitech Media Server
Version: 8.0.1 - 1608617100
I've installed the community radio plugin on the server.
I've also installed the 'Version Comparison' Patch on the Squeezebox
radio and ticked the 're
dunk wrote:
> yep thats enabled too
so it turns out the system wouldnt download the new firmware because i
had a custom.baby.bin and custom.baby.version files in the updates
folder
dunk's Profile: http://forums.slimdevic
chill wrote:
> Every time I read through that paper I'm always taken by the care and
> attention to sound quality that went into the Boom's design.
Ditto. It must have been a fascinating and fun project to have worked
on.
kidstypike wrote:
> Have you seen this Boom .pdf?
Every time I read through that paper I'm always taken by the care and
attention to sound quality that went into the Boom's design. I always
get to the end, where the future possibilities are discussed, and regret
again the untimely demise of th
mrw wrote:
> 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 possibilitie
chill wrote:
> 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
MPO wrote:
> 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
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 pr
@MPO
As Slarti says, get up to date with Buster
[URL]https://www.max2play.com/en/download/46152/[/URL
groetjes
ronnie
Man in a van's Profile: http://forums.slimdevices.com/member.php?userid=43627
View this thread: htt
MPO wrote:
> 32743
>
> 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
> Platformarchitect
Man in a van wrote:
> Are you sure you are up to date ?
>
>
> L
32743
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
mrw wrote:
> 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,
MPO wrote:
> 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
401 - 500 of 610 matches
Mail list logo
