Tidal Connect is not playing a most of tracks

[mikegolant]

log : tidal-connect | [2024-11-18 16:57:55.664] [tisoc] [error] [logger.cpp:25] [http_stream_fetcher.cpp:162] Content-Range is missing from response! tidal-connect | [2024-11-18 16:58:01.678] [tisoc] [error] [logger.cpp:25] [operation_curl.cpp:258] curl_easy_perform failed: Timeout was reached - Operation too slow. Less than 1 bytes/sec transferred the last 5 seconds tidal-connect | [2024-11-18 16:58:01.678] [tisoc] [error] [logger.cpp:25] [http_stream_fetcher.cpp:162] Content-Range is missing from response! tidal-connect | [2024-11-18 16:58:05.038] [tisoc] [error] [logger.cpp:25] [operation_curl.cpp:258] curl_easy_perform failed: Transferred a partial file - transfer closed with 524288 bytes remaining to read tidal-connect | [2024-11-18 16:58:05.038] [tisoc] [error] [logger.cpp:25] [http_stream_fetcher.cpp:162] Content-Range is missing from response! tidal-connect | [2024-11-18 16:58:16.958] [tisoc] [error] [logger.cpp:25] [operation_curl.cpp:258] curl_easy_perform failed: Timeout was reached - Operation too slow. Less than 1 bytes/sec transferred the last 5 seconds tidal-connect | [2024-11-18 16:58:16.958] [tisoc] [error] [logger.cpp:25] [http_stream_fetcher.cpp:162] Content-Range is missing from response!

[ponim]

Also experience the same issue since yesterday.

[GioF71]

Hello, I am trying right now and it seems to work. Can you provide more details? maybe specific tracks/albums, or maybe something happens with newer albums only available through mpeg-dash?

[ponim]

A lot of albums are not playing. Just try several ones (examples https://tidal.com/album/385589764?u, https://tidal.com/album/376694350?u)

[GioF71]

Both playing here... can't seem to be able to reproduce the issue. Did you try re-creating the container?

[longday11]

Hey buddy. Try adding -v "1.1.1.1" to the end of your command line. So far so good for me. Here is mine : ./configure.sh -n "AUDIO" -f "SMSL DAC" -m "Moode Audio" -v "1.1.1.1" docker-compose up -d

[mikegolant]

Hi It's not help to me… Same issue...

[ponim]

Did anybody review the log Mike sent? Maybe some API changed from Tidal side?

[GioF71]

Not that I know of... I played one of the two albums entirely with no issue. There might be a DNS or CDN issue, which hopefully should be transitory. Which countries are you from?

[GioF71]

Does the mobile device play without issue on its own speaker?

[ponim]

Yes, on the phone playing all the albums and tracks

[GioF71]

Can you post your .env files?

[mikegolant]

Default: user@moode:~/tidal-connect $ cat .env FRIENDLY_NAME=Moode DAC MODEL_NAME=Raspberry Pi 4b CARD_INDEX=0 CARD_NAME=NOT_SET

I tried to set DNS to: 1.1.1.1

user@moode:~/tidal-connect $ cat .env FRIENDLY_NAME=Moode DAC MODEL_NAME=Raspberry Pi 4b DNS_SERVER_LIST=1.1.1.1 CARD_INDEX=0 CARD_NAME=NOT_SET

tried to set to Google DNSes (8.8.8.8 and 8.8.4.4 ), and my provider DNS - same issue

[GioF71]

Hello, I also tried with a Moode box, no issue there as well. Until this test I was using a Pi4 running OSMC. No difference, so strange. Since when you are experiencing the issue? In the meantime, as a temporary solution, if your mobile device is an Android, can you try to enable the "UPnP Client for MPD" renderer in moode, in UPnP-A/V mode, and use something like BubbleUPnP player? If your mobile device is an Apple, maybe you can just try to enable AirPlay on Moode and keep using the Tidal App.

Let me know if this helps

[GioF71]

Have a look here. Looks related. Someone suggested these dns: 185.228.168.9 and 185.228.169.9 Maybe use these by setting:

DNS_SERVER_LIST=185.228.168.9,185.228.169.9

in your .env file.

Or drop the dns settings from the compose file entirely and change those in your router or where relevant. I'm not sure it will work of course, but it might be worth a try.

[ponim]

Tried the suggested DNS settings - did not help

[ponim]

Content-Range is missing from response! - error in REST API...

[GioF71]

I tried myself and this broke tidal-connect for me. I had to revert to the usual dns. Some say here that there is an issue with the latest version of the app. I don't know why I am not experiencing the issue. Has anyone of you tried some alternative?

[mikegolant]

BDW, no issues with UPnP Client for MPD

[GioF71]

BDW, no issues with UPnP Client for MPD

Good... at least that works

[longday11]

Not that I know of... I played one of the two albums entirely with no issue. There might be a DNS or CDN issue, which hopefully should be transitory. Which countries are you from?

New Zealand for me.

[GioF71]

The fact that a similar issue, opened almost at the same time, has been solved for @longday11 with a change of DNS settings seems to indicate a temporary issue or something that might be as well be solved by changing DNS settings. However other than trying other DNS providers I am short of solutions. Also we have a relatively small number of people having the problem. And we have a few similar problems notified on Reddit. That said, I invite you guys to consider alternatives. This version of tidal connect is unmaintained and might completely stop working at any time. If (or when) Tidal decide to adopt mpeg-dash also for standard resolution (they did that for higher res content already), this application will stop working, without hope for a fix.

[ponim]

it works now - looks like tidal fixed on their side

[GioF71]

NOT_SET

Hello, I don't think that this might be the issue, but I would remove that line in the .env file that says

- CARD_NAME=NOT_SET

[GioF71]

it works now - looks like tidal fixed on their side

ah... good... let's see if it's the same for @mikegolant Thank you @ponim for the update

[mikegolant]

The issue is solved for me too Thank you!

[GioF71]

I am really happy of this. Please star the repository if you like the work. In any case, I reiterate the recommendation to look at the existing alternatives... this solution is living on borrowed time :-)