Hello, I’m a new subscriber to Volumio, I have been running Volumio on a Pi 3 b+ for about a week now and Tidal Connect has not worked well for me at all. The Tidal Connect feature constantly crashes and I need to do a full reboot of the Pi to get it working again. I’m running Volumio ‘2.907’ and I’m hardwired not using wifi.
Here is a link to the log that I submitted.
http://logs.volumio.org/volumio/gMIrbxS.html
Not sure if this matters but I’m connected via USB from the Pi to a Topping D70s DAC.
Having the exact same issue. Was far more stable before updating to 2.907
also, here is what was reported in the log as soon as tidal connect crashed:
Jul 26 23:30:54 volumiods volumio[1003]: info: CoreStateMachine::pushState
Jul 26 23:30:54 volumiods volumio[1003]: info: CoreCommandRouter::volumioPushState
Jul 26 23:30:54 volumiods volumio[1003]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
Jul 26 23:30:54 volumiods vtcs[1557]: Floating point exception
Jul 26 23:30:54 volumiods systemd[1]: vtcs.service: main process exited, code=exited, status=136/n/a
Jul 26 23:30:54 volumiods systemd[1]: Unit vtcs.service entered failed state.
Hi @dannydd,
We have launched a new alsa backend for tidal connect, that could cause the issue. Can you please tell me what track you were playing and what stream quality? Thanks in advance!
Hard to say, it seems to happen when switching songs. I too have a Topping D70s and am connected USB (MQA enabled). I am unable to reproduce it now as I reverted back to 2.8 
Hard to say, it seems to happen when switching songs. I too have a Topping D70s and am connected USB (MQA enabled). I am unable to reproduce it now as I reverted back to 2.8
Yes, it would happen when switching songs in version 2.9 and up. Upon reverting to 2.882, I as well, am not having any issues. Although, I’m still able to crash it if I switch songs very rapidly.
I’m having the same issue as well. Started today for me… some of my playlists wont play at all while others will play a song or two and fail. Only happens with Tidal Connect…
Hardware:
Volumio Version: 2.907
Hardware: Raspberry Pi 4 8GB
DAC: Schiit Asgard 3 w/ Multibit
Song that I tried to play when it crashed:
{“status”:“play”,“title”:“7 Years”,“artist”:“Lukas Graham”,“album”:“Lukas Graham”,“albumart”:"/albumart?sectionimage=music_service/tidalconnect/images/tidal-logo.png",“uri”:"",“trackType”:“tidal”,“seek”:7501,“duration”:237,“samplerate”:“44.1 KHz”,“bitdepth”:“24 bit”,“channels”:2,“random”:false,“repeat”:false,“repeatSingle”:false,“consume”:false,“volume”:100,“mute”:false,“disableVolumeControl”:true,“stream”:false,“updatedb”:false,“volatile”:true,“service”:“tidalconnect”}
What I saw in the logs when no sound came out and Tidal Connect went offline:
Jul 28 02:07:17 asgard vtcs[21019]: Floating point exception
Jul 28 02:07:17 asgard systemd[1]: vtcs.service: main process exited, code=exited, status=136/n/a
Jul 28 02:07:17 asgard systemd[1]: Unit vtcs.service entered failed state
root@asgard:/home/volumio# volumio endpointstest
TESTING REMOTE ENDPOINTS
https://google.com, 393 ms: OK
https://www.googleapis.com, 208 ms: OK
https://securetoken.googleapis.com, 241 ms: OK
https://myvolumio.firebaseio.com, 339 ms: OK
https://functions.volumio.cloud, 463 ms: OK
https://oauth-performer.dfs.volumio.org, 590 ms: OK
https://browsing-performer.dfs.volumio.org, 559 ms: OK
http://cddb.volumio.org, 989 ms: OK
https://functions.volumio.cloud, 486 ms: OK
http://pushupdates.volumio.org, 390 ms: OK
http://plugins.volumio.org, 717 ms: OK
https://database.volumio.cloud, 487 ms: OK
https://radio-directory.firebaseapp.com, 258 ms: OKREMOTE ENDPOINTS TEST OK, all Endpoints are reachable
I agree with @buggyglint, fast switching of songs broke it on 2.882 but 2.907 is driving me bonkers, doesn’t seem to want to play anything I like LOL.
Please let me know if you need anything else
nudge
bump
Is anything being done about this?
I tried downgrading to an older image that I had kicking around (2.882) and I was still having issues with Tidal Connect showing up. Spotify Connect works without any issues.
Is there another issue at play here?
Are there any updates? Here are fresh logs with the beta version of Volumio installed.
logs.volumio.org/volumiobuster/gX8XJKr.html
3.080 is what I’m running on the Pi4 8GB w/ Schiit Asgard w/ Multibit DAC connected via USB
3.080 has a defect so should not be used next week there will be a new release.
3.080 does not work properly. A bug in audio output pipe results on no sound in most of cases or strange behaviour. i wanted to switch to 3.080 and asked if a other fault was still present in it and heard this.
Thanks for the details. I’ve been having issues with Tidal Connect for awhile now even on 2.907 so that’s why I tried 3.080. Guess I’ll just keep waiting lol
we are trying to get all back in order but the switch to 3.xx is a lot of work that’s why we are still in beta. filtering all the quircks and bugs out of it.
I understand that 
Just sad that its appears broken in 2.907 as well which is supposed to be stable. Using Tidal via Volumio works no issue, but I don’t have access to all the same playlists like I do in the app… so I’m missing a working Tidal Connect. Plus the playlists in general on Volumio for Tidal is just buggy.
Anyway I can help… always happy to do so.
for now we have to wait for the new release i hope in time that more are back from vacation,
still a few weeks to go.
Downgraded to 2.882, at least I can play Tidal using Tidal connect for hours without an issue.
(My tracks / playlists are still messed, but Tidal Connect is more stable) I’ll wait until everyone comes back from vacay and help then I downgraded my subscription until I can get it stable on one device.
Email to techsupport@volumio.org for help requests maybe they can shine a light on the problems. @DED
Thanks @dvo
Support didn’t do much, and I passed them these threads as well. @volumio maybe you’ll take a look… I’m happy to debug
I ran wireshark and I could see Spotify Connect advertising and replying to all mdns requests. However the tidal packet doesn’t seem right, and needs a kick in the butt to advertise itself. (Start and stop the service while in the Tidal app looking for devices)
6397 57.600263 192.168.1.92 224.0.0.251 MDNS 289 Standard query response 0x0000 PTR asgard._spotify-connect._tcp.local SRV 0 0 45739 asgard.local TXT A 192.168.1.92
1728 64.353122 192.168.1.92 224.0.0.251 MDNS 289 Standard query response 0x0000 PTR asgard._spotify-connect._tcp.local SRV 0 0 45739 asgard.local TXT A 192.168.1.92
1424 59.634103 192.168.1.92 224.0.0.251 MDNS 292 Standard query response 0x0000 TXT, cache flush PTR Volumio-c27afdfa9e827e4d2973ad2e5f2dfd96._tidalconnect._tcp.local SRV, cache flush 0 0 2019 asgard.local A, cache flush 192.168.1.92 PTR _tidalconnect._tcp.local
1387 58.403626 192.168.1.92 224.0.0.251 MDNS 231 Standard query 0x0000 ANY Volumio-c27afdfa9e827e4d2973ad2e5f2dfd96._tidalconnect._tcp.local, "QM" question SRV 0 0 2019 asgard.local TXT