I'm in the process of migrating the build environment for Logitech Media
Server to a totally new system. The change hopefully will be transparent
to you.
Recent Mac builds already run on this new system, as the old Mac build
host died a few weeks ago. There should be no surprise here.
The
All players are on the same subnet 192.168.111.x and I did factory reset
of the boom but it did not help.
Boom can browse and communicate with the squeezebox server but would not
stream.
I think enabling debug logging for slimproto might tell you what server
IP is announced to the players when
earthbased wrote:
> Hi, been running 1.05a fine and dandy. If this is the case, is there
> any reason to upgrade to 1.07?Yes in v1.07 auto update is fix a.m.
Send from my mobile Phone
*
maintainer of QLogitechMediaServer, QOptware-NG and QAutoSub.
Qnap TS-453a, with LogitechMediaSever
mherger wrote:
>
> Hmm... might be a legacy from before Andy wrote Image::Scale.
>
Thanks. That was my thought.
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread:
Hi, been running 1.05a fine and dandy. If this is the case, is there
any reason to upgrade to 1.07?
earthbased's Profile: http://forums.slimdevices.com/member.php?userid=334
View this thread:
Boom binds either to the local LAN IP interface or the Public IP on the
Squeezebox server. It depends on how the server is started.
With httpaddr parameter it links with the server's NIC local IP but does
not stream and without it Boom binds to the public IP and streams fine.
Is the boom configured to talk to the internal or external address of
LMS server? (Assuming I have the right end of the stick..)
-Transcoded from Matt's brain by Tapatalk-
--
Hardware: 3x Touch, 1x Radio, 2x Receivers, 1 HP Microserver NAS with
Debian+LMS 7.9.0
Music: ~1300 CDs, as 450 GB of
I completely agree it makes no sense.
All players are on the same subnet 192.168.111.x and I did factory reset
of the boom but it did not help.
Boom can browse and communicate with the squeezebox server but would not
stream.
When httpaddr argument with the local IP address is used Squeezebox
boom, Squeezebox radio and duet receiver stop working. They do not
stream the local music and hang at "33% buffering" or thereabouts on
Internet radio. Also the spotify plugin is affected by the same.
There are no errors in the
*
To look if QLogitechMediaServer, will also work QNap nas systems with
QTS lower then 4.2.
I am looking for people how have a QNap, to test if it also works on
those !
So if you have a QNap system with the right architecture with QTS 4.1 or
lower send me a pm?*
*
maintainer of
Hi Michael,
I discovered possibly a new bug that is related to the httpaddr argument
regardless of the squeezeboxserver version or your patch. It may deserve
its own thread.
When httpaddr argument with the local IP address is used Squeezebox
boom, Squeezebox radio and duet receiver stop
But a quick question: do you know why the Linux platform build is
requiring libgd ? I can't see any obvious dependency. I have built with
it and without it, with no discernible effect - the built modules are
identical. So I'm wondering if my build is right, but I can't see which
package requires
mherger wrote:
>
> The packages already have huge overhead... and armel isn't that popular
> any more.
>
> Have you tried building yourself? It's not too difficult. Takes some
> patience, though...
>
> --
>
> Michael
Thanks for your response, understood.
With some application of
An app that binds to "all local addresses" when it opens a socket
doesn't do so in an order as such. The question is more about the way
the function decides which address to return when you ask what it is...
It should probably return all the addresses in a list in fact. The
ordering of that list
14 matches
Mail list logo
