tidal-connect

A simple script used to configure a docker-compose stack for Tidal Connect.

Support

Please see the Goal
Please note that support goal is limited to cover running costs for subscriptions to music services.

Issue on the Raspberry Pi 5

If you use a Raspberry Pi 5, you might encounter an issue that shows with the following content in the container logs:

/app/ifi-tidal-release/bin/tidal_connect_application: error while loading shared libraries: libsystemd.so.0: ELF load command alignment not page-aligned

This issue can be solved by editing the file /boot/firmware/config.txt using the following command:

sudo nano /boot/firmware/config.txt

Add the following line in the all section:

kernel=kernel8.img

You will need to reboot, then restart the container.

News

MQA content is gone

At the end of July 2024, Tidal has removed all the MQA content. This particular implementation of Tidal Connect could play hi-res files only up to 24/48 and for MQA content: in the latter case, an unfolding to 24/88 or 24/96 was implemented by the application itself, while the further processing was delegated to a MQA capable DAC.
As far as I know, content above 16/44 available as HI_RES at 24/44 or 24/48 is currently inexistent on Tidal, so I guess we are now stuck to standard redbook resolution (16/44).
I don't consider this limitation a show-stopper. Some people might miss MQA, and that is totally fine for me. On the bright side, at least from now on, we don't have to worry about this controversial format to be detrimental to the audio quality, as some people said.
All the hires content from Tidal is now available only via MPEG-DASH. Some of the alternatives mentioned below support this streaming schema and will be able to play hi-res content up to 24/192.

Presets

I am trying to document all the configurations I have encountered with my own dacs and through your tickets. Look here and here.
Look at the samples and userconfig directories. They might contain a good file for your dac. It something for you isn't already there, open an issue, and we will create a sample file for your dac, which will also help other users.

A nice alternative

Also, consider the new mopidy-tidal alternative. Some things are not on par with the full-fledged web player or mobile app, but the developer is excellent, and I believe things are going to improve.
Visit this page for an example configuration using my docker image for mopidy. You will also find the references to the underlying projects.

Disclaimers

Contents

This repository does not contain the Tidal Connect software. There is only a docker-compose.yaml file, a configurator script, and a modified entrypoint which is just used for selecting the desired audio output more easily and reliably.

Credit

All the hard work has been done by the owner of the repository mentioned in the References section and in the other repositories from which his one has been forked. I am just trying to provide a way to run their container more easily in certain environments (where the index of your audio device is not the same on every restart).

No support from Tidal

This solution is not and will probably never be supported by Tidal. It might stop working at any time.

Alternatives

If you need to have a supported solution, look at Tidal Connect enabled products. A cheap one is the ubiquitous Wiim Mini/Pro/Pro+/Amp. Another option is represented by Google Chromecast/Chromecast Audio devices. Also, if you use Apple devices, you can already stream to AirPlay-enabled devices.
Even your current TV might already be used as an endpoint for Tidal via the embedded Chromecast functionality, or via AirPlay.

UPnP

Alternatively, if you are not scared of some DIY, you might want to create an upnp/dlna renderer, maybe with upmpdcli (you might use my docker image for upmpdcli) and mpd (you might use my docker image for mpd), and then use some Android app like BubbleUPnP or mConnect Lite (this one is also on iOS/iPadOS), connect those apps to Tidal and then stream to your upnp/dlna renderer.
Starting late November 2023, BubbleUPnP supports hires flac, see this post on Reddit. This is something that, from what I know, is not supported by this Tidal Connect application, and will probably never be.

Tidal Plugin for upmpdcli

Another solution might be my Tidal Plugin for Upmpdcli but again, there will be no support from Tidal. This solution works well with Tidal HiFi or with HiFi+ with MQA DACs.
This solution supports native HiRes flac playback (HI_RES_LOSSLESS so up to 24/192) to and mpd/upmpdcli player. If you configure it to play only up to HI_RES (so up to 24/48 and unfolding on a DAC), it will work on pretty much any UPnP renderer.
See here for a configuration for the HI_RES_LOSSLESS enabled media server.

Logitech Media Server

Another alternative, if you have a HiFi subscription and/or are ok with being limited to standard resolution or mqa-encoded tracks, is using Logitech Media Server and Squeezelite, for which you might use my docker image for squeezelite.
Even considering that after February 2024 the mysqueezebox online services will be shut down, there is a new, very promising, and I'd say already very usable plugin here by community heroes michaelherger and philippe44. This solution does not currently support Tidal HiRes while it supports MQA encoded streams: there will be no software-based unfolding, but a MQA enabled DAC should do that instead.

Mopidy-Tidal

There is a new plugin for Mopidy called Mopidy-Tidal, which enabled Mopidy to stream for Tidal with full support for HiRes streams.
I have prepared a docker container image for this solution here with a strong focus on this plugin especially.
A simple configuration can be found here.

Audirvana

A commercial solution, Audirvana Studio, allows you to stream from Tidal to UPnP renderers.
I maintain docker images for Audirvana Studio and here you can find a simple configuration for using mpd and upmpdcli as a player for Audirvana.

