Tidal keeps stopping on the NDS

Posted by: Laxton Yeo on 18 October 2015

I've just upgraded to the latest firmware 4.4 for The NDS. Tidal works fine but 50% of the time, it would play a song for about 30 seconds and stops playing. Pressing play plays the song from the start which is very irritating.

My internet connection is a dedicated fiber line in Singapore with 500mbps bandwidth. I'm using a direct cat6 cable to the router. My uPNP works fine. The issue happens less often when I select high quality instead of Hifi for Tidal streaming .

I've tried streaming the same songs over wifi on a iPad with quality set as Hifi and adaptive streaming turned off. Hifi quality plays back without issues on the iPad.

I have written to Naim and the reply I got was it is due to bandwidth issues. This isn't too convincing as Hifi streams fine on the iPad.

Has anyone experienced any similar issues on their streamer?
Posted on: 29 November 2015 by Trevor Wilson

hi all

 

just to update another beta went out this weekend

 

Trevor

Posted on: 29 November 2015 by Dustysox

Hi all,

 

Getting server error message, just me?

Posted on: 29 November 2015 by Goon525

Not just you. Tidal not working right now. Wants me to sign in again, but won't accept the data.

Posted on: 29 November 2015 by hungryhalibut

It's playing happily here. Mind you, I'm running the latest beta. 

Posted on: 29 November 2015 by ChrisSU
Originally Posted by Hungryhalibut:

It's playing happily here. Mind you, I'm running the latest beta. 

Same here.

Posted on: 29 November 2015 by Goon525

Working again now. First time I've had a significant problem.

Posted on: 29 November 2015 by Dustysox

Yes, working here agin...phew!

 

If this new technology is to be a success they really need to make it more reliable. Harsh Dusty, maybe but the public ain't gonna mess with something that works then doesn't then does....!

Posted on: 29 November 2015 by Simon-in-Suffolk

Dusty, the latest beta firmware is a lot more reliable.. effectively the Naim code has been optimized to work with unreliable data throughput from streaming services......

Simon

 

Posted on: 29 November 2015 by Dustysox
Originally Posted by Simon-in-Suffolk:

Dusty, the latest beta firmware is a lot more reliable.. effectively the Naim code has been optimized to work with unreliable data throughput from streaming services......

Simon

 

Thank you Simon. The forum is so much richer for your input. You are indeed a mighty fine person. 

 

I look forward to the public release. I am enjoying Tidal more than I thought I would. 

Posted on: 30 November 2015 by paul:b

Simon, thanks for the update.  Sounds promising.  Have you had the opportunity to qualify that no regression has been introduced so other sources, such as Spotify Connect and UPnP still function as before?

Posted on: 30 November 2015 by Pål Bråtelund [TIDAL]

First of all, thank you for your patience. Since a couple of weeks we have seen an escalation of drop-outs. Particularly in some regions such as South-East Asia and Australia, but also more sporadic reports from the UK. 

 

While you probably thought we were too quiet, we were busy looking at what was causing this both together with Naim and with our delivery partners.

 

At our delivery locations, content is is both downloaded from our storage and cached in chucks smaller than the entire music file. During the analysis of the streaming performance issues we found that the size of these chucks was too small, leading to higher latency and poorer cache hits rates. We have now released an update which removes chucking for smaller files and uses much larger chucks for large files. This will improve performance and should resolve the buffering issues experience in some regions.

 

Please do know that we take all feedback seriously and want to thank especially those users that with very constructive feedback and technical information have helped resolve the issues. 

 

Note also that as since this is related to caching it will take some time for all regions to fully resolve. 

 

Pål Bråtelund

TIDAL

Posted on: 30 November 2015 by kaydee6

Thanks Pal,

 

Great update and hopefully all's well now.

Posted on: 01 December 2015 by nigelb

Pal, many thanks for the update. I very much hope Tidal are successful and, assuming the dropouts can be overcome, look forward to using Tidal beyond the trial.

 

Dropouts have become less of an issue for me recently (in UK) so hopefully moving in the right direction.

Posted on: 01 December 2015 by Simon-in-Suffolk
Originally Posted by paul:b:

Simon, thanks for the update.  Sounds promising.  Have you had the opportunity to qualify that no regression has been introduced so other sources, such as Spotify Connect and UPnP still function as before?

Hi, I don't use Spotify so can't comment.. But UPnP still works wonderfully well like it always has done.

Simon

Posted on: 02 December 2015 by Trevor Wilson

hi all

 

just a quick update the Naim team are busy bees working through stuff, shouldnt be long now, a big thank you for being patient

 

Trevor

Posted on: 02 December 2015 by DC71

Thanks for the updates. Last few days Tidal has been much better here in Singapore, only a couple of dropouts.

If it's going to improve even further then I'll almost certainly ditch spotify, although I will miss the curated and shared/social playlists. 

Posted on: 03 December 2015 by Kiwi cat

Much better Tidal in New Zealand. No drop outs at all today!

Posted on: 03 December 2015 by PaulinBath

Simaudio released a firmware update for the MiND a couple of days ago. No idea what it covered as their customer communication is a bit thin on the ground - they dont even announce the updates - but since applying it Tidal seems a lot better. Only issue in the last couple of days has been that Tidal continues to play the occasional track as lower res MP4 rather than as FLAC even though the higher res FLAC version is available if the track is restarted.

Posted on: 04 December 2015 by nigelb

Oh dear. The dropout problem seems to have been eradicated only to be replaced by a different problem. Recently I have noticed that playing an album saved in My Music often tracks are skipped. The number of tracks skipped seems to be random. It has happened so frequently I thought I had selected the random play option but on checking this I have not.

Wierd! Anyone else had this problem?

Posted on: 04 December 2015 by PaulinBath

I have had this in the past few weeks (and has been quite bad at times to the extent of just 4 of 15 tracks being played) but not had it in the last couple of days (touching wood as typing!)

Posted on: 04 December 2015 by Robd123

Hey Trevor/Beta team et al

Please pass my thanks over to the testing teams. Out here in the wilds outside of Brisbane b/w is small, with little more than 3 meg peak the service this weekend is working perfectly. Naim native Tidal playback has continuously played for 6 hours straight. Last week was also fine but this is the first long play test.

This week has been a bumper week for me both home and away with network & app bug fixes, tweaks and enhancements......And what better way to kick back with a glass of wine and Tidal/Naim favourite tunes playing away. Thank you all.

Have a great weekend one and all.

Kind regards 

Rob D

Posted on: 06 December 2015 by Trevor Wilson

hi all



just to let you all know we are still checking and refining things, shouldn't be long now

trevor

Posted on: 07 December 2015 by Jack

Much better but still experiencing dropouts in UK, can manage about 4 tracks before problem appears.

Posted on: 07 December 2015 by kaydee6

I may have missed this but what are the new changes Naim is working on regarding Tidal integration. I thought the problem with music breaking up is at Tidal's end?

Posted on: 07 December 2015 by engjoo
kaydee6 posted:

I may have missed this but what are the new changes Naim is working on regarding Tidal integration. I thought the problem with music breaking up is at Tidal's end?

I believe Naim is tweaking the firmware to improve on connectivity robustness with Tidal. Nothing revolutionary in terms of interface. :-)