Tidal Connect

Matt

October 21, 2020 14:41

None

Tidal Connect is finally arrived. It works same way as Spotify Connect.

https://darko.audio/2020/10/tidal-connect-who-what-why/

When we can have Tidal Connect in HiFiberryOS? :)

Date Votes

159 comments

0

Cereyanlı Musiki December 02, 2021 15:31

Now I am reading through some other information sources made me think that if HifiBerry DSP add on board factor ?

Tony Tromp I have an also HifiBerry DSP addon top on HiFiBerry Digi2 Pro attached Rpi . Do you think this might be factor.

I will remove and test it and report back

Edited by Cereyanlı Musiki December 02, 2021 15:35

Comment actions Permalink
0

HiFiBerry team December 02, 2021 15:32

With the DSP add-on you definitely won't get any MQA.

Comment actions Permalink
0

Cereyanlı Musiki December 02, 2021 15:48

HiFiBerry team

then , there you go. We found the issue :).

I will still test and confirm

PS: Is there any way I can disable DSP Add on the UI ?

Edited by Cereyanlı Musiki December 02, 2021 15:50

Comment actions Permalink
0

Jon Rotaetxe December 12, 2021 10:26

Hi, friends, Tony

I have the Tidal connect running over Hifiberry OS and happy as apig in the mud with it, but I am suffering the lack of volume control from the tidal app....
My entrypoint .sh is this one

#!/bin/bash

echo "Starting Speaker Application in Background (TMUX)"
/usr/bin/tmux new-session -d -s speaker_controller_application '/app/ifi-tidal-release/bin/speaker_controller_application'

echo "Starting TIDAL Connect.."
/app/ifi-tidal-release/bin/tidal_connect_application \
--tc-certificate-path "/app/ifi-tidal-release/id_certificate/IfiAudio_ZenStream.dat" \
-f "HiFiBerry" \
--playback-device "snd_rpi_hifiberry_dacplus: HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0 (hw:0,0)" \
--codec-mpegh true \
--codec-mqa false \
--model-name "HiFiBerry" \
--disable-app-security false \
--disable-web-security false \
--enable-mqa-passthrough false \
--log-level 3 \
--enable-websocket-log "0" \
#echo "Starting Speaker Control Application.."
#/app/ifi-tidal-release/bin/speaker_controller_application

echo "TIDAL Connect Container Stopped.."

I believe the line in bold is the problem with volume control. Seems HifiberryOS does not have TMUX command, so no volume control...

Is there any way to "upgrade" HifiberryOS to have "TMUX"?

Thanks in advance

Comment actions Permalink
0

HiFiBerry team December 12, 2021 11:42

This has nothing to do with tmux on HiFiBerryOS as this command runs in the docker container that has its own tools.

Comment actions Permalink
1

Tony Tromp December 12, 2021 15:04

tmux is started from within the docker container.

The idea is that the intercepted volume controls (e.g. volume up/down) are forwarded as input commands to the TMUX session. It works for myself, but apperantly not for everyone for some reason.
I have not figured out why as i am unable to replicate the issue.

Comment actions Permalink
0

Jon Rotaetxe December 13, 2021 06:57

Oh, I see...

Thank you again

Comment actions Permalink
0

Lflarochemorin January 03, 2022 14:51

Hi everyone,

I've just gone through this thread to help me decide whether or not i'm up to the challenge. Zero experience in DIY electronics or coding ! But now i know this Rpi solution exists I'll never feel comfortable buying a 600 $ streamer...

So just a small question before I jump in : any reason this set up would not work from a Mac computer ?

Special thanks to Tony for your engagement to this community !

LF

Comment actions Permalink
0

Tony Tromp January 03, 2022 15:32

Hi Lflarochemorin,

Depends what it is exactly you want to do from your Mac? If you want to primarily use your Mac as Streamer instead of a Raspberry, best (subjective to my opinion) would be by installing Audirvana. It should integrate nicely with Tidal.

If you want something more 'standalone' and running 24x7, than the Rpi is a great alternative. Putting a Rpi streamer together is really simple and straight forward. You can go multiple routes, either buy a DAC board from Hifiberry or Allo. Or you could even connect a external USB DAC (even a DragonFly could be used). Most distributions (Moodle, HifiberryOS, Volumio) supports Airplay/Bluetooth/Spotify Direct/Tidal Connect. So you can stream from almost everything. In my opinion the Raspberry route is really great as you can choose how you want to upgrade without breaking the bank.

Edited by Tony Tromp January 03, 2022 15:34

Comment actions Permalink
0

