Tidal connect inconsistent from tidal app about tidal-connect HOT 3 CLOSED

Hello, thank you very much.
About your 'inconsistencies', can you try and reproduce the issue, and then post the container logs?
I can try and guess what could happen, and I just want to remind that Tidal Connect always tries to lock the audio output exclusively when a connection is made from the Tidal Apps (phone, computer, etc). Is there a chance that the audio output was used by some other application?
I just made a test and this is what happens in this situation: the Tidal Connect application cannot 'lock' the card and terminates with an error. The entrypoint.sh script from this repository will try to restart the application every 30 seconds (configurable), so when the output is 'lockable', the application restarts successfully and you can select the Tidal Connect device from your app.
Assuming you are using the card '0', you can check if the card is used with the following:

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

it should say 'closed' if the card is not used, otherwise you will see something like the following:

access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 96000 (96000/1)
period_size: 4800
buffer_size: 24000

which means (among the other details) that the card is used.
Of course this might not be your specific issue, maybe the logs should help, please post them using the following:

docker logs tidal-connect

of, if you want to keep watching the logs,

docker logs -f tidal-connect

from tidal-connect.

Hello @maximosstratis, did you solve your issue?

from tidal-connect.

Closing for inactivity... feel free to open another ticket is the issue persits.

from tidal-connect.