ome significant new observations since filing, from an automated watcher polling /api/v1/getState every 4 seconds during normal listening (Qobuz, same system as the original report):
-
NOT FIXED BY RESTART, AND INTERMITTENT WITHIN A SESSION. After a full Volumio restart the same album played several tracks cleanly — then the skip returned mid-session. Earlier the same evening it had been skipping repeatedly. So the bug comes and goes within one uptime; restarting only buys a quiet period.
-
THE STRICT EVERY-SECOND-TRACK ALTERNATION BREAKS. Two confirmed skips in one listening session (Aug 10, after the restart) with three clean natural handoffs between them:
- Skip A: track at position 4 was loaded after the natural end of position 3, reported “stop” at 0:00 of 4:30, and playback resumed at position 5. The position-4 track never played.
- Clean: positions 5 → 6 → 7 all handed off normally at natural end of track.
- Skip B: position 7 ended naturally at 5:02 of 5:04, playback jumped directly to position 9. Position 8 was silently skipped.
-
STRONG HINT IT IS RESPONSE-TIME DEPENDENT: an album played repeatedly during the same session (so presumably warm at Qobuz/CDN) looped with NO skips at all; switching to a fresh album brought the skipping back immediately. This intermittency pattern (rather than deterministic alternation) points to a timing race whose window depends on how quickly the next track resolves — possibly Qobuz-side response timing. Related report with the same position-jump fingerprint from June 2026: Qobuz skipping track — where a workaround of forcing 44.1/16 CD quality was suggested. I have not yet tested the quality-cap workaround.
-
As in the original report: TIDAL on the identical system remains clean (5/5 natural handoffs), and manually tapping a queue entry always plays it correctly. Journal signature when it fires is unchanged: syncState stateService stop / currentStatus play → CoreStateMachine::play index undefined → clearAddPlayTrack of the track after the loaded one.
System configuration (in case peripherals are relevant — verified via lsusb/aplay at time of writing):
- Raspberry Pi 4, Volumio 4.119, Wi-Fi on 5 GHz
- DAC: Topping D10s, USB (enumerates as card 5, USB Audio)
- Local storage: 2 TB USB SSD (JMicron JMS567 SATA bridge) mounted at /media/ROCKET-nano — note the skips occur on QOBUZ streams, not local files
- Touchscreen attached: HDMI display + ILI Technology USB multi-touch (Volumio touch display UI running)
- DAC and SSD share the USB3 controller; touchscreen on USB2
One practical note: this system is at a seasonal house and is now powered down until my next visit, so I can’t pull additional logs in the short term. The log link in the original report covers the identical signature. In the meantime I’ll be testing my second Volumio system (same architecture, version 4.103) for the same behavior, and can gather fresh logs here on my next stay if useful.