Lflarochemorin January 04, 2022 13:48

Hi Tony Tromp, thanks again for a quick response. I'm actually trying to move away from using my Mac as main source (streamer). That's why I'm looking at Rpi solutions. My question was more specificaly about the process of setting up the Pi from a Mac. I hear using Terminal (Mac's app) I could configure the SD card. Is this viable with the Hifiberry OS install and your Docker solution ?

The best way forward I've found right now is : Rpi > AudioquestJitterBug > USB DAC > amp... etc.

I want to use the Jitter bug instead of a Hat like Digi Pro or actual DAC from HifiBerry because I already have it and a simple JDS Labs DAC. Any counter indications here ?

Thanks again !

LF

Comment actions Permalink
0

Lflarochemorin January 04, 2022 14:11

Actually I might have found the answer to my question : https://www.youtube.com/watch?v=j2zJHGbyWxU&ab_channel=DarkoAudio [5:45]

In this video (from April 30th 2021), Dark Audio guy mentions problems getting sound out from his Rpi's USB ports. Has this issue been resolved since, HiFiBerry team ?

Comment actions Permalink
0

HiFiBerry team January 04, 2022 14:45

This is not a "problem" at all. USB DACs are not supported by HiFiBerryOS and won't be in the future. You need to use a HiFiBerry sound card with HiFiBerryOS.

Comment actions Permalink

Adam Niezgodka January 04, 2022 19:39

Dear HiFIBerry team,

what could be the reason of such a log?

"Starting TIDAL Connect Service.

Job for tidal.service failed because the control process exited with error code.

See "systemctl status tidal.service" and "journalctl -xe" for details.

Finished starting TIDAL Connect Service.

Tue Jan 4 19:44:47 CET 2022 hifiberry install.sh[1761]: [INFO]: Restarting Beocreate 2 Service.

Stopping Beocreate 2 Server

Starting Beocreate 2 Server

Finished restarting Beocreate 2 Server."

Thanks in advance.

TRANSLATE with x

English

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian

TRANSLATE with

COPY THE URL BELOW

Back

EMBED THE SNIPPET BELOW IN YOUR SITE

Enable collaborative features and customize widget: Bing Webmaster Portal

Back

0

HiFiBerry team January 05, 2022 07:30

We can't say anything about this as this is not something we provide. Some other user from this topic might be able to help.

Comment actions Permalink
0

Tony Tromp January 05, 2022 08:36

Hi Adam,

its in the message, how to investigate. please run command: journalctl -xe

and check for relevant errors and share results here.

Comment actions Permalink
0

Tony Tromp January 05, 2022 08:52

Hi Lflarochemorin,

Creating a Rpi streamer and installing the software/OS is really easy. a bit off topic in this forum, but there are plenty of good resources to find online. HifiberryOS works with a Hifiberry DAC. But vice versa you can use other distros (Rpi OS, Moodle, Volumio) also with the Hifiberry DAC. As mentioned, the HifiberryOS does not support USB DAC.

Comment actions Permalink
0

Adam Niezgodka January 05, 2022 13:36

Dear Tony,

I reinstalled the whole system including your plugin and now playback is working but unfortunately there is no volume control and it does not show the track being played.

I see that I have the same as Jon.

No idea why?

Comment actions Permalink
0

Tony Tromp January 06, 2022 06:14

Hi Adam Niezgodka,

That is correct. As of today you wont see any updates on the webinterface (song information) etc. Work on this has been started but has been stale. Volume control via you mobile phone should work (if using Tidal Connect), from webinterface there i no integration.

Comment actions Permalink

Adam Niezgodka January 06, 2022 10:39

Tony,

thanks for the answer, however the volume control on the mobile device doesn't work for me. I hope you will be able to make it all work.

TRANSLATE with x

English

Arabic	Hebrew	Polish
Bulgarian	Hindi	Portuguese
Catalan	Hmong Daw	Romanian
Chinese Simplified	Hungarian	Russian
Chinese Traditional	Indonesian	Slovak
Czech	Italian	Slovenian
Danish	Japanese	Spanish
Dutch	Klingon	Swedish
English	Korean	Thai
Estonian	Latvian	Turkish
Finnish	Lithuanian	Ukrainian
French	Malay	Urdu
German	Maltese	Vietnamese
Greek	Norwegian	Welsh
Haitian Creole	Persian

TRANSLATE with

COPY THE URL BELOW

Back

EMBED THE SNIPPET BELOW IN YOUR SITE

Enable collaborative features and customize widget: Bing Webmaster Portal

Back

