since update Node1 to 3.10.XX Tidal and Internetradio very slow

Answered

Comments

9 comments

  • Official comment
    Tony W.
    Product Support Manager

    Hi Fritz

    As mentioned in those other threads, we are having a hard time replicating the issue you are having and cannot confirm the details. So far in those cases we have found, it turned out to be a DNS setting in your ISP router. Please ensure you are on 3.10.3 by selecting Help, About. Then select Help, Send Support Request in your App so we can review the log file and take a closer look, and if necessary, send details to both our QA Team and TIDAL for review.

  • Harry

    Hi Tony, I encounter similar problems when streaming from my Synology NAS to my node 2i, and have been living with this problem since. Could you tell me what the DNS setting should be?

    -1
  • Tony W.
    Product Support Manager

    Hi Age Nero Usone

    If you are seeing an issue with a Synology, that's something different. Please see the official comment on this thread; https://support1.bluesound.com/hc/en-us/community/posts/360049542433

    -1
  • Harry

    Thanks. I've changed the SMB protocols and cleared cache. Its back to normal now.

    0
  • Steffan

    Hi Fritz

    I have the exact same problem! First Tony told me (would you guess) it was my router now he says it is Tidal authentication problems! Which is absolutely incorrect! I am using MDC 2 module in my NAD M32 and it has been working flawlessly for 2 years but after update 3.10.xx the problem started to occur. But by entering my password in the wifi section of the bluos app it fixes it for a while again - and yes I have tried resetting the mdc module several times AND uninstalling the app, but it doesn't work!

    Now it could be a couple of days sometimes a week in between this issue but it is always fixed by entering my wifi password again. But God have mercy if you by mistake type in a wrong password because then you would have to reset everything again in order for it to work 🤦🏼‍♂️ My router has 3 ssid's one for 5ghz, 2,5ghz and a combination and given the OLD technology on those modules you have to stick to 2,4. However it seems it is referring to the commons ssid sometimes. The ssids are all named the same (which has never been a problem) however I think I'll try and rename the 2.4ghz so that it doesn't confuse the two.
    Nevertheless this is bluesound who has messed it up whit their update and they just don't want to acknowledge it!

    1
  • Tony W.
    Product Support Manager

    HI Steffan

    Thank you for your feedback, the fact that it works, authenticates, logs in, and then stops working does illustrate the authentication problem I mentioned. Again please contact TIDAL regarding your account. If it was a problem with BluOS, you would not be able to authenticate.

    Thanks for understanding, but as mentioned, if you would like us to take a closer look, please select Help, Send Support Request in the App so we may review your log files.

    0
  • Steffan

    Hi Tony

    I can understand what you're saying, however what is the reason that the issue was introduced right after the update 3.10.00? Also I have tired to contact Tidal a week ago, and no response! Can you provide me with some contact information to someone from Tidal who will actually be willing to answer?
    In advance thank you.

    Furthermore I don't have this issue with the Tidal app alone, only through bluos.

    1
  • Steffan

    Still a problem after update 3.12.4 this is really starting to annoy me!
    WHO can I contact from Tidal in order to resolve this issue? Furthermore yesterday I tried to factory reset the MDC 2 bluos module and the reinstall everything again. Now after have been powered of completely from the wall as I do every night, when it was switched back on it had forgotten the setup and I had to reconnect the NAD M32 player, after doing so I switched off the power again, and guess what... it was gone again. So now I did another factory reset which has been working for the past 2 days now - though I still suffer from tidal being extremely slow until I have entered my wifi password AGAIN! This is also the case with tidal connect in the official app!

    1
  • Drew Podwal

    I'm having the same problem as you are.  Tidal works 100% fine on my other network devices, but takes 15-30 seconds to search for songs, play a song, and switch songs.  This all started for me after the update.  It happens so much I'm considering replacing my BlueNode 2I with a Raspberry PI unit. 

    I have 4 other stereos in my house each with a ChromeCast Audio that I'm looking to replace. I bought one Node 2i to see if I liked it, but  I'm so frustrated that I might just dump this on Craigslist and chalk it up as a loss.  It's really sad to see a customer support representative point their finger at the upstream point of integration especially when there are so many other posts I've seen on this forum reporting the same exact issue.  As a veteran product manager, I would take the responsibility to solve this problem for my customers even if it wasn't a defect within my own product architecture.  I think I have the patience to deal with this another week, before I pull the trigger on a Raspberry Pi with an ALLODigital Hat to see if it does what I want it to do with the performance that I need.  

    1

Please sign in to leave a comment.