suby
January 27, 2026, 2:58pm
1
Hello dear community.
I have a problem with native Tidal playback.
When I press pause and then play during playback, the name of the previous song and the sample rate of 44kHz appear in the Volumia graphical interface. This is displayed until the next song starts playing, then everything is displayed correctly again until I press pause.
This happens in both version 3.886 and 4.0xx. Thanks for any information.
This has nothing to do with Tidal, but a core race condition. Issue has been addressed multiple times to Volumio’s core team, also by me with plenty examples, but not resolved yet.
suby
January 27, 2026, 3:16pm
3
Thank you very much for the reply, it’s strange that this doesn’t happen to me when playing my local library or Spotify queue.
It happens with all source, some more then others.
Local files, Qobuz, Tidal,…
opened 02:33PM - 04 Aug 25 UTC
Verbatim from: https://community.volumio.com/t/public-beta-test-audio-without-co… mpromise-refining-the-future-of-volumio-on-bookworm/72576/489
### Environment:
* Device: Raspberry Pi 5
* Software: Volumio BW V4.021
* Audio Output: HiFiBerry DAC+ Pro (rPi5)
* Network: Wired Ethernet
* Services Tested:
* Spotify Connect (Community plugin)
* Qobuz Connect (MyVolumio)
* Tidal Connect (MyVolumio)
### Minimal Reproduction Steps:
1. Start Volumio BW V4.021
2. Launch any Connect service:
* Spotify Connect: Works normally
* Qobuz Connect: Metadata often freezes, playback intermittent
* Tidal Connect: App enters endless loading, metadata delayed, playback fails
3. Switch between Connect services (e.g., stop Spotify, start Qobuz, then Tidal)
4. Observe:
* Metadata freeze in SoundCheck
* Audio dropouts or playback failure
* Occasional full system crash requiring hard reboot
### Expected:
* Connect playback initializes reliably
* Metadata populates fully and accurately
* System remains responsive across Connect service transitions
### Actual:
* `CoreStateMachine` receives `servicePushState` events from MPD or the Connect service **before queue/trackBlock is initialized**
* Results in:
1. Missing or frozen metadata
2. Misleading `updateQueue error: null` in logs with debug stack traces
3. Intermittent playback failures or audio dropouts
4. In severe cases, Volumio crashes or becomes unresponsive
### Suspected Race Condition:
* Queue population vs. `servicePushState` timing:
```
Connect Service -> MPD/Backend -> servicePushState()
|
v
trackBlock undefined
|
+---> Missing metadata
+---> updateQueue error: null
+---> Logs show misleading stack traces
```
* Combined Spotify/Qobuz/Tidal usage increases likelihood of race triggers
* Node.js 20 on Bookworm exposes timing issues previously hidden on Node.js 14 (Buster)
* Queue double-nesting occasionally produces array entries instead of track objects, further breaking `getTrack` and `trackBlock` handling
### Impact:
* Metadata gaps, frozen UI, playback failures
* `vrestart` sometimes fails with rotary encoder errors, requiring hard reboot
* Cross-service instability escalated after Tidal Connect integration