Problems with drop-outs using AMAZON or TIDAL - Read this!
Completed
Those infrastructures rely heavily on ECS (EDNS client subnet) function of a DNS.
Technically this function does find the nearest and mostly best infrastructure for serving your needs.
Somehow in the past these functions grew of importance for these services and they began to drop-out while re-buffering more frequently until it became impossible to listen to one track without interruption.
So when I changed from my local resolver unbound to one of those DNS servers, the streaming was as of currently uninterrupted:
Quad9 DNS address (with ECS): 9.9.9.11 AND 149.112.112.11
Googles DNS address: 8.8.8.8 AND 8.8.4.4
Don't forget, this is only a small portion of a functioning network, but can be a base cause, when the rest of your network was always behaving rock-solid.
Happy streaming!
-
Official comment
Our Support Crew often also recommends CloudFlare 1.1.1.1 to EU and Asian-based consumers...
-
I tested the Cloudflare service as well, but I had drop-outs after one day here in Germany on Telekom-network using AM HD.
This is a complex problem that is totally dependant on geographic network-infrastructure plus your providers infrastructure (to make things more complex)
Cloudflare is not using ECS but is using other measures for geographical detection. That might work for one, but there's no easy solution for everyone.
I think there's a lazyness of the big music services to enhance proper infrastructure automatism on their own including the APIs, which has now to be solved on the network layer - meaning implementers and users.
I wonder, how Spotify will perform once they start lossless....
0
Please sign in to leave a comment.
Comments
2 comments