Edited by Adam Niezgodka January 06, 2022 10:41

0

Luis January 06, 2022 12:17

Hi Tony,

Great, in this new version it is no longer necessary to edit the "entrypoint.sh" for Tidal app to show the name we chose for our device.
My devices are:
- Raspberry Pi 4 2GB
- HiFiBerry DAC 2 PRO (I have other Chinese hat DAC cards that work (and sounds) great with HiFiBerry OS)
The volume control by Tidal app works perfectly via Jack 3.5 output; unfortunately it doesn't work via RCA outputs. But volume control via RCA works by the UI.
Thank you very much for your excellent work.

Comment actions Permalink
0

Luis January 06, 2022 12:22

... and Happy New Year !!!

Comment actions Permalink

Firefly January 14, 2022 11:45

Hi everyone !

I know this is mainly a HifiBerry OS thread but my issue is still about this Tidal Connect docker container and HifiBerry hardware.

I use a Rpi 4B 4GB a Digi+ Pro with the 2nd recommended OS (LibreELEC 10.0.0). As many here I would love to use it with Tidal Connect.

I launch the docker container with this docker-compose:

version: '2.2'
services:
tidal-connect:
image: edgecrush3r/tidal-connect:latest
tty: true
network_mode: host
devices:
- /dev/snd
volumes:
- /var/run/avahi-daemon/socket:/var/run/avahi-daemon/socket
- /var/run/dbus:/var/run/dbus
restart: always
dns:
- 8.8.8.8

And with this command override:

/app/ifi-tidal-release/bin/tidal_connect_application \
--tc-certificate-path "/app/ifi-tidal-release/id_certificate/IfiAudio_ZenStream.dat" \
-f "Hifiberry Tidal Connect" \
--codec-mpegh true \
--codec-mqa false \
--model-name "Hifiberry Tidal Connect" \
--disable-app-security false \
--disable-web-security false \
--enable-mqa-passthrough false \
--log-level 0 \
--playback-device "snd_rpi_hifiberry_digi: HiFiBerry Digi+ Pro HiFi wm8804-spdif-0 (hw:0,0)"
--enable-websocket-log "0" \

Here are my logs:

Starting Tidal Connect..
,STARTING TidalConnect services, version: 1.1.3
,Expression 'GetExactSampleRate( hwParams, &defaultSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 895
,Expression 'GetExactSampleRate( hwParams, &defaultSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 895
,ALSA lib pcm_asym.c:106:(_snd_pcm_asym_open) capture slave is not defined
,ALSA lib pcm_direct.c:977:(snd1_pcm_direct_initialize_slave) requested or auto-format is not available
,ALSA lib pcm_dmix.c:1064:(snd_pcm_dmix_open) unable to initialize slave
,Expression 'GetExactSampleRate( hwParams, &defaultSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 895
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround40
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround41
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround50
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround51
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
,ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
,ALSA lib pcm_asym.c:106:(_snd_pcm_asym_open) capture slave is not defined
,ALSA lib pcm_direct.c:977:(snd1_pcm_direct_initialize_slave) requested or auto-format is not available
,ALSA lib pcm_dmix.c:1064:(snd_pcm_dmix_open) unable to initialize slave
,ALSA lib pcm_direct.c:977:(snd1_pcm_direct_initialize_slave) requested or auto-format is not available
,ALSA lib pcm_dmix.c:1064:(snd_pcm_dmix_open) unable to initialize slave
,Cannot connect to server socket err = No such file or directory
,Cannot connect to server request channel
,jack server is not running or cannot be started
,JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
,JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
,STARTED TidalConnect services.
,[2022-01-14 11:28:25.094] [tisoc] [warning] [PlaybackControllerImpl.cpp:472] Illegal state:1
,[2022-01-14 11:28:30.270] [tisoc] [warning] [logger.cpp:22] [audio_worker.cpp:321] Attempting to initialize a decoder without initial data!

I can see the service in Tidal Connect but of course, no sound.
Last 2 lines appear when I browse Tidal Connect devices and then (5 sec later) when I connect to this device.

Exact same errors with ifi-pa-devs-get but ends with:

device#0=iec958 
device#1=spdif 
Number of devices = 2

On the other hand, my Digi+ is recognized by ALSA:

# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HiFiBerry Digi+ Pro HiFi wm8804-spdif-0 [HiFiBerry Digi+ Pro HiFi wm8804-spdif-0]
Subdevices: 0/1
Subdevice #0: subdevice #0

