Great Kudos also from my side to all who have been involved!
Whether it’s related or not, I’ve recently (over the last two weeks or so) been experiencing recurring audio stuttering on both of my Volumio installations. Since updating to V4.069, I no longer have this problem. Hopefully it stays that way.
And so, a very frustrating problem has been solved. The Tidal connection is now working perfectly. There are not enough words to thank user @hulver who found the key to the problem and the Volumio team for their availability and effort in quickly resolving the issue!
Hi,
Sad to say, that the problem presist. My version is 4.071 and i have to deactivate and then activate tidal conenct on sources If RPI4 with RPI DAC+ is idle for awhile.
This is just annoying!
I assume that the problem fixed with all versions? (Stable, Test, Alpha)
Hi @PoisonDwarf
You are on a version that includes the fix to the original problem and that goes for stable & test. For me, and I’m sure others or there’d be more reports, Tidal is working perfectly now, so I think your issue is likely to be something else. Suggest you share a log.
Hi,
Sure, I just activated the live log and restart Tidal Connect and now Just wait.
System is RPI 4 B with 4GB mem, Raspberry DAC+ The behaviour is the same in Wifi or wired networking.
Hah! It died already. Tidal Connect just dissappears on sources listing in Windows Tidal Client
Edit: Livelog does not show the problem. I must dig deeper then.
Edit2 vtcs.service does not show any more info either. About 4min of restarting vtcs Volumio disappears on Tidal Client sources on Windows client. Phone (Android) client shows it and It works just fine. What is happening here?
sudo journalctl -u vtcs.service --since "2025-11-22 18:06:00" --follow
Nov 22 18:06:40 volumio vtcs[27639]: [2025-11-22 18:06:40.187] [tisoc] [error] [SpkconServer.cpp:375] recv error. socket disconnected
Nov 22 18:06:40 volumio vtcs[27639]: [2025-11-22 18:06:40.187] [tisoc] [warning] [SessionManagerImpl.cpp:240] Illegal State: IDLE
Nov 22 18:06:40 volumio systemd[1]: Stopping vtcs.service - Volumio Tidal Connect Service...
Nov 22 18:06:40 volumio systemd[1]: vtcs.service: Killing process 27646 (vtcs) with signal SIGKILL.
Nov 22 18:06:40 volumio systemd[1]: vtcs.service: Deactivated successfully.
Nov 22 18:06:40 volumio systemd[1]: Stopped vtcs.service - Volumio Tidal Connect Service.
Nov 22 18:06:49 volumio systemd[1]: Started vtcs.service - Volumio Tidal Connect Service.
Nov 22 18:06:49 volumio vtcs[31522]: STARTING TidalConnect services, version: 1.5.1-beta1
Nov 22 18:06:49 volumio vtcs[31522]: STARTED TidalConnect services
[v4.071 Raspberry Pi4b 2GB 32GB SD USB DAC]
Hi @PoisonDwarf - I’ll just add something that I experience that may be related. I experience a quirk re:device discovery.
If I open the Tidal App on my Windows 10 Pro laptop, it does not see my Volumio/Tidal Connect Raspberry Pi instance, but if I also open the Tidal App on my Android phone or on my Windows 11 Pro desktop, then my Windows 10 Pro laptop can now see and connect to my Volumio/RPi Tidal Connect setup.
I may have developed that habit of leaving the App open on my phone while I listen to music via Volumio/Tidal Connect on my laptop.
Timeouts and dropped connections don’t seem to be an issue but sometimes playback will pause and I’ll have to manually ‘click’ next to advance to the next song in the playlist. (This may be an ISP or Tidal thing.not Volumio?)
.
.
(P.S. note: If I encounter a ‘LOW’ res song in a playlist I still have to restart/reboot my RPi but this issue is being addressed in the ‘Tidal Connect Failures’ thread.)
I have been watching the log whole evening and playing via phone. Short pauses for a while, and finally got something maybe useful here.
Log when Tidal Connect crashes
Nov 22 21:29:49 volumio vtcs[31522]: [close:85] Entering
Nov 22 21:29:49 volumio vtcs[31522]: [close:100] Exiting
Nov 22 21:29:49 volumio vtcs[31522]: [open:50] Opening with sample rate: 44100, type: 3
Nov 22 21:29:49 volumio vtcs[31522]: [start:106] Entering
Nov 22 21:29:49 volumio vtcs[31522]: [start:113] Reopening PCM device...
Nov 22 21:29:49 volumio vtcs[31522]: [start:115] PCM opened successfully.
Nov 22 21:29:49 volumio vtcs[31522]: [start:120] Exiting
Nov 22 21:29:49 volumio vtcs[31522]: [feedThread:223] Entering
Nov 22 21:29:49 volumio vtcs[31522]: [2025-11-22 21:29:49.827] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
Nov 22 21:29:49 volumio vtcs[31522]: [2025-11-22 21:29:49.907] [tisoc] [warning] [PlaybackControllerImpl.cpp:846] Empty media_info.
Nov 22 21:29:56 volumio vtcs[31522]: [2025-11-22 21:29:56.339] [tisoc] [critical] [TidalEvents.cpp:155] [ASSERT] playingTrackCompleted(prepared_play_log_event_)
Nov 22 21:29:56 volumio vtcs[31522]: [2025-11-22 21:29:56.339] [tisoc] [critical] [TidalEvents.cpp:156] [ASSERT] playingTrackCompleted(prepared_playback_statistics_event_)
Nov 22 21:29:56 volumio vtcs[31522]: [2025-11-22 21:29:56.339] [tisoc] [critical] [TidalEvents.cpp:157] [ASSERT] playingTrackCompleted(prepared_streaming_session_end_event_)
Nov 22 21:29:56 volumio vtcs[31521]: Segmentation fault
Nov 22 21:29:56 volumio systemd[1]: vtcs.service: Main process exited, code=exited, status=139/n/a
Nov 22 21:29:56 volumio systemd[1]: vtcs.service: Failed with result 'exit-code'.
Nov 22 21:29:56 volumio systemd[1]: vtcs.service: Consumed 1min 5.985s CPU time.
Nov 22 21:29:56 volumio systemd[1]: vtcs.service: Scheduled restart job, restart counter is at 1.
Nov 22 21:29:56 volumio systemd[1]: Stopped vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:29:56 volumio systemd[1]: vtcs.service: Consumed 1min 5.985s CPU time.
Nov 22 21:29:56 volumio systemd[1]: Started vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:29:56 volumio vtcs[19495]: BYE TidalConnect
Nov 22 21:29:56 volumio systemd[1]: vtcs.service: Deactivated successfully.
Nov 22 21:29:57 volumio systemd[1]: vtcs.service: Scheduled restart job, restart counter is at 2.
Nov 22 21:29:57 volumio systemd[1]: Stopped vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:29:57 volumio systemd[1]: Started vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:29:57 volumio vtcs[19498]: BYE TidalConnect
Nov 22 21:29:57 volumio systemd[1]: vtcs.service: Deactivated successfully.
Nov 22 21:29:57 volumio systemd[1]: vtcs.service: Scheduled restart job, restart counter is at 3.
Nov 22 21:29:57 volumio systemd[1]: Stopped vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:29:57 volumio systemd[1]: Started vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:29:57 volumio vtcs[19501]: BYE TidalConnect
Nov 22 21:29:57 volumio systemd[1]: vtcs.service: Deactivated successfully.
Nov 22 21:29:58 volumio systemd[1]: vtcs.service: Scheduled restart job, restart counter is at 4.
Nov 22 21:29:58 volumio systemd[1]: Stopped vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:29:58 volumio systemd[1]: Started vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:29:58 volumio vtcs[19504]: BYE TidalConnect
Nov 22 21:29:58 volumio systemd[1]: vtcs.service: Deactivated successfully.
Nov 22 21:29:58 volumio systemd[1]: vtcs.service: Scheduled restart job, restart counter is at 5.
Nov 22 21:29:58 volumio systemd[1]: Stopped vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:29:58 volumio systemd[1]: Started vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:29:58 volumio vtcs[19507]: BYE TidalConnect
Nov 22 21:29:58 volumio systemd[1]: vtcs.service: Deactivated successfully.
Nov 22 21:29:59 volumio systemd[1]: vtcs.service: Scheduled restart job, restart counter is at 6.
Nov 22 21:29:59 volumio systemd[1]: Stopped vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:29:59 volumio systemd[1]: vtcs.service: Start request repeated too quickly.
Nov 22 21:29:59 volumio systemd[1]: vtcs.service: Failed with result 'start-limit-hit'.
Nov 22 21:29:59 volumio systemd[1]: Failed to start vtcs.service - Volumio Tidal Connect Service.
If I try to start it directly with systemctl, I get the same result. But if I deactivate and activate Tidal Connect on Sources, it will start. See logs below.
Nov 22 21:35:48 volumio systemd[1]: vtcs.service: Scheduled restart job, restart counter is at 4.
Nov 22 21:35:48 volumio systemd[1]: Stopped vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:35:48 volumio systemd[1]: Started vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:35:48 volumio vtcs[20582]: BYE TidalConnect
Nov 22 21:35:48 volumio systemd[1]: vtcs.service: Deactivated successfully.
Nov 22 21:35:49 volumio systemd[1]: vtcs.service: Scheduled restart job, restart counter is at 5.
Nov 22 21:35:49 volumio systemd[1]: Stopped vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:35:49 volumio systemd[1]: vtcs.service: Start request repeated too quickly.
Nov 22 21:35:49 volumio systemd[1]: vtcs.service: Failed with result 'start-limit-hit'.
Nov 22 21:35:49 volumio systemd[1]: Failed to start vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:36:51 volumio systemd[1]: Started vtcs.service - Volumio Tidal Connect Service.
Nov 22 21:36:51 volumio vtcs[20706]: STARTING TidalConnect services, version: 1.5.1-beta1
Nov 22 21:36:51 volumio vtcs[20706]: STARTED TidalConnect services
I am a little confused here 
@PoisonDwarf, the “vtcs.service: Start request repeated too quickly.” message looks very similar to the message I’ve seen when I attempt to play a ‘LOW’ res song and my RPi hangs and has to be rebooted.
What song/artist are you playing or about to play when you get your failure?
Hi,
The song was Dark Tranquillity Phantom Days started 21.12.23
Nov 22 21:12:23 volumio vtcs[31522]: [open:50] Opening with sample rate: 44100, type: 3
I paused it
Nov 22 21:16:13 volumio vtcs[31522]: [pause:161] Exiting
And then came back and starting again
Nov 22 21:29:49 volumio vtcs[31522]: [open:50] Opening with sample rate: 44100, type: 3
Nov 22 21:29:49 volumio vtcs[31522]: [start:106] Entering
Nov 22 21:29:49 volumio vtcs[31522]: [start:113] Reopening PCM device...
Nov 22 21:29:49 volumio vtcs[31522]: [start:115] PCM opened successfully.
Nov 22 21:29:49 volumio vtcs[31522]: [start:120] Exiting
Nov 22 21:29:49 volumio vtcs[31522]: [feedThread:223] Entering
Nov 22 21:29:49 volumio vtcs[31522]: [2025-11-22 21:29:49.827] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::er>
Nov 22 21:29:49 volumio vtcs[31522]: [2025-11-22 21:29:49.907] [tisoc] [warning] [PlaybackControllerImpl.cpp:846] Empty>
Nov 22 21:29:56 volumio vtcs[31522]: [2025-11-22 21:29:56.339] [tisoc] [critical] [TidalEvents.cpp:155] [ASSERT] playin>
Nov 22 21:29:56 volumio vtcs[31522]: [2025-11-22 21:29:56.339] [tisoc] [critical] [TidalEvents.cpp:156] [ASSERT] playin>
Nov 22 21:29:56 volumio vtcs[31522]: [2025-11-22 21:29:56.339] [tisoc] [critical] [TidalEvents.cpp:157] [ASSERT] playin>
Nov 22 21:29:56 volumio vtcs[31521]: Segmentation fault
Nov 22 21:29:56 volumio systemd[1]: vtcs.service: Main process exited, code=exited, status=139/n/a
Nov 22 21:29:56 volumio systemd[1]: vtcs.service: Failed with result 'exit-code'.
The service was automatically tried to start 6 times and then it throws the boxing gloves into the ring.
After this I tried to manually restart myself with systemctl. (restart, then stop and start) All the too quickly messages are for that. Then sources > Tidal Connect disable > Tidal Connect enable. No need to reboot.
journalctl -u vtcs.service |grep "Opening with sample rate:"
Tells me that there’s no lower than 44100 on samplerate during this log period. Mostly 44100, couple of 48800 and few 96000
If this is the song,
Yep, Just listening my listenbrainz weekly jams and then suddenly at the song #20 Anathema - Fragile Dreams Tidal connect (vtsc.serivice) hang with segmentation fault (And Windows Client gives some Java errors). I was trying to start it but it just give me segmentation faults again and again. Then I was trying the song #21 on the list and all worked again. This song is also 44100, type: 0
Volumio is Linux, constant rebooting is not an option!
This is just hilarious! 
@PoisonDwarf - Yeah your,
are both 'LOW" res tracks. This is the ‘Tidal Connect Failures’ saga and its inability to play ‘LOW’ res tracks.
You need to try and advance to another song, ‘High’ or ‘MAX’ encoded then go thru the reboot restart. 
then find your ‘tidal connect’ instance again.
Hi Guys, we hear you. We already are working to fix this issue and we are waiting for a new version of the library from TIDAL.
We will keep you posted
We have published an updated version of TIDAL Connect for Volumio 4 in order to fix the issues with low res playback. We have not yet issued a new release for Volumio 3 since the problem was not reproducible there.
@PoisonDwarf Your issue seems different, we are in contact with TIDAL to get it fixed, but we need more info. Could you share a log containing the crash?
Hi,
Thanks for the update! <3
I’ll try to reproduce the problem that I encounter.
journalctl -u vtcs.service --follow
will be on while listening.
Cheers
Hi, it is reproducible for me on v 3.877 on minidsp shd studio. Tidal goes silent when switching from max to high quality via tidal connect. Is there a chance for a fix for 3.x please? Thank you!
The issue you are experiencing is most likely something different, can you send a log from your device after reproducing the issue you mentioned?
@devgianlu hi!, thanks for your reply, heres the log link I think this might be the line with the issue, the timestamp of when it stopped producing sound is about right:
` 18:00:26 minidsp-shd vtcs[1638]: [2026-01-21 18:00:26.032] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
heres the full log
http://logs.volumio.org/minidspshd/LjZZddE.html
I was able to reproduce it once more a few minutes later:
http://logs.volumio.org/minidspshd/s91YqFH.html
Jan 21 18:09:26 minidsp-shd vtcs[1638]: [2026-01-21 18:09:26.039] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
Jan 21 18:09:26 minidsp-shd vtcs[1638]: [2026-01-21 18:09:26.039] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_BAD_HEADER
Jan 21 18:09:26 minidsp-shd vtcs[1638]: [2026-01-21 18:09:26.039] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
Jan 21 18:09:26 minidsp-shd vtcs[1638]: [2026-01-21 18:09:26.039] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_BAD_HEADER
Jan 21 18:09:26 minidsp-shd vtcs[1638]: [2026-01-21 18:09:26.039] [tisoc] [warning] [flac_decoder.cpp:302] FLACDecoder::error_callback FLAC__STREAM_DECODER_ERROR_STATUS_LOST_SYNC
Hello everyone and thank you for your patience. Version 3.905 has been released to the test channel with a potential fix for TIDAL Connect. Please let us know if it solves the playback issues.