Ok, so the Oppo, dmesg reporting no USB errors which is good and bad (assumes USB is working fine).
The only differences I can see is your DAC’s are running at USB 2.0 (high speed), mine is USB 1.x (full speed):
01/19 13:20:57 Trace: [RAAT::OPPO USB AUDIO 2.0 DAC] pcm card longname OPPO OPPO USB AUDIO 2.0 DAC at usb-1c1d000.usb-1, high speed
01/19 15:23:09 Trace: [RAAT::USB Audio Device] pcm card longname C-Media Electronics Inc. USB Audio Device at usb-1c1d400.usb-1, full speed
Roon logs indicate constant dropouts:
01/19 13:21:56 Warn: [RAAT::OPPO USB AUDIO 2.0 DAC] dropout of 882 samples at 580166 [2]
Are you by any chance using a USB hub on the Neo, or, DAC directly plugged into the Neo?
Also, if you get another chance, please can you try using the performance CPU governor on the Neo, then see if dropouts occur? dietpi-config > Performance > CPU Gov > Performance
Dang 58LesPaul ! I was just booting up trying to jump into the testing here as well, you beat me to it
Sounds promising! Will test here later too!
/Kenneth
Great to hear. Yep, spot on, does indicate an issue with the ondemand scaling on 4.9 kernel. Appears the throttle up isn’t being triggered by Roon Bridge process. Or under-voltage issue with one of the frequency steps.
Also, is there a way to keep this setting (it returns to “ondemand” after poweroff/on)
DietPi applies your chosen CPU gov during bootup. So lets check settings, please paste results: cat /DietPi/dietpi.txt | grep cpu_gov
And: systemctl status firstrun -l
Finally, lets check current cpu gov: cat /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
root@DietPi:~# systemctl status firstrun -l ● firstrun.service - LSB: PLEASE DO NOT INTERRUPT THE FIRST BOOT Loaded: loaded (/etc/init.d/firstrun) Active: inactive (dead)
Thanks, all appears to be in order, should be fine.
Please try selecting performance again from dietpi-config, reboot system and check the results match performance?
Excellent, thanks for letting me know
I’ve made some notes and will try to debug the ondemand issue further. But for now, Performance CPU gov is a working solution.
Temps should be fine if only using RoonBridge (minimal CPU load), however, If not using a heatsink, might be worth checking CPU temps now and then (< 60’c is great, but < 80’c as a max limit):
─────────────────────────────────────────────────────
DietPi CPU Info
Use dietpi-config to change CPU / performance options
─────────────────────────────────────────────────────
Architecture | armv7l
Temp | 40’c | Optimal temperature.
Governor | performance
systemctl status firstrun -l
firstrun.service - LSB: PLEASE DO NOT INTERRUPT THE FIRST BOOT
Loaded: loaded (/etc/init.d/firstrun)
Active: inactive (dead)
Yep, looks fine, should be working . mmm, we could try limiting CPU clocks at each frequency and see if any of them have any effect on this. But, lets check network issues first.
I still have the “Network error” messages…
Can you elaborate on the errors you are receiving? And, are you using USB WiFi or onboard Ethernet on the Neo?