I am having a both bizar and irritating problem.
Running Core on a virtual Windows machine with an ethernet interface connected to a 48-port switch in VLAN 1.
Endpoint is a AURALiC ARIES G2.1
When the ARIES G2.1 is connected to the network using WLAN there is no problem. It is served via an POE access point fed from the same switch. Obviously, the switch port is (also) member of VLAN 1.
When I change the ARIES G2.1 to use its wired ethernet interface, connected to the same switch on a port in VLAN 1, it is IMPOSSIBLE to listen to music from Tidal or Qobus.
The logfile of Core reports dropouts like so:
06/03 13:02:30 Warn: FTMSI-B-OE qo/90520FB3: poor connection kbps:992.0 (min:1325.0)
06/03 13:02:30 Warn: FTMSI-B-OE qo/0003BDC3: poor connection kbps:909.0 (min:1325.0)
06/03 13:08:27 Warn: [ARIES_BILZEN] [zoneplayer/raat] long rtt sync AURALiC ARIES_G2: realtime=1374942628806 rtt=91000us
offset=-5309371us delta=-78646us drift=-64663us in 355.3225s (-181.985ppm, -655.145ms/hr)
06/03 13:10:27 Warn: [ARIES_BILZEN] [zoneplayer/raat] long rtt sync AURALiC ARIES_G2: realtime=1494920814452 rtt=65000us
offset=-5288185us delta=-62051us drift=-43477us in 475.3055s (-91.473ppm, -329.303ms/hr)
06/03 13:10:44 Warn: [raat/tcpaudiosource] send failed: Object reference not set to an instance of an object.
06/03 13:10:44 Warn: [raat/tcpaudiosource] disconnecting + retrying
06/03 13:10:55 Warn: [ARIES_BILZEN] [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
What am I missing here? Can someone explain the topology of Roon?
Is it the Core server downloading content and stream it to endpoints using RAAT?
In that case, how on earth can I suffer from slow download speeds if nothing changed to the config of the core server?