I had my first drop out this morning. Lasted about 2 seconds. Was just playing redbook via Tidal.
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
After some pro-MQA announcement, something from the opposite side:
https://www.computeraudiophile.com/...by-another-pro/?do=findComment&comment=712977
FYI only. Disclaimer: Posting links do not imply I agree with the contents.
I had my first drop out this morning. Lasted about 2 seconds. Was just playing redbook via Tidal.
Sent from my iPhone using Tapatalk
You know Peter, if you want to find any negativity about computer audio, your hearing, AB testing, blind testing, downloads, DACS, formats, CA is the place. Man that place will leave you depressed. So darn negative. Makes me want to spin a LP and heck with dacs, streamers, cables, testing.
You know Peter, if you want to find any negativity about computer audio, your hearing, AB testing, blind testing, downloads, DACS, formats, CA is the place. Man that place will leave you depressed. So darn negative. Makes me want to spin a LP and heck with dacs, streamers, cables, testing.
That's true. I suppose you have not read discussions about vinyl distortions from CA.opcorn:
Yes. 27.1 mbps.
Sent from my iPhone using Tapatalk
Chris
My IPv4 feed is coming from Jax while the IPv6 feed is coming from an FSU research facility, so it may not be long before you start to see some more effects in your area at least on one side of the signal. Unless they start making moves to correct the issues pretty quickly it is probably not going to end well. I suspect the appropriate people at the streamer companies are aware of the problems coming.
Chris
I understood what you were saying, the ISP is faster than Tidal, same here though the disparity is not as great until the stuttering starts. My point was that if it is happening here it will probably start getting more frequent where you are as part of my feed is coming from your area. It may take a while as you are 200 miles closer to the Jacksonville feeds than me. The backlog should start farther out from the hub and work back to the center. Maybe they will be proactive and take the steps to increase capacity before the major population centers are effected. Time will tell how the Tidal "braintrust" chooses to handle it.
Our programming team confirmed with me that this is a known issue that is affecting a number of users, which has placed it at the top of their list to fix.
While I don’t have a timeline as to when a fix will go through, please know that our team is working to resolve the issue as soon as possible.
We realize that this is an inconvenience for you, so we thank you for your patience.