I guess the container cannot view/access my Digi+ sound card ? Any bind I missed ?
Is it because it might be locked by Kodi ?
Or that LibreELEC deals differently with soundcards ? (iirc Kodi only sees Digi+ directly through ALSA, not PulseAudio)

Huge thanks for your work for this community, I tipped you on GitHub !

Edited by Firefly January 14, 2022 19:53

0
Tony Tromp January 18, 2022 09:18
Hi Firefly,

Interesting issue as for LibreElec we probarbly need different sound devices.

like you said, ALSA recoginizes the soundcard in the host environment, so we will need to expose it somehow.
I found this forum which could definitely help: https://forum.libreelec.tv/thread/24308-docker-container-audio-output-to-libreelec/

You could add the /dev/snd to the volume mounts and see if that resolves your problem.

Add the following to your docker-compose.yaml
```
    volumes:
      ....<as-is>
    devices:
      - /dev/snd:/dev/snd

      
```
Kind regards,
Tony
Comment actions Permalink
0

raaven January 18, 2022 21:08

hello tony,

thx for your great work to integrate tidal. seems to work quite well, but not in my applicaton.

i were using your guideline on github, but i get during installing this

"failed to register layer: Error processing tar file(exit status 1): write /usr/lib/arm-linux-gnueabihf/vdpau/libvdpau_nouveau.so.1.0.0: no space left on device
Tue Jan 18 21:59:21 CET 2022 subito-tl-mit-sub install.sh[1959]: [INFO]: Finished pulling docker image edgecrush3r/tidal-connect:latest.
Tue Jan 18 21:59:21 CET 2022 subito-tl-mit-sub install.sh[1959]: [ERROR]: Docker image edgecrush3r/tidal-connect:latest does not exist on the local machine even after we tried pulling it.
Tue Jan 18 21:59:21 CET 2022 sub"

error.

do you have any hints to solve this problem.

carsten, asking from germany

tia

Comment actions Permalink
0

HiFiBerry team January 18, 2022 21:10

"No space left on device" shows that the file system is probably full. What SD card size do you use? To run containers (that require quite a bit of storage) I would recommend at least 16GB, better 32GB (not all of this space is available for the system partition).

Comment actions Permalink
0

raaven January 18, 2022 21:50

hello daniel, thx.

it is an 8 gb sd card. so this might be the solution.

i'll try tomorrow and will report.

sweet dreams, carsten

Comment actions Permalink
0

raaven January 20, 2022 21:36

hello daniel,

with a new 32 gb sd-card installation was working quite easy. thx tony. and to you too.

now tidal connect with my beocreate - raspi4 application appears in the android tidal-app.

and i can choose this as destination for the stream, but no sound occurs.....

does anyone have some hints to solve this?

might i have to change something in the entrypoint.sh?

tia

carsten

Comment actions Permalink
0
Tony Tromp January 23, 2022 13:33
Hi Raaven,

What DAC are you using and which outputs are you using for the connection?

Is it just TIDAL not working or do you also have issues on Spotify/UPnP etc?

If its TIDAL that you dont get sound, check the logs:
```
cd Docker
docker-compose logs
```
If you dont get any audio, you will need to add to following to the tidal_application arguments
```
--playback-device "<NAME_OF_DEVICE>"
```
Where NAME_OF_DEVICE you can find by running
```
docker run -ti \
--device /dev/snd \
-v /var/run/dbus:/var/run/dbus \
-v /var/run/avahi-daemon/socket:/var/run/avahi-daemon/socket \
--entrypoint /app/ifi-tidal-release/bin/ifi-pa-devs-get edgecrush3r/tidal-connect
```
Comment actions Permalink
0

matvarg January 29, 2022 17:40

Tony Tromp:

First of all, I am very thankful for having TIDAL on my Raspberry Pi now. You made it so easy to get there.

However, I am still curious what would one have to do with your docker image such that we can have volume control working for all users.

On another forum I have seen a solution without docker that allows to configure volume control. Is there a way to integrate this solution into your docker image such that everyone can modify some parameters and eventually get it to work for their devices (similar to how we entered parameter --playback-device "<MY_DAC>")?

I find it hard to accept that the conclusion about volume control on this dockerized solution is: "We'll bad luck if it doesn't work for you :D"

Edited by matvarg January 29, 2022 17:41

Comment actions Permalink
0

raaven January 30, 2022 23:06

hello tony,

first of all: THX.

i'm using a beocreate with raspi4 and dac+dsp with raspi3.

in both aplication - both also from scretch - it's not working.

will try your hints.

where do i find that file that needs the right input for

--playback-device ......

carsten

Comment actions Permalink

Please sign in to leave a comment.