I have been using HQP integrated with Roon for about a year now. I stream with a Microrendu. My server is a SGC Sonicorbiter i7 specifically for HQP. Until today, I have been able to upsample to DSD 512 using any filter except the xtr non -2s with only the very occasional issue (buzzing sound, fixable by stopping track and restarting).
Yesterday, I updated the FW on my MR and update HQP. Now, using ply-sincshrt-mp I get very frequent buzzes and clicks. I have tried rebooting everything including internet, server, etc. No improvement.
Any ideas? I know this kind of issue its usually overloading the server, but this server should have and has had plenty of juice. let me know your thoughts.
There are two likely problems, CPU load or some networking issue.
Trying with -2s filters helps telling if it is a CPU load problem.
Trying without NAA (microRendu) with straight USB tells if it’s a networking or NAA issue.
Reducing number of variables helps locating the problem… Also considering any software configuration changes or other changes in the system around the same time as software upgrade.
If the previous version of HQP was 4.0.4 and now you have 4.0.6, there are no changes in the code that is involved your playback case.
I really don’t have detailed information about what was updated in microRendu firmware update. I also installed the 2.6 on my microRendu, but I haven’t got time yet to try it out. But from NAA perspective I don’t think the NAA software module has changed, only the name it represents outside has been changed form “default” to something more meaningful for cases where you have more than one NAA. The OS itself may have got some updates, but I don’t know about those.
There isn’t anything really drastic about the 2.6 update. It’s the same Linux Kernel with patches for new native DSD devices. Some of the Apps have been updated, but this has occurred over many months.
I think I was using MR 2.5 before updating to 2.6 the other night. Everything worked fine except for the very occasional buzz, say every 90 minutes, easily fixed by stopping and restarting stream. Rebooting server made it happen less often.
Is there a way to uninstall and reinstall 2.6? Or, reinstall 2.5 (not sure I even need the 2.6 functions)? While the issue could be the Amanero chip, the fact that the problem started immediately after updating to 2.6 makes it hard to rule ut the update as the cause.
The Amanero Combo 384 has been a pain. I had the beta installed in October. It worked fine until it completely crashed in December. reinstalled and it has worked well until now. I have been hearing since April of 2017 when i bought my dac about Amanero finsihubg the new firmware and still nothing. The Lampi sounds great, but I would not buy another Amanero dac.
I hope MR downgrade to 2.5 is a workaround.
You are not alone with concerns about Amanero firmware related to native DSD on Linux. We all hope some news from Amanero.
New Amanero FW is still Beta and not completely reliable. However interesting to ask Lampi which FW version is currently installed on your DAC ?
If Amanero unable to fix (release) FW for native DSD on LINUX, for technical or others reasons, alternative might be, sadly, to use a WIN RoonBridge / NAA networked endpoint. Amanero ASIO driver is OK and seems reliable with native DSD up to DSD512.