Tidal Connect installed on Moode Audio

[GioF71]

I just documented the process of installing Tidal Connect on a MoodeAudio box with a Hifiberry HAT.
Everything should be available in the README.md.
I also discovered and fixed a bug when using card index in the process, so that has been fun.
Enjoy

[DKrampi]

Hi!
I need help :)
After i have run the following script
sudo apt update
sudo apt install docker.io docker-compose
sudo usermod -a -G docker $USER

and after this script

pi@moode:/ $ ./configure.sh -n "AUDIO" -f "Tidal" -m "Moode"
-bash: ./configure.sh: No such file or directory :(

from which directory should I run the configure.sh script? or what else would I need to do to configure the default sound device?
Thank you! Dí

[GioF71]

Hello, you need to clone the repository first.
Execute the following:

sudo apt install -y git
cd
git clone https://github.com/GioF71/tidal-connect.git
cd tidal-connect
./configure.sh -n "AUDIO" -f "Tidal" -m "Moode"

Let me know if this helps
Cheers

[DKrampi]

the script seems to run fine :)
Thank you! What comes next?
Unfortunately, I don't have a Tidal account yet but I'll get one soon ;)

[GioF71]

You need the tidal account in order to play to Tidal Connect. Why not trying with a free trial?

[GioF71]

BTW why "AUDIO" for the "-n" parameter? Is that the name of the sound card?
It might help if you post the contents of

cat /proc/asound/cards

[DKrampi]

I downloaded the Tidal app to my mobile phone, I'm on the same network/router/Wi-Fi with Moode, only This Device is shown, no other device :(

[DKrampi]

Is there anything to adjust on Moode?

[GioF71]

Can you post the output of:

docker-compose logs

from the tidal-connect directory

[GioF71]

There seems to be a space after AUDIO in the output of cat /proc/asound/cards, can you verify that?

[DKrampi]

there was no space

[GioF71]

You may also want to have a look to the upmpdcli docker image (https://github.com/GioF71/upmpdcli-docker), there is a new Tidal plugin which will allow you to create a media server dedicated to Tidal. See discussion here

[DKrampi]

I really don't know what happened. :) what was the reason for the improvement.
Apart from running this "docker pull giof71/upmpdcli" and restarting Moode, I did nothing.

[DKrampi]

"If you can, please consider starring the repo!" I do not understand, you mean promote your tidal-connect solution? please explain what you want. I am happy to promote it on the forums I know.
Sorry, I do not understand the language of today :) And English is not my strong point either.
I cannot express my gratitude enough.

[GioF71]

Hello, thank you for the kind words.
Starring means click the small star icon on the top-right corner of the repository page (in this case this, where it says "Star" with the current number of stars received. When you star it, the icon becomes yellow, yes of course it is for appreciation.

[GioF71]

Ok, so maybe you probably just did not restart the container after changing the configuration, at least I am guessing that this a possibility!
Maybe I need to clarify this in the documentation.

[DKrampi]

I think it would be useful to describe the whole process (the whole command line from start to finish) in the documentation, so that people who are less familiar with the process - like me - can successfully install tidal-connect :)

[GioF71]

I think it would be useful to describe the whole process (the whole command line from start to finish) in the documentation, so that people who are less familiar with the process - like me - can successfully install tidal-connect :)

First of all, thank you for starring the repo.
About the suggestion, you are right, I have just updated the documentation. Can you take a look and tell me if any of the steps require further documentation?

Cheers

[DKrampi]

Hi,
I see what looks like a missing 'cd tidal-connect' command in front of
./configure.sh -n "AUDIO" -f "Tidal" -m "Moode"
Configure Audio
,
,
Great, the operating system has just disabled the onboard audio and set the Hifiberry HAT as the default card.
So let's configure Tidal Connect:
.....

As soon as I have time, I'll try to see if the updated description works :)

[GioF71]

Ok, I have added "cd $HOME/tidal-connect" where needed (hopefully), let me know!

[DKrampi]

I re-did a tidal-connect installation following the updated instructions, successfully. :)

[GioF71]

