Hey @Lethalsheep, @jkoks, @balbuze,
Thanks for testing.
One note on how reports are handled here, because it directly affects whether yours can be acted on.
This is a plugin under active development. Reports that arrive in fragments - a symptom in one post, a hardware detail in an edit, a partial log later - cannot be investigated. Each fragment restarts the analysis, and none of them on its own contains enough to reproduce anything. This has been clearly stated in the opening post.
You choose not to provide requested details I choose not to invest my time in investigating.
In short, one post containing:
- Exact Volumio version (for example 4.123, not “latest”)
- DAC or output device in use, and how it is connected
- Exact steps to reproduce
- What actually happens
- What you expected to happen
- A log link from http://<volumio_IP>/dev
On logs: /tmp and /var/log are held in RAM. A reboot destroys them. The log must be collected after reproducing the problem and before any power cycle.
Pasted extracts chosen by the reporter are not a substitute for the full log link. A section that looks unremarkable to you is frequently where the failure is actually recorded, and the surrounding context is what makes it readable.
We are glad to have testers and every complete report is read and worked on. Where the requested details are not supplied, the problem cannot be reproduced, and it will not be progressed. That is not a judgement of anyone - it is the limit of what can be done without the information.
Kind Regards,