Volumio 4 Feedback Thread

[nerd]

Hey @Kampf_Keks_3000,

I’ve analyzed both complete logs. The stuttering is caused by multiple critical issues working together.

Primary Issue - Time Desynchronization:

Client log line 3249 shows: "diff to server [ms]: 21983.7"

Your client and server have a 22-second time offset. This destroys Snapcast synchronization and causes the buffer overflows you’re seeing (server log lines 4349, 4353).

Diagnose time sync on both devices:

Follow this guide:

[GUIDE] Volumio Time Sync Watchdog (setdatetime-helper)

What it is Volumio is a bit-perfect audio player. Accurate system time is critical for: Online services such as TIDAL, Qobuz, Spotify, Web Radio Secure HTTPS connections Correct playback scheduling Multiroom synchronization Not every device has a Real-Time Clock (RTC), and not every network provides working NTP. To avoid time drift or boot-time errors, Volumio now includes a Time Sync Watchdog. How it works Runs every minute via systemd timer. Checks if ntpsec already keeps the clock in…

Since you’re running Volumio 4.071, the Time Sync Watchdog is already built-in and should be running. The 22-second offset means something is preventing proper sync.

SSH to each device and run these diagnostic commands:

Verify actual time offset:

hdr="$(curl -sI --max-time 3 https://time.is | sed -n 's/^[Dd]ate:[[:space:]]*//p')"
echo "hdr: $hdr"
echo "sys: $(date -u)"
echo "delta_sec=$(( $(date -u +%s) - $(date -ud "$hdr" +%s) ))"

If delta_sec is large on either device, force a manual sync:

sudo /usr/bin/setdatetime-helper.sh --force --verbose

Then recheck the offset with the curl command above.

Second Issue - client on WiFi:

Client log lines 32-37 show ethernet interface is down (no IP assigned). Lines 47-53 show WiFi active on 192.168.178.26 (5GHz, signal -56 dBm).

Your statement “Both devices on wired network connection does not make a difference” contradicts the logs - the client is actually on WiFi during this test.

Connect ethernet cable to client, disable WiFi in Volumio settings, verify ethernet gets IP, then test again.

Third Issue - SMB/NAS Filesystem Problems:

Server log lines 3816, 4066-4075 show multiple "CIFS: VFS: bogus file nlink value 0" errors from your FritzBox NAS mount. This indicates filesystem metadata corruption or instability.

Update SMB mount to force SMB 2.1:

In Volumio UI > Settings > Sources > Network Drives:

1. Find your FritzBox mount and click Edit
2. In the “Options” field, add: vers=2.1
3. Click Save

Do this on both server and client devices.

Fourth Issue - DHCP IP Changes:

Your devices keep getting different IPs between tests:

• Original report: server .54, client .46
• These logs: server .25, client .26
• Server was offered .36 during boot

This breaks Snapcast discovery and causes connection failures.

Set static IP addresses:

In Volumio UI > Settings > Network:

• Server: 192.168.178.25, gateway 192.168.178.1
• Client: 192.168.178.26, gateway 192.168.178.1

Complete troubleshooting sequence:

1. Diagnose time sync on both devices using commands above
2. If large offset found, force sync with setdatetime-helper
3. Switch client to ethernet
4. Set static IPs on both devices
5. Update SMB mount to vers=2.1 on both devices
6. Reboot both devices
7. Wait 5 minutes, verify time sync again
8. Test multiroom grouping
9. Submit new logs if still stuttering

The 22-second time offset is likely the main cause of stuttering, but the WiFi connection and SMB errors are making it worse. All issues need to be fixed.

Kind Regards,