Good! Feedbacks like yours are quite useful for improving the documentation. Thank you.

[longday11]

Hi - unfortunately, since a couple of days ago, this solution has stopped working for me.
9 out of 10 tracks just sit there at zero and won't play. Eventually one will. So bizarre.
Has anyone else experienced this? Such a shame!
To fix, I've tried to do a fresh reinstall of the latest moode (9.1.4) on my pi4, and have re-installed this solution - but same result. Tidal app on phone connects to Tidal Connect but tracks just will not play. I didn't really want to splash out for a wiim - I like to tinker.

[bauhorm]

Hello, I'm DIYer from Thailand . I've found out issue that My DAC only display 48KHz maximum bit rate only. and additional question if tidal connect can pass http stream to MPD player instead to go direct to alsa?

[GioF71]

Hello, unfortunately this solution is quite limited, see here.
There are alternatives though, some involve mpd, see here.

About mpd, what you ask is not possible AFAIK. Even if, maybe captured from the logs, a stream might be playable by mpd (but I never tried), the application would not be able to control mpd.

I have built a Tidal plugin for upmpdcli, maybe give it a try (sample configuration here).

Cheers

[kabexa22]

Hi, thanks for this. I really had to struggle, but I got it working. The key is to get the DAC name right. I also happen to have iqaudio, and there's a sample file. The one I had to configure to get it working is fine. If anyone finds it useful, the ASOUND_FILE_PREFIX parameter is helpful. Thanks!

[ponim]

Hello! lately I realized that my Moode with the lovely Tidal docker designed by you, stopped playing in Hi-Res, even 16bit/44100kBps. it can be easily seen in Windows Tidal application, where the rate window shows LOW instead of HIGH. I opened the ticket to Tidal support, but they still did not figured out the issue.

Can anything be done on the docker side to fix that?

[GioF71]

Hello @ponim, I just tried, an 16/44 works on my side. Can you post the container logs?
BTW it's not my solution, I have only built an alternative entrypoint script to make it easier to run the existing docker image with (almost) any alsa device.
Please, don't open issues on Tidal official boards about this solution. It is completely unsupported. Maybe investigate about its origin, and you will understand why Tidal will be a lot happier when they are able to phase it out :-)

[mike-golant]

hi
I have had the same issue since last week( or a week + a half :) )
Which kind of logs do you need?

[mike-golant]

attaching Docker-Compose logs
logs.txt
I have a DIY Hi-Fi DAC connected to RPI4 via I2S

[GioF71]

this line is scary:

�[2Ktidal-connect  | [2026-03-30 12:35:19.862] [tisoc] [warning] [PlaybackEngineTidal.cpp:142] url fetch error: 2, 401, {"status":401,"subStatus":11003,"userMessage":"The token has expired. (Expired on time)"}

Can you try to remove CARD_FORMAT=S24_LE from your .env file? usually we can use S16_LE or S32_LE. You might as well not need the parameter at all. But S24_LE is problematic AFAIK, some DACs don't work with that setting.
Restart using

docker-compose up -d --force-recreate

A re-create always happens if you change the value of any env variable. The --force-recreate tell docker to always create the container from scratch.

[mike-golant]

logs2.txt
logs3.txt

Hi again :)
new logs :
logs2.txt with CARD_FORMAT=S32_LE
logs3.txt with CARD_FORMAT=

same issue ...

[ponim]

and I got the same issue when setting is S16_LE

[GioF71]

post your logs as well if you can, thank you

[GioF71]

at least that "certificate" error is gone. any particular track you're trying to play?

[mike-golant]

Attaching screenshots

[ponim]

in the picture you can observe how we see the issue (also hear :) ).
ponim_log.txt

[ponim]

as I told, we see the issue as LOW indicator in the Tidal application's right bottom corner. When using the phone, instead of usual HIGH indicator, no indication at all (as on the picture Mike sent). Can we check the real stream rate in the command line?

[GioF71]

@ponim you seem to be using one of my sample config files, which specifies CARD_NAME=DAC along with FRIENDLY_NAME=Aune S6 USB DAC.