Roon

Roon is another commercial solution which can allow you to stream to Tidal.
You can build an endpoint using Roon Bridge. A dockerized solution is here.

References

The contents of this repository entirely rely on this repository from GitHub user TonyTrump. A big thank you to the author for the great work.
It will also use his docker image.

Why

I created this repository because it was very inconvenient for me to figure out the string to put for the PLAYBACK_DEVICE variable. I even failed for one of my DAC, I don't know honestly why, but as far as I understand, the ifi-pa-devs-get for some reason refuses to see the device. The most relevant issue I found about this issue is this, but it does not seems to have an easy solution.
Additionally, even if you can specify the correct string for your DAC, I found that the resulting configuration would be error-prone as the string reports both the device name and the device index. AFAIK the index can change across restarts, so outside of a known and controlled setup (which is probably represented by the I*i devices) this situation can an will lead to errors or unwanted configurations.
Keep in mind that the audio device index can also be changed because one time the (usb) device is powered on during boot, and another time it isn't.
This is my experience, unless I am missing something obvious. If so, I will be glad to be corrected.
The work in this repository consists in slightly altering the container startup phase (the entrypoint.sh file), in such a way that a custom /etc/asound.conf is created with (hopefully) the correct device index, regardless of the order of the audio devices, which can vary across restarts. The underlying application then always uses the default audio device.

Requirements

You will need a single-board computer (or anyway, a computer) with an armhf architecture (arm64 should work as well), running docker and docker-compose.
A Raspberry Pi 3/4 will work. If you plan to use a usb dac and hi-res audio, consider at least using a Pi 3b+ or, even better, a Pi 4b.
I am also running this on as Asus Tinkerboard. With this hardware, my suggestion is to not allow it to scale down the cpu frequency too much, or you might experience every kind of crackling noises along with what will remain of your music. In my experience, I am having good result if I set the minimum frequency at least about 600MHz, but, of course, YMMV.

Usage

Install Docker

Docker is a prerequisite. On debian and derived distributions (this includes Raspberry Pi OS, DietPi, Moode Audio, Volumio), we can install the necessary packages using the following commands:

sudo apt-get update
sudo apt-get install docker.io docker-compose
sudo usermod -a -G docker $USER
newgrp docker

The third line command adds the current user to the docker group. This is not mandatory; if you choose to skip this step, you might need to execute docker-compose commands by prepending sudo.
The last line will login to the group named docker. The previous command (usermod) is of course required in order for the newgrp instruction to be successful.

Clone the repository

You need to clone the repository. Make sure that git is installed using the following command on debian and derived distributions (again, this includes Raspberry Pi OS, DietPi, Moode Audio, Volumio):

sudo apt-get update
sudo apt-get install -y git

Move to the your home directory and clone the repository using the commands:

cd
git clone https://github.com/GioF71/tidal-connect.git

Update the repository

If you just downloaded the repository, you can skip this step.
If you previously cloned the repository, it might have been updated in the meantime. Move to the directory and pull the changes:

cd $HOME/tidal-connect
git config pull.rebase false
git pull

Configure

From the repository directory, just run the configure.sh bash script, specifying the following parameters:

I recommend to use the -n parameter instead of -i, because the index of the devices might change across restarts.
If you already used the configure.sh command and you are experiencing issues (because of the card has changed its index), you can run the command again. In the latest version, the card index is calculated during the container startup phase and hopefully there will not be any need to use configure.sh again unless you change the audio device you want to use.

Example

Configure for sound card named "DAC", using friendly name "Aune S6 USB DAC" and model name "Asus Tinkerboard":

cd $HOME/tidal-connect
bash configure.sh -n DAC -f "Aune S6 USB DAC" -m "Asus Tinkerboard"

If no error is reported, you will find a new (or updated) .env file.
If you find a spurious .asound.conf file there, it probably was generated by a previous version of the configure.sh script, and you can safely delete it.
So now you can run the docker-compose.yaml as usual:

cd $HOME/tidal-connect
docker-compose up -d

Environment Variables

The container can be entirely configured using the environment variables listed on the following table:

Please note that if both CARD_NAME and CARD_INDEX are specified, only CARD_NAME will be considered.
Also, if both CARD_NAME and CARD_INDEX are not specified, sysdefault (the system default audio device) will be used.

Volumes

Here is the list of volumes:

User-provided configurations

Custom asound.conf

If you put an asound.conf file in the userconfig directory of the repository, this file will be copied to /etc/asound.conf, so you can implement your custom configuration. You might need to set the variable FORCE_PLAYBACK_DEVICE according to the contents of the provided file, unless the device you want to play to is named custom.

Installation on Moode Audio or Volumio

It is possible to use this solution for easy installation of Tidal Connect on Moode Audio and Volumio.
It is required to have a ssh connection to the Moode/Volumio audio box. In order to enable ssh on Volumio, refer to this page.
Those two platforms do not ship docker out of the box (unsurprisingly), so docker installation is required. See Docker Installation earlier in this page.

Configure Audio

If you have just installed docker with the previous commands, it is probably a good idea to logoff your current ssh session, then log back in. Otherwise, just open a ssh connection to your box.
We need to configure the audio output you want to use for Tidal Connect.
If your device only has one output, or if that output is also configured as the default output, no configuration might be needed other than the Friendly and Model name.

Single audio device

On one of my boxes, I have a Hifiberry Dac+ Pro Hat, so when I use the command:

cat /proc/asound/cards

I get:

pi@moode-living:~/git/tidal-connect $ cat /proc/asound/cards
 0 [sndrpihifiberry]: HifiberryDacp - snd_rpi_hifiberry_dacplus
                      snd_rpi_hifiberry_dacplus

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:

cd $HOME/tidal-connect
./configure.sh -f "Living Aux1" -m "Raspberry Pi"

We are not specifying anything (not the card index and neither the name) because there is only one output available.
Replace the first and second strings to your liking. Once configured, start the service as usual:

cd $HOME/tidal-connect
docker-compose up -d

Multiple audio devices

On another one of my boxes, I have an usb dac connected, so when I use the command:

cat /proc/asound/cards

I get:

moode@moode:~ $ cat /proc/asound/cards
 0 [b1             ]: bcm2835_hdmi - bcm2835 HDMI 1
                      bcm2835 HDMI 1
 1 [Headphones     ]: bcm2835_headpho - bcm2835 Headphones
                      bcm2835 Headphones
 2 [X20            ]: USB-Audio - XMOS USB Audio 2.0
                      XMOS XMOS USB Audio 2.0 at usb-0000:01:00.0-1.2, high speed

So in this setup, the operating system has not disabled the onboard audio. Even if you have configured Moode so that is will use the USB DAC, this might not be enough for Tidal Connect to automatically select that card.
The safest way (at least IMO) is to use the string that identifies the dac as card name: So let's configure Tidal Connect:

cd $HOME/tidal-connect
./configure.sh -n "X20" -f "Desktop" -m "Raspberry Pi"

Replace the second and third strings to your liking. Once configured, start the service as usual:

cd $HOME/tidal-connect
docker-compose up -d

Caveat

Audio device locking

Tidal Connect will access exclusively your audio device if you select it in your desktop/mobile Tidal App.
If you want to play to the selected audio device from other sources, you will need to disconnect from the Tidal app you are using.
Similarly, you won't be able to play to a device if this device is already playing something from another source.
In order to check if a device is playing, follow the instructions in the next paragraphs.

Check Audio device is playing, by index

Say you have selected your card by its index (not recommended), and that the index is 1, you can execute the following command:

watch cat /proc/asound/card1/pcm0p/sub0/hw_params

If this does not say "closed", it means that the audio device is being currently used.

Check Audio device is playing, by name

Say you have selected your card by its name, and that the name is D10, you can execute the following command:

watch cat /proc/asound/D10/pcm0p/sub0/hw_params

If this does not say "closed", it means that the audio device is being currently used.

Software volume

This solution will try to configure a software volume for your Tidal Connect device, so that you should be able to control the software volume from the Tidal App on any platform, without touching the hardware volume, which is something you might find useful if you have other players running on the same audio device, e.g. mpd, librespot, squeezelite, etc.
However, software volume will be enabled only if your audio device does not already have a control named Master. You can verify if your device already has such control using the following command, for the audio device at index 0:

amixer -c 0 | grep \'Master\'

The desired output is no output, as this would mean that there is no Master control already.
If, instead, you get a line like this one, you are (almost) out of luck:

Simple mixer control 'Master',0

Even under this condition, the solution will create the SoftVolume control naming it SoftVolume. This will allow the Tidal Apps (at least the current Android version) to control the hardware volume using its slider. This means that changing the volume from the Tidal App will affect all the other players running on the same audio card.
If you are in this situation (so if you already have a Master control defined in your audio device) and you don't want to use hardware volume, consider disabling software volume by setting ENABLE_SOFTVOLUME to no in your .env file, or acting on the correspondent switch of the configure.sh script.
See this issue for some context information.
Special "Thank You" to zamiere for providing useful information.

Hardware changes

Remember that, should you change something to your Moode/Volumio setup, maybe replacing the audio-hat with an USB DAC, you will most likely need to reconfigure Tidal Connect accordingly.

Volumio integration

Please be aware that this solution will not be completely equivalent to the built-in premium feature of Volumio. That solution (probably) allows the attached (touch) display to show the currently playing song, while this solution for sure does not allow that or any other related features.

Mandatory IPV6 support

Tidal connect won't work if your system does not support ipv6. See this issue.
Afaik, there is no solution or workaround available other than, somehow, enabling ipv6.

DietPi

On DietPi (which I am running on my Asus Tinkerboard), you might need to enable avahi-daemon, if this is not enabled yet.
You might find the following on the logs:

[tisoc] [error] [avahiImpl.cpp:358] avahi_client_new() FAILED: Daemon not running

This can be fixed by installing the avahi-daemon. It is not installed by default on DietPi, so we can installing it with this command:

sudo apt-get install avahi-daemon

An already started tidal-connect container should start working immediately, at least that is what happened with my setup.

Change History