Noris,
Thanks for your reply. Unfortunately I am about to go travelling for
two weeks, so we will probably have to complete this process after
April 11th. However I will try to answer your questions below.
Thanks for contacting us regarding this issue, I’d be happy to
troubleshoot with you here. I have a few questions starting off:
- Can you please confirm if you are using the Devialet Air or
Devialet RAAT protocol to stream to the endpoint?
I set the devialet source to be “roon ready” using the source selector
on the devialet amp. Once it starts operating though, it appears to switch
to AIR. This puzzles me a bit as I think I have not explicitly enabled AIR in
the roon software: under Settings-Audio I have enabled Devialet
Networked only, and Airplay is not enabled.
Should I be doing something else?
- What is the model/manufacturer of your switch?
My router/switch is:
NetComm/Wireless
VDSL2/ADSL2+ Dual band AC1600 Gigabit gateway NF18ACV
and there is also a second switch in the ethernet path:
TP link TL-SF1008D
However I am pretty sure the hardware is not the problem as some days,
like today, the system works perfectly and as far as I am aware,
nothing has changed since the last time I had the problem!
- Have you tried rebooting the Core, Networking gear and endpoint
yet? I would give this a try.
Yes of course, several times and in all possible sequences. I check that the CPU, disk and network of the NAS are not busy doing other things, as surely the problem is that somehow the NAS cannot deliver the data quickly enough to either the roon core on the NAS or from the core to the devialet? ie I review the NAS resource monitors and also run the linux “top” program on the NAS to look for disk/cpu/network intensive processes and check that there are none.
- I noticed that your QNAP NAS model has two Ethernet ports, can you
please give the other one a try and let me know if the same behavior
occurs?
In fact it has four. I will try them all, but doubt this is the issue
- as I said sometimes it works perfectly so my guess is a software
issue rather than a hardware issue.
In the forums somewhere I read that other people who have had this
apparently common problem claimed that the upstream ISP might be doing
something that interferes. If this is the case can you please let me
know what should I tell my ISP about what I require them to do or not
do to keep Roon working. The ISP is quite approachable and willing to
make changes.
My suspicion is that a larger buffer might solve such problems - I see
one buffer option in roon where I have set it to the 5000ms maximum -
perhaps larger buffer options would be helpful?
Thanks for your further ideas, I feel a permanent understanding/fix of
this problem is essential.
W
PS I also note that the roon app on windows 10 works well, I use that
mostly. But the roon app on my android phone (running 5.1 baseband
20234) is hard to use as random letters are missing in the menus.