See in the log:

tidal-connect  | CARD_NAME=DAC

But also from your logs you seem to have some hifiberry dac:

tidal-connect  | Skipping audio device [sndrpihifiberry] at index [0]

maybe write the following line in your .env file:

CARD_NAME=sndrpihifiberry

Also a multi-word friendly name has represented an issue in the past, try using just a word (or just no spaces).

[ponim]

oh, right! interesting why I do see the different GUI indication from what you have.

But thanks in any case for your time - important to know that the sound quality I get is OK!!!

[GioF71]

oh, right! interesting why I do see the different GUI indication from what you have.

But thanks in any case for your time - important to know that the sound quality I get is OK!!!

I might be due to an application glitch... I used the android app, you are using the windows app from what I understand from the fact that it displays chromecast devices and not airplay. But the top-right button looks like some MacOS version.
Edit: it says MacBook Pro... I did not know that the mac version could play to chromecast devices.
Can you try some mobile version? Be sure to disconnect the app from the app you are currently using before trying to connect the mobile version.

[ponim]

attached is from my iPhone :)

[GioF71]

No indication of stream being lossless, but no indication of it being lossy as well. So we get the silence treatment :-)
It that's the trend, the android app will start to behave similarly sooner than later I think.
Anyway you can always check using the logs.

Remember, this thing might stop working at any time. Consider the alternatives. As you are running apple devices, the easiest is AirPlay. Maybe version 1 (using shairport sync with docker if you don't want to mess with moode's configuration files and potentially brick or even partially disrupt your device functionality) can still stream lossless 16bit/44.1 kHz.

Consider starring the repo if you like the work!

[ponim]

thanks again! for me Tidal connect sound quality is unbeatable! AirPlay is always the option, but sounds not hi-end at all!

[GioF71]

@mike-golant can you post your .env file? If you set

ENABLE_SOFTVOLUME=False

that should be yes or no. Try removing the line.
Also post the output of

cat /proc/asound/cards

and

aplay -L

[Iruizcast]

Hello!

First of all, thank you for your work. I have Moode Audio (10.1.2 2026-03-02) installed on a Raspberry Pi Zero 2W. After trying several configurations for the userconfig, this is the ASound configuration that worked for me to get sound over HDMI output:

file : hdmi-rpi-zero.asound.conf

pcm.tidalout {
    type iec958
    slave.pcm "hw:CARD=vc4hdmi,DEV=0"
    slave.format "IEC958_SUBFRAME_LE"
}

And this is my .env file

FRIENDLY_NAME=RaspberryPi
MODEL_NAME=Raspberry Pi Zero 2
ENABLE_SOFTVOLUME=no
ENABLE_GENERATED_TONE=no
FORCE_PLAYBACK_DEVICE=tidalout
ASOUND_FILE_PREFIX=hdmi-rpi-zero

Thank you!!

[adamnight0-pixel]

Okay, thanks for the explanation. What exactly should I look for? I've been using picoreplayer for years.

[GioF71]

have a look at https://www.music-assistant.io/. You can install it using docker. Or on Home Assistant if you have one running. Then you can connect your piCorePlayer to that server instead of lyrion. Only issue is should you want to run it in the same server where lyrion runs. You might need to change some ports for the slimproto protocol.

[GioF71]

Or of course you can run a upmpdcli media server with the tidal plugin enabled and use Moode as a renderer. Dislaimer: I am the author fo the plugin (not upmpdcli, only the plugin). See upmpdcli repo and example configuration.

[adamnight0-pixel]

Thanks for the reply. Unfortunately, I can't handle this, so I'm dropping the idea.
I'll keep listening via the picoreplayer plugin, or eventually just buy a WiiM and sell off all these "magic" add-on boards and power supplies. ;)

[GioF71]

Thanks for the reply. Unfortunately, I can't handle this, so I'm dropping the idea. I'll keep listening via the picoreplayer plugin, or eventually just buy a WiiM and sell off all these "magic" add-on boards and power supplies. ;)

alright, cool. If you change your mind, feel free to drop another comment here.