Getting really frustrated trying to run down the source or sources of clicks and dropouts. To level-set, I would say the frequency and severity of this behavior varies between “occasionally annoying” and “materially impairs enjoyment” of the music. The degree and frequency varies such that when I have made a change to hardware or software configuration, I can often get through an entire song or most of a song before the disappointment sets in again. I’ve been up and down this board and hardware manufacturers sites, employed google search creatively, and I’m stuck looking for a new hypothesis.
I’m willing to throw some money at solving the problem, but I don’t want to drop a large sum on DAC or renderer hardware unless I’m confident that the problem has been isolated. I really like Roon (full subscriber), but I’m hesitant to commit to re-configuring everything (or upping to lifetime) until I’m confident I can make it stable. Other than the clicks and dropouts, I’m getting some really good sound from both endpoints (eg way better than I used to experience using a Sonos ZP90->Creek OBH playing the same 16/44 WAV file).
Hardware and network configuration:
Roon core is located on core i7 desktop: Windows 10, roon db and software on 256 gb SSD, 12GB internal RAM. all local data other than applications is located on separate 3TB internal hard drive. This machine is hard-wired via Cat 6 to the router.
Music files, mostly 16/44 WAV, with some 24/96 and 24/192 located on synology ds716+, with two very new WD Red 6TB drives set in RAID configuration. Library size is about 1600 albums/15000 tracks/1.2TB. These drives also house other media files, but no other data are being accessed or streamed from this media-only NAS when the dropouts are occurring.
Subscribed to Tidal, although most listening is with locally owned/stored files.
Network - recent vintage 1GB ASUS AC router, connects directly via cat 6 to two additional 1GB ASUS routers, configured as WAP’s. A 24 port GB switch is also connected to this router, but the WAPs go straight into the router, not via the switch. The Synology NAS is connected to this switch.
Currently, I am using only two Roon endpoints for listening, although a third (SOSE to main listening room) is waiting for successful resolution of this problem:
(1) the aforementioned core i7 machine, with an older vintage 24/96 HRT music streamer DAC connected via USB (exclusive mode). This configuration experiences fewer dropouts than (2)
(2) SonicOrbiter SE connected directly to one of the WAP’s via cat6 (short run). Running latest firmware (2.2). Connected via USB to Musical Fidelity V.90 DAC, in turn connected to Creek OBH Headphone amplifier. SE uses IFI power supply.
Tweaks attempted:
- Tried two different V90 DAC’s.
- Changed the native 12V wall wart for the V90 to a separate IFI 12V power supply. (saw some improvement from this in unrelated ways, btw).
- Uninstalled and reloaded Roon core after experiencing a number of crashes. Crashes seem to be fixed, clicks and dropouts, no.
- switched out USB cable from the SOSE to the DAC.
- switched out network cable from SOSE to WAP.
- various tweaks to software configuration within Roon. Using fixed volume / no volume leveling or other processing at the core level.
Any reasonable hypothesis will be given serious consideration. I’m willing to ditch the DAC, a WAP, the SOSE for a mac mini or (other??), power supplies, cables, etc. I could migrate the Roon Core to the Synology NAS, but I’m not using an SSD on this device. Changing out the NAS or the core i7 desktop would be really unpleasant, and I don’t see any evidence that either is the culprit, but willing to listen to good ideas. The network performance seems very good for all other applications (eg HD video streaming wirelessly on the the same WAP as to which the SOSE connects). Massive file transfers over the wired network complete successfully at a seemingly appropriate rate (averaging 50+MB/sec transfer rates).