Released as official firmware 11.1 for you. Please try it and see if it helps.
"dropouts" still ?
- Thread starter srt
- Start date
Released as official firmware 11.1 for you. Please try it and see if it helps.
Hello Peter,
I am experiencing frequent dropouts (to the point where it has become unusable) playing MQA files from Tidal, I have been assuming that it was due to internet speed and have addressed it with my ISP to no avail. I am under the impression that MQA does not use more bandwidth than non MQA ?? There is a significant lag before an album starts with MQA, upwards of 10 seconds , whereas with other files it is three or four seconds, I assume this is because of buffering? Now I am wondering if it is a problem with my settings on the Lumin. I am using a T1 and have no problems when playing from my L1. Do you have any suggestions?
Regards
Rod
I am experiencing frequent dropouts (to the point where it has become unusable) playing MQA files from Tidal, I have been assuming that it was due to internet speed and have addressed it with my ISP to no avail. I am under the impression that MQA does not use more bandwidth than non MQA ?? There is a significant lag before an album starts with MQA, upwards of 10 seconds , whereas with other files it is three or four seconds, I assume this is because of buffering? Now I am wondering if it is a problem with my settings on the Lumin. I am using a T1 and have no problems when playing from my L1. Do you have any suggestions?
Regards
Rod
After FLAC compression, MQA uses roughly double the bandwidth of the normal files, or more. It uses the same bandwidth only if we count decompressed PCM in 24-bit, but that's not the case for streaming.
The lag is indeed caused by buffering.
Where are you located? It's a Tidal server capacity issue, not usually an ISP issue if you have a reasonable broadband connection. You can send a request to Tidal.
It's not a Lumin setting problem, but by turning off MQA, the bandwidth is reduced since Lumin will get a smaller version.
Thanks Peter,
I am in rural South Africa, bandwidth is limited to 4mbps which is fine for movie streaming but I am not sure if thats sufficient for MQA. I will contact Tidal as you suggest.
I owned T1. After doing this, tidal response time is more acceptable.
Discuss with your ISP to create “Static routing to Tidal Servers”. It will reduce network latency, and get better Tidal Network Connection. I believe it is not bandwidth problem. It consumes about 3 mbps during network consumption spike. Please make sure that no other network devices are used during MQA streaming.
Delay on the first song is normal for Tidal Service at this moment.
My ISP had increased my download speed from 4 to 6mbps and this has solved the problem with MQA files. My T1 buffers prior to playing at the maximum of 6mbps and then continues for some while at about 1.6mbps while it is playing
Thanks for all the suggestions
Thanks for all the suggestions
mark090852
New member
I just received my Lumin D2 two days ago, and have also been having random dropouts from Tidal. Not just when streaming in MQA, but also other times. The sound will stop, even though the app shows the music is playing. Sometimes it just last for a second or two, other times much longer. It seems as if, during these times of dropouts, that the "pause" button does not stop the song from "soundlessly" continuing. I power cycle my router and the Lumin and my Ipad, and this will correct the problem for a while, but the dropouts came back after a short while. The app shows that I have firmware version 11.1b. Any suggestions?
still-one
Active member
I have no idea if this will help with your Lumin issue but my dropouts had nothing (or little) to do with my audio gear. Unfortunately I ended up changing from an Apple to Netgear Orbing network almost simultaneously when moving from the Rossini to my Vivaldi stack. what was causing the dropouts? Was it my Tidal, my Upsampler or DAC or Network or sonicTrransporter?
To make a long story short Andrew from Small Green Computer suggested I insert a TrendNet switch between my Orbi router and my Upsampler and i5 rather than connecting them direct to the Orbi. That solved my dropout issues immediately. (I had tried a TPlink unit but the dropouts remained).
Based on my experience, I suggest that you look/check your internet speed and connection. If your router is old, you may want to replace it. New routers can create a mesh that improves transmission throughout your entire house.
mark090852
New member
I really don't think that is the problem. I just tested my connection and I'm at 64.17 Mbps download, and 6.62 Mbps upload. My listening room is the same room that my router is in, so the WiFi signal strength to my Ipad running the Lumin app is reading full strength. I'm guessing it is a problem with the TIDAL servers as some others have seemed to indicate. I'll keep monitoring this thread and see if any other suggestions show up. One interesting thing I have noticed is that when a dropout occurs, the timer on the display on the front of the Lumin and in the app continues to run. However, once it gets to the end time, the music continues and runs beyond the time indicated. In other words, if I have a 15 second dropout, for example, in the middle of a song, the music will continue for 15 seconds beyond the timer showing the song is over. So I am getting the full track, just with a 15 second break in the middle.
I haven’t experienced any dropout issues with my LUMIN S1 over the last couple of years. My S1 is connected to the router via an Ethernet cable. I had some dropout issues several years ago when the network configuration included a wireless extender (not the best solution).
Tidal server issues are regional, and are usually not related to your own ISP connection. Please try changing the DNS in your router settings to 8.8.8.8, 1.1.1.1 or auto. See if it makes any difference. If it does not, please submit a support request to Tidal.
mark090852
New member
Peter, I followed your recommendations regarding changing the DNS settings, and it has been working perfectly since then. Thank you!
Mark