Icon Tidal-Connect doesn't respond to the launch

[tomazi78]

Hi,
I've been using TIDAL-Connect for a very long time. I didn't report the problem because I thought it would somehow resolve itself over time.
Problem description:
I'm running it on a Pi4B, using MOoDEAudio 9. Every time I start the Pi, TidalConnect starts up. I see the Tidal-Connect icon in the Tidal app on the iPad, but the icon doesn't respond to the launch—nothing happens, the music continues to play on the iPad as if nothing had happened. I have to use the commands:

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

Only then does TidalConnect work, and I can switch the source on the iPad.
What could be the problem that TidalConnect doesn't work immediately, even though it's visible on the iPad's network?

[GioF71]

Hello, I have not been using this solution for quite some time now, so I tried on an Asus Tinkerboard running DietPi bookwork, and on a Pi3 running Moode 9.4.0.
Both worked for me.
Are you sure that the device is not used by another application?
Maybe post the application log, using

docker-compose logs -f

Also, assuming that your device is named "DAC" (please correct!), try to execute the following:

cat /proc/asound/DAC/pcm0p/sub0/hw_params

if this does not say "closed", it means that the device is in use.

[tomazi78]

[GioF71]

ok the docker compose command must be done from the repository directory, so maybe try:

cd ~/tidal-connect
docker-compose logs -f

the other command fails because your dac is not named "DAC" in alsa. Try this so we know the name of your dac:

cat /proc/asound/cards

it should be the same name set in your .env file inside the ~/tidal-connect directory.
So just to be sure, maybe also execute this:

cat ~/tidal-connect/.env

[GioF71]

Hello, is the issue solved?