Tidal Hi-Fi - partial track load bug back again?

I’ve found a significant difference for track load times from Tidal between IPv4-only networks and networks with IPv6 enabled…not simply at home (where I have a native v6 connection and network configured to make use of it), but in 2 other places as well: the v4-only network with 100Mbps DL speeds was slower than the dual-stack (v6 enabled) 5Mbps connection. re-read that: a 20x slower connection loaded tracks faster over v6 than v4. It shouldn’t happen because "it doesn’t or shouldn’t matter, " but having seen it with my own eyes, I’ve started to reconsider

While we may not care to put some time into learning these things, it’s a matter of needing to know to do our jobs/have great gigs/look professional and knowlegable, and that includes some basic troubleshooting of the medium/systems we rely on to get what we need to use.

1 Like