Ive started from post 1 and gone through all of the thread. I have to
admit to not understanding most of it. I am a tecchie, but tends to be
Windows related and some high level networking. No experience of
streaming technologies.
_SYSTEM_OVERVIEW_
My system is Fujitsu ESPRIMO E3521
Inter
bpa wrote:
> How are the startup delay and the stop start issues ? I hope these were
> related to playing FlashAAC format.
Good as gold now ta :cool:
properjob's Profile:
properjob wrote:
> Back to 1.5.X :-
> With the new settings, listen again is indeed up to 320kbps on both
> iPlayer and iPlayer Extras. Awesome, ta!
How are the startup delay and the stop start issues ? I hope these were
related to playing FlashAAC format.
bpa wrote:
> Probably the first playing of 6music didn't work and LMS cached failure
> for next 1.5hrs as you kept refreshing the cache expiry by trying it
> repeatedly.
>
>
> 1.5.2 is intended as a betatest for users of 1.4 DASH version of plugin.
> 1.5.* series aim is to fix Windows problems
properjob wrote:
> 6 music listen again started working over an hour and a half later.
Probably the first playing of 6music didn't work and LMS cached failure
for next 1.5hrs as you kept refreshing the cache expiry by trying it
repeatedly.
> I wouldn't say clicking that one Livetext box
bpa wrote:
> Not sure what is working for your but after initially saying settings
> are as installed it is clear you have changed some settings. Your
> upgrade path is not clear (no version detailed) so chances are your
> settings are now in a mess.
>
Things were changing dynamically as I
properjob wrote:
> One comment on the new Iplayer Extras V1.9.5...
> .
> .
> .
> EDIT: I'll leave my original query in but that seems to have cured
> itself.
> .
> .
> .
> B]EDIT: DARN THING's WORKING NOW. FFS. [/B]I changed a setting called
> "show on air text" and it started working.
Not
OK, was using the previous versions with not too many issues (ref
Sticky: BBCiPlayer Plugins - an alternative quick fix guide), but
couldn't get listen again on the iPlayer to work. iPlayer Extras worked
ok so any listen again needs were catered for, left it alone.
Now tried using V1.5.2 &
slartibartfast wrote:
> We have two Radios playing the same station in the morning not
> synchronised. When one Radio has a 30 second interruption (rebuffering
> 0%) the other one plays straight through it. Is that expected?
Yes.
DASH is implemented using many sequential http request each
bpa wrote:
> Timeout can be changed it is matter of finding out which one is
> expriing for you.
>
> Can you double check what the duration felt like ? - it is 30 sec or 300
> secs ? Your logs looks like 35 or 27 ms ms - which is about 300
> sec or 5 mins.
>
> In the plugin I have
Gnq wrote:
> Many thanks. I removed an unworking version and installed v1.5.2 (and
> updated iPlayer Extras). Both now work very well (after attending to
> iPlayer Extras' setting re disabling DASH streams). Just one problem
> (one that originally surfaced when the BBC abandoned WMA) is the
Many thanks. I removed an unworking version and installed v1.5.2 (and
updated iPlayer Extras). Both now work very well (after attending to
iPlayer Extras' setting re disabling DASH streams). Just one problem
(one that originally surfaced when the BBC abandoned WMA) is the pitch
change. Live and
bpa wrote:
> You asked before about increasing the "delay" setting, I assumed it was
> at default. Can you confirm the value of the "Second to delay start of
> live stream" ?
I have not changed it so default 15 seconds.
Sent from my SM-G900F using Tapatalk
slartibartfast wrote:
> This may be of use. It is a debug log from just before an interruption
> until playback resumes 30 seconds later.
You asked before about increasing the "delay" setting, I assumed it was
at default. Can you confirm the value of the "Second to delay start of
live stream"
bpa wrote:
> A possible explanation. There is an IS8601 DateTime parameter in DASH
> MPD file which says when player can start live stream - BBC have set to
> this -15 secs - acting on BBC engineer comments I've been checking code.
> I found the library ISO8601 conversion routine to Epoch time
castalla wrote:
> Ah! Think that's solved it. Will test further during the day & report
> back
A possible explanation. There is an IS8601 DateTime parameter in DASH
MPD file which says when player can start live stream - BBC have set to
this -15 secs - acting on BBC engineer comments I've
Ah! Think that's solved it. Will test further during the day & report
back
Touch, Logitech Radio, Logitech UE Radio, O2 Joggler + SqpOS
UPnPBridge - 2 paired Sonos Play1 speakers; Rocki - Sony SRS-BTM8
speaker; Pioneer WX-SMA1 speaker; - PURE One Flow internet radio: PURE
Jongo S3x ;
castalla wrote:
> Settings: .. delay to start - no delay
Please return to default setting of 15 secs. Following comments by BBC
streaming engineer "No delay" is not right - this may not be the problem
but it doesn't please BBC.
bpa wrote:
> thanks, I didn't unserstand your "BBC" and "all players" ref in earlier
> post - now I'm guessing you meant all LMS players.
>
> The fifteen sec delay is strange as the log I cannot see where the delay
> is coming from.
> Are you doing a test where you skip from one station to
castalla wrote:
> Difficult to say - as PC is already slow - but maybe 2-3 secs. Just
> tried R4 on LMS - 15 secs to play
thanks, I didn't unserstand your "BBC" and "all players" ref in earlier
post - now I'm guessing you meant all LMS players.
The fifteen sec delay is strange as the log I
bpa wrote:
> Do you mean the delay is there on BBC web player site ?
Difficult to say - as PC is already slow - but maybe 2-3 secs. Just
tried R4 on LMS - 15 secs to play
Touch, Logitech Radio, Logitech UE Radio, O2 Joggler + SqpOS
UPnPBridge - 2 paired Sonos Play1 speakers; Rocki - Sony
bpa wrote:
> The "Connection timed out" without any other messages mean the network
> interface on server is up but the destinmation hosts does not respond to
> the initial TCP connection. Without other chunk request timeout message
> it means no outstanding chunk requests so usual stream
castalla wrote:
> The delay in sound is there for all players on BBC
Do you mean the delay is there on BBC web player site ?
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread:
bpa wrote:
> Not synced to another player ?
No sync
The delay in sound is there for all players on BBC
Touch, Logitech Radio, Logitech UE Radio, O2 Joggler + SqpOS
UPnPBridge - 2 paired Sonos Play1 speakers; Rocki - Sony SRS-BTM8
speaker; Pioneer WX-SMA1 speaker; - PURE One Flow internet
castalla wrote:
> That was to a Touch - no transcoding, as far as I know
Not synced to another player ?
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread:
bpa wrote:
> Just a quick look through and it seems the plugin has got 12 secs of
> audio within 1 secs of track starting - after that it fetches a chunk
> every 6 secs which is as expected.
>
> What sort of player are you using ? Is it transcoding ? Is it a
> Chromecast or uPNP or similar ?
castalla wrote:
> Here's a log -
Just a quick look through and it seems the plugin has got 12 secs of
audio within 1 secs of track starting - after that it fetches a chunk
every 6 secs which is as expected.
What sort of player are you using ? Is it transcoding ? Is it a
Chromecast or uPNP or
bpa wrote:
> Those are the reponse time from BBC/CDN to a request from plugin - so
> that says there is a small netwrok issue outside your control However
> 12 secs is 2 chunks so the above delay does not explain 12 secs starts -
> perhaps there is a delay in getting either or both of the MPD
slartibartfast wrote:
> >
Code:
> > [17-01-19 08:54:56.0440] Plugins::BBCiPlayer::DASH::__ANON__ (706)
error fetching [232002468] Status=596 Reason: Connection timed out Fetch time
27 ms
>
> >
>
> Looks like the same message I always see
bpa wrote:
> Can you copy log message please. They tell a lot more than you think.
Code:
[17-01-19 08:54:56.0440] Plugins::BBCiPlayer::DASH::__ANON__ (706) error
fetching [232002468] Status=596 Reason: Connection timed out Fetch time 27
ms
slartibartfast wrote:
> Usual connection timed out message in the server log when playback
> stopped this morning at 8.50 but no rebuffering message on screen. No
> restart after 30 seconds either. I had to stop the stream and restart
> manually.
Can you copy log message please. They tell a
Usual connection timed out message in the server log when playback
stopped this morning at 8.50 but no rebuffering message on screen. No
restart after 30 seconds either. I had to stop the stream and restart
manually.
Sent from my SM-G900F using Tapatalk
bpa wrote:
> Not sure since you haven't said where you are looking nor what UI (e.g.
> Web Touch ) you are using ?
Sorry my bad for a) not giving a decent issue report and b) for not
waiting before a did a reboot
I changed to Dash as main format
I rebooted LMS
And now it's there... not
Giza2020 wrote:
> Am I missing something very very obvious?
Not sure since you haven't said where you are looking nor what UI (e.g.
Web Touch ) you are using ?
bpa's Profile:
I am sure I'm going to kick myself for asking something stupid... but in
the latest version of the BBCiplayer I cannot find the skip back/forward
options.. where I use to see it when listening to live streams I can now
only see stream info and an 'on spotify' option.
Am I missing something very
bpa wrote:
> Those are the reponse time from BBC/CDN to a request from plugin - so
> that says there is a small netwrok issue outside your control However
> 12 secs is 2 chunks so the above delay does not explain 12 secs starts -
> perhaps there is a delay in getting either or both of the MPD
PasTim wrote:
> Which still leaves me (and possibly many others) in the dark ;)
As I read it Radio2t/m6 means Radio 2 up to and include Radio 6
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View
Man in a van wrote:
> Tot/met is up to and including u/i
Which still leaves me (and possibly many others) in the dark ;)
LMS 7.9 on VortexBox Midi box, Xubuntu 16.04, FLACs 16->24 bit,
44.1->192kbps.
LMS plugin UPnP/DLNA Bridge to MF M1 CLiC (to A308CR amp & ESLs) &
Marantz CR603 UPnP
With
Man in a van wrote:
> I sometimes use Dutch expressions, which come readily to mind, instead
> of English language.
> Tot/met is up to and including u/i
and > Maybe it's a mañana thing?
A polyglot.
re: "mañana" in Ireland we don't have any word that has the same sense
of urgency.
bpa wrote:
> I don't listen to R2 do can you explain what t/m6 is ? Was it on alarm
> ?
>
Ah, sorry about that, nothing to be alarmed about :D (see what I did
there?).
It's just that for some strange reason (a left over from my working
days, I think)
I sometimes use Dutch expressions, which
castalla wrote:
> Haven't changed anything ...
>
> Log:
>
> [17-01-18 10:25:35.7723] Plugins::BBCiPlayer::DASH::__ANON__ (696)
> status 200 Long chunk fetch time 1055 ms
> [17-01-18 10:25:37.0601] Plugins::BBCiPlayer::DASH::__ANON__ (696)
> status 200 Long chunk fetch time 2362 ms
>
bpa wrote:
> Any message in log file ?
> BBC DASH streaming engineer says they are getting lots of 404 from my
> plugins but I have yet to find user with one in the log ?
>
> I found a small bug which means in next rev BBC stream will have to
> start 15 secs earlier (defined in BBC MPD for
castalla wrote:
> I've noticed that recently all BBC stations take seconds (upto 12 secs)
> to start. Previously, they all fired up almost instantly.
>
> No changes to setup (test iplayer using dash) other that LMS nightly
> updates.
Any message in log file ?
BBC DASH streaming engineer says
Man in a van wrote:
> I Radio2t/m6
I don't listen to R2 do can you explain what t/m6 is ? Was it on alarm
?
I was involved a little bit when alarm clock was being developed and for
such a small feature it had loads of feedback and lots of grief for the
developers ("I nearly lost my job
castalla wrote:
> I've noticed that recently all BBC stations take seconds (upto 12 secs)
> to start. Previously, they all fired up almost instantly.
>
> No changes to setup (test iplayer using dash) other that LMS nightly
> updates.
In the UK, using LMS v7.9 from Jan 5th, skipped through
bpa wrote:
> I've been playing R4 all afternoon with only an occasional long delay
> (e.g. 7 sec response time) but no break until 17:23 when I got the 596
> error as follows
> >
Code:
> >
> 17-01-17 17:23:11.5779] Plugins::BBCiPlayer::DASH::__ANON__ (739) Retrying
bpa wrote:
> OK. To get HTTP 1.1/ with persistent TCP functionality I used a 3rd
> party module - it looks like I haven't told the module correctly to
> shutdown and there are still timers running.
I've noticed that recently all BBC stations take seconds (upto 12 secs)
to start. Previously,
bpa wrote:
> Are all these timeout problems related by using alarm to initially play
> the stream ? It seems to be an alarm interaction. I have found when
> trying to play an alarm first thing after a system (and associated
> network) been unused overnight - some parts of network are in low
I've been playing R4 all afternoon with only an occasional long delay
(e.g. 7 sec response time) but no break until 17:23 when I got the 596
error as follows
Code:
17-01-17 17:23:11.5779] Plugins::BBCiPlayer::DASH::__ANON__ (739) Retrying
after error fetching
slartibartfast wrote:
> The alarm was triggered at 6.00am so played normally for 45 minutes
> before playback stopped. I see interruptions when playback is started
> manually as well. I have just moved the router slightly and the reported
> wireless signal strength at the Radio has increased
bpa wrote:
> Are all these timeout problems related by using alarm to initially play
> the stream ? It seems to be an alarm interaction. I have found when
> trying to play an alarm first thing after a system (and associated
> network) been unused overnight - some parts of network are in low
slartibartfast wrote:
> One of the interruptions this morning was at 6.45 during the alarm
> period. I turned off the alarm when the disco sound started and
> restarted the radio stream. I have now checked the server log and see
> this
>
> 17-01-17 06:50:20.3962]
bpa wrote:
> Timeout can be changed it is matter of finding out which one is
> expriing for you.
>
> Can you double check what the duration felt like ? - it is 30 sec or 300
> secs ? Your logs looks like 35 or 27 ms ms - which is about 300
> sec or 5 mins.
>
> In the plugin I have
bpa wrote:
> Timeout can be changed it is matter of finding out which one is
> expriing for you.
>
> Can you double check what the duration felt like ? - it is 30 sec or 300
> secs ? Your logs looks like 35 or 27 ms ms - which is about 300
> sec or 5 mins.
>
> In the plugin I have
slartibartfast wrote:
> It does restart after thirty seconds I just wondered if that timeout
> could be reduced. The most annoying time for the interruption is during
> the morning alarm period where the radio falls back to the default alarm
> sound after a time.
Timeout can be changed it is
bpa wrote:
> The plugin does knows when a timeout occurs and it should just continue
> after the 30 secs wait. It does not stop for me - now I understand your
> persistence. Strange.
> For reference what is your setup OS, LMS version, processor, player etc.
> On what do you play the stream ?
slartibartfast wrote:
> Does the plugin "know" that playback has stopped in these circumstances?
> I can restart the stream manually immediately without waiting for the
> timeout. If the plugin could restart the stream automatically or the
> timeout was shorter these stoppages would be less
bpa wrote:
> I've had similar problem with HLS - as both DASH and HLS are delivered
> by the same CDNs, server and BBC sources. Theoretically 1.5.2 should be
> better (lower host network & server load) as it uses HTTP 1.1 over a
> persistent TCP connection (i.e TCP connection is kept open for
slartibartfast wrote:
> I have actually tried both CDNs with similar results unfortunately. I
> don't really want to revert to HLS as the skip back can be useful.
I've had similar problem with HLS - as both DASH and HLS are delivered
by the same CDNs, server and BBC sources. Theoretically 1.5.2
bpa wrote:
> Debugging won't help - this means no response from CDN/BBC for a request
> (timeout is 30 secs). Plugin can do nothing if BBC doesn't respond
> except stop and try again.
>
> I get some of these and I have run parallel tests with Web browser
> playing DASH and Plugin and both get
slartibartfast wrote:
> with the logging for plugin.bbciplayer.dash set to error. Should I set
> logging to debug?
Debugging won't help - this means no response from CDN/BBC for a request
(timeout is 30 secs). Plugin can do nothing if BBC doesn't respond
except stop and try again.
I get some
bpa wrote:
> Start delay is really only for Windows and is only there to help the
> startup of the socketwrapper transcoding chain typically on low end PC
> systems. It will no really do anything on Linux except change the start
> time of the stream (i.e. the timecode of
>
> the first packet).
slartibartfast wrote:
> A couple of times most mornings Radio 2 will stop accompanied by
> "rebuffering 0%". 30 seconds later I see "rebuffering failed" and
> playback restarts. Should I try increasing the start delay? Using Linux.
Start delay is really only for Windows and is only there to
A couple of times most mornings Radio 2 will stop accompanied by
"rebuffering 0%". 30 seconds later I see "rebuffering failed" and
playback restarts. Should I try increasing the start delay? Using Linux.
Sent from my SM-G900F using Tapatalk
bpa wrote:
> Program and track info come from separate feeds - there is no indication
> of news breaks or other items being broadcast in the track feed so it is
> either track data or program data . Also track feeds often is not
> updated in late evening and night so for example in late evening
slartibartfast wrote:
> (1) Time sync would be a problem when pausing and rewinding but if track
> info was only available during live playback that would be enough.
> (2) Most of the time only track info needs to be shown. Program
> description info could be shown during news breaks or other
bpa wrote:
> It's mot impossible but
> (i) there is no way to sync the time of the track so at night you could
> be shown track info from 7pm. You can see this on BBC own Web Browser
> iPlayer. It gets worse if people pause/delay the track as track info is
> realtime so if you go back to start
slartibartfast wrote:
> It looks like this feature does not show track info as scrolling text in
> the same way as the on air text when the station logo is displayed but
> instead as a separate menu item. The ideal situation for me would be for
> the program image to be displayed but with the
bpa wrote:
> The experimental track feature is described here
> http://forums.slimdevices.com/showthread.php?106409-BBCiPlayer-V1-5-2-beta-test=867456=1#post867456
It looks like this feature does not show track info as scrolling text in
the same way as the on air text when the station logo is
slartibartfast wrote:
> Actually I just realised track info is available on the iplayer app
> further down the page. Maybe this is the info your new latest tracks
> feature uses. I 'll try it.
The experimental track feature is described here
slartibartfast wrote:
> Looking at the iplayer app on my phone it seems that track info is not
> available there either.
>
> Sent from my SM-G900F using Tapatalk
Actually I just realised track info is available on the iplayer app
further down the page. Maybe this is the info your new latest
slartibartfast wrote:
> If I select "always display station icon" and "on air text" then I see
> track info for radio 2 and radio 6. If I then deselect "always display
> station icon" I see the program image and a program description but no
> track info.
>
> Sent from my SM-G900F using Tapatalk
If I
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=106409
Jeff07971 wrote:
> All seemed fine this morning and no BBCiPlayer entries in the logs.
Certainly odd but thanks for reporting. I "feel" it may be something to
do with alarm which can do persistent retries to play a station - the
plugin delay in getting packets may be clashing with the alarm
Hi Bpa,
All seemed fine this morning and no BBCiPlayer entries in the logs.
Fingers crossed, thanks for looking though!
Jeff
*Players:* SliMP3,Squeezebox3 x3,Receiver,SqueezePlayer,PiCorePlayer
x3,Wandboard
*Server:* LMS Version: 7.9.0 - 1475786002 on Centos 7 VM on ESXi 6 on
Dell T320
bpa wrote:
> Status 200 means the packet was received so the bulk of the message are
> receive but the dleay are long - I would expect 100-200ms. The delay is
> measured by noting when ther equest packet was sent and the time
> response was received assiming OS clock is OK - the cause is the
Jeff07971 wrote:
> There are some (really) long "fetch times" in the log though
Status 200 means the packet was received so the bulk of the message are
receive but the dleay are long - I would expect 100-200ms. The delay is
measured by noting when packet was sent and the time was received
bpa wrote:
> Nothing in the URL should initiate a delay.
>
> Had you played this url within the previous 24 hours ?
> If so did you delay the stream ?
> Did you delay any BBCiPlayer live stream stream in the previous 24 hours
> ?
>
> LMS caching in some cases has a long expiry and I'm
Nothing in the URL should initiate a delay.
Had you played this url within the previous 24 hours ?
If so did you delay the stream ?
Did you delay any BBCiPlayer live stream stream in the previous 24 hours
?
LMS caching in some cases has a long expiry and I'm wondering whether
somehting is being
Hi Bpa,
I took this from the GUI (See SS) if theres a better place let me know
!
Code:
Jeff07971 wrote:
> Also while the alarm started at the correct time (0730) the program was
> the one that was on 87 minutes ago IE Chris Hawkins !!
What URL is being used in the alarm to play the stream ?
bpa's Profile:
Hi Bpa,
The time on the server is what I thought as well but as I said it was
correct within 1 second, I've just rechecked:-
Code:
[root@myserver ~]# ntpq -crv -pn
associd=0 status=0618 leap_none, sync_ntp, 1 event, no_sys_peer,
version="ntpd 4.2.6p5@1.2349-o
With Live streams each packets has an URL which contain the time of day
based on a reference time.
The estimated delay is a calculation using the time code of the packet
against the LMS sever time as supplied by the OS. This seems to say
your LMS server time setting could be wrong.
Hi Bpa
Had a rude awakening today.
I have as an alarm BBCi Player Radio 6 Music set for 0730Hrs
I was awoken at 0730Hrs by a very loud Radio 6 Music playing (it made me
jump so much I hurt my back), I bleerily turned it down to a more
reasonable level and slowly woke up.
As I lay there I
Atlantic wrote:
> I would have had no idea that the time of day setting could be critical
> to music streaming.
It's not but the way live streaming is done in DASH as implemented by
BBC - each6 sec chunk is timestamped. If a user pauses the simplest way
to guess how much delayed was to compare
bpa wrote:
> The following is an explanation why I think DNS should not be the main
> source of your issue even with your satellite links.
>
> First a general comment about SB player - When and SB player (e.g.
> Touch) plays any stream (http/MP3, http/AAC, HLS or DASH) using a local
> LMS - the
Atlantic wrote:
> On transactions requiring multiple, sequential DNS lookups, the delays
> caused by DNS alone can be a couple of seconds and we find this is
> usually sufficient to knock over any real-time services. We try to make
> sure that time-sensitive equipments and applications only
kidstypike wrote:
> Pausing a stream causes the effect you're seeing, the minutes next to
> the title increment by 1 for every minute paused.
>
> It possibly happens for other reasons, not sure.
To see a 23 min delay the user will have to had pressed paused and
waited for 23 mins - I don't
Pausing a stream causes the effect you're seeing, the minutes next to
the title increment by 1 for every minute paused.
It possibly happens for other reasons, not sure.
+---+
|Filename: Pic03.jpg
Atlantic wrote:
> I wondered, but BBCiPlayer 1.3.x seemed to work. If, indeed, that turns
> out to be the case, do you recall how or whether I could return to
> BBCPlayer 1.3.x*, which I think I had before this update?
I'll study the rest of the note later (I see the mention of satellite
links
bpa wrote:
> I think LMS maybe too old as 7.5 is very very old.
>
>
I wondered, but BBCiPlayer 1.3.x seemed to work. If, indeed, that turns
out to be the case, do you recall how or whether I could return to
BBCPlayer 1.3.x*, which I think I had before this update?
bpa wrote:
>
>
> Your
I think LMS maybe too old as 7.5 is very very old.
Your descirption of previous use is very confusing (128kbps MP3 , R3 320
is probably AAC) but then you mention iPlayer - did you use BBCiPlayer
or not and did you have proiblemn befroe with BBCiPlayer plugin ?
Something very strange is
I installed 1.5.2 yesterday on our Linux (Debian) SBS version 7.5, from
repo
"
http://downloads.sourceforge.net/project/bpaplugins/betarelease-repo.xml
".
We're in the UK and use a major UK ISP. 1.5.2 isn't working for me,
tested using our SB Touch. Two symptoms are:
(i) The playing title,
Owen Smith wrote:
> Thanks. I've never heard it called SqueezeNetwork before and it seems a
> strange name. I'd ask what aspect makes it a network and not a server,
> but that's rather off topic for this thread.
In the beginning I think Slimdevices operated their own nertwork of
servers before
Paul Webster wrote:
> SqueezeNetwork (mysqueezebox.com)
Thanks. I've never heard it called SqueezeNetwork before and it seems a
strange name. I'd ask what aspect makes it a network and not a server,
but that's rather off topic for this thread.
Owen Smith wrote:
> I thought SN was some abbreviation for DNS server, but bpa's last post
> makes it clear it isn't. So please, what does SN stand for in this
> context? (I doubt it's Serial Number.)
SqueezeNetwork (mysqueezebox.com)
Paul Webster
http://dabdig.blogspot.com
I thought SN was some abbreviation for DNS server, but bpa's last post
makes it clear it isn't. So please, what does SN stand for in this
context? (I doubt it's Serial Number.)
Owen Smith's Profile:
Jeff07971 wrote:
> Yes I see that does sound reasonable, but maybe its time for a change to
> LMS.
>
> Anyway its a bit off topic so we can leave it there.
>
> BTW Been trying 1.5.2 for a couple of days, no problems at all so far.
Yep - it's a minro point. If user needs to access SN it will
> No - perhaps a user has turned off the router while away but left all
> other system on -also LMS was created in the days of slow connections
> and pay per bit so developers were asked to keep overheads down and SN
> connection wasn't as important as it is now with Touch devices and some
>
Jeff07971 wrote:
> Bit excessive though, wouldn't you agree ?
No - perhaps a user has turned off the router while away but left all
other system on -also LMS was created in the days of slow connections
and pay per bit so developers were asked to keep overheads down and SN
connection wasn't as
401 - 500 of 604 matches
Mail list logo
