Hello,

As a newbie here, I’d like to say first and foremost a big thanks to all
of you who work to keep the LMS and associated “stuff” working; I’ve
been using it daily for 10 years and love it.

Here’s my problem: about 3 months ago I signed up with Tidal (regular
not HiFi) and for the first few weeks it was fantastic; we have 2x Boom,
3x UE Radio (running Squeezebox firmware), 1x SqueezePlay on Win10, 1x
SoftSqueeze on Win10, and LMS running on a Synology DS918+. We have a
Gigabit wired backbone and 8 wireless APs (due to thick stone walls). We
could play Tidal synced to all players through the whole building… it
was perfect! 
Then Tidal started skipping tracks; I’d line up an album and it would
start playing the first track and then after a few seconds skip to the
next track, play a bit of that and then proceed to similarily skip
through the remaining tracks, sometimes up to a minute, some not even
starting. It happens regardless of using one or multiple players, wired
or wireless.
I’ve been pulling my hair out trying to analyse what the problem(s)
could be. I can only play Tidal music with no skipping if I change the
player music source to mysqueezebox.com and thus bypassing LMS. Playing
Tidal music via the app on the iPhone over WLAN is problem free.

I have upgraded to LMS 8. I have rebooted the ADSL router (an Orange
Livebox V4). The Synology NAS is at the current DSM level, and it has a
CPU load of below 10% when LMS is running, memory utilisation is 20%,
16% of a 20TB RAID5 volume used, all healthy. I don’t believe it is a
LAN/WLAN problem as everything works perfectly playing 320kbps mp3s from
the NAS on LMS 8. We have an average ADSL internet performance of 14 / 1
mbps in/out, and Netflix/VuDu work fine; I’ve tried stopping everything,
but it doesn’t seem to be internet bandwidth related.  

Having said that, Squeezeplay has a “Buffering” - “Now Playing” -
“Connecting”, “Buffering” - “Now Playing” - “Connecting” cycle where the
buffering gets up to  about 30% progress, the track starts playing, then
the buffer goes back down to about 10% and then skips to the next track.


Looking at the LMS log file it seems to be trying to connect to
www(dot)mysqueezebox(dot)com a lot:
"[20-09-14 16:54:14.9467] Slim::Networking::Async::DNS::resolve (43)
Using cached DNS response 63.34.162.152 for
www(dot)mysqueezebox(dot)com
[20-09-14 16:54:15.5622] Slim::Networking::Async::DNS::__ANON__ (75) Got
DNS response 151.101.122.142 for ab-pr-fa.audio.tidal.com (ttl 30)
[20-09-14 16:54:28.8507] Slim::Networking::Async::DNS::resolve (43)
Using cached DNS response 63.34.162.152 for
www(dot)mysqueezebox(dot)com
[20-09-14 16:54:29.3745] Slim::Networking::Async::DNS::resolve (43)
Using cached DNS response 151.101.122.142 for ab-pr-fa.audio.tidal.com
[20-09-14 16:54:42.4413] Slim::Networking::Async::DNS::resolve (43)
Using cached DNS response 63.34.162.152 for
www(dot)mysqueezebox(dot)com
[20-09-14 16:54:42.9871] Slim::Networking::Async::DNS::resolve (43)
Using cached DNS response 151.101.122.142 for ab-pr-fa.audio.tidal.com
[20-09-14 16:54:47.7680] Slim::Networking::Async::DNS::resolve (43)
Using cached DNS response 63.34.162.152 for
www(dot)mysqueezebox(dot)com
[20-09-14 16:54:48.3835] Slim::Networking::Async::DNS::__ANON__ (75) Got
DNS response 151.101.122.142 for ab-pr-fa.audio.tidal.com (ttl 30)"

When I ping www(dot)mysqueezebox(dot)com (from anything on our network)
I get:
C:\Users\N>ping www(dot)mysqueezebox(dot)com

Pinging www(dot)mysqueezebox(dot)com [34.244.111.131] with 32 bytes of
data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 34.244.111.131:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

However  ping www(dot)google(dot)com[/url] is OK:
PING www(dot)google(dot)com (216.58.204.132): 56 data bytes
64 bytes from 216.58.204.132: icmp_seq=0 ttl=113 time=23.254 ms

I guess that the problem is related to connectivity to
www(dot)mysqueezebox(dot)com ??? 
Odd though that Tidal seems to work on a player (somehow?) connected to
mysqueezebox.com.
I'm starting to wonder if this could be a problem with our internet
provider primary / secondary DNS?

Any ideas / suggestions how to proceed would be most gratefully
accepted!
Many thanks,
Nico


------------------------------------------------------------------------
Niconico's Profile: http://forums.slimdevices.com/member.php?userid=70661
View this thread: http://forums.slimdevices.com/showthread.php?t=112933

_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter

Reply via email to