Windows 11 23H2, Geekom IT13 mini-PC i7-13700H 32GB RAM + 2TB SSD
Local library stored on this SSD.
Networking Gear & Setup Details
PC and Meridian endpoint are both hardwired to 8 port dumb TP-Link switch, which in turn is connected BT Smart Hub 2 router with G.Fast broadband connection (159Mbps downstream, 29Mbps upstream)
Connected Audio Devices
Meridian 818/ID41 endpoint - hardwired Ethernet to the TP-Link switch
Number of Tracks in Library
37,000 tracks
Description of Issue
Intermittent problem, where streaming stops mid-track and Meridian endpoint disappears from client. Endpoint reappears a little later, and playback is paused at the start of the following track. Sometimes doesnāt happen at all - will play for hours and hours, other times happens after a few minutes, then again after a few more minutes.
Recent example at 17:53 UK time today 8th Dec, streaming from Qobuz.
Have tried reinstalling Roon, powering everything down, swapping patch cables but problem persistsā¦
Iāve read through that post, and while I think itās possible that my issue could be a networking problem, the symptoms donāt sound the same. In my case, playback suddenly stops, the Roon client shows no audio zone selected, then a little while later (10-20 seconds) the Meridian reappears again. This only started happening recently, before that everything was v stable with the same network setup. Before I take any further steps, like swapping out network switch, Iāll wait to see what Support advises.
My issue seems only to affect the Meridian endpoint - for example yesterday evening I streamed a local file to the Meridian and at the same time streamed Qobuz to a Squeezebox endpoint. After a while the issue I described above occurred with the Meridian, while Squeezebox playback continued.
From further testing this morning I think I have pretty much eliminated my home network from the equation: I brought the Meridian to the room where the router and the PC is, and connected both PC and Meridian to the router, with nothing else apart from the broadband connected, No WiFi connected. The issue still occurred - at 11:53 UK (GMT) this morning. I checked the router log and it did not show any disconnection of either the PC or the Meridian.
So Iām coming to the conclusion that this is more than likely a software problemā¦
Additional details on the Meridian 818v3: Firmware version 4.14, ID41 card is hardware version 2.1 running software v1.2 build 218 (which I believe is the latest).
Exactly the same problem Iāve been having - and it got particularly bad over the last 2 weeks - with my 861v8 + ID41. All my Meridian kit is @ the latest level of firmware.
There is no denying that this is @ the Roon end of the āenvironmentā - there is too much evidence available to be able to reject this hypothesis now.
Thanks for the reports here. For @Steve_Johnson and those impacted by this, can you please try the following test to check to see if the issue is related to the current Roon database?
Thanks for the response. Following the testing I did on Saturday 9th, when I still saw the problem (with PC and Meridian both directly connected to the broadband router and nothing else on the network), I restored my home network to how it was previously, and have not encountered the problem again since.
Would you advocate taking the steps you describe anyway, or should I wait until if/when I see the problem again?
The issue happened a couple of times this morning, so Iāve followed the steps above, setting up Qobuz streaming only (no local library) and have set it playing ā¦ will let you know of any recurrenceā¦
Everything seemed OK for a while, so I added my local music folder into the library a couple of days ago.
But at 12.28-12.29 GMT today the same problem occurred. Playing track: Violin Concerto in B minor, Op. 61: I. Allegro - Hilary Hahn / Colin Davis / London Symphony Orchestra / Edward Elgar.
The roonserver logfile shows the same pattern as previous occurrences - extract pasted below:
1/02 12:28:59 Trace: [Music Room] [Lossless, 24/88 QOBUZ FLAC => 24/88] [100% buf] [PLAYING @ 11:38/18:01] Violin Concerto in B minor, Op. 61: I. Allegro - Hilary Hahn / Colin Davis / London Symphony Orchestra / Edward Elgar
01/02 12:28:59 Trace: [remoting/brokerserver] [initconn 127.0.0.1:54301=>127.0.0.1:9332] Connected
01/02 12:28:59 Info: [remoting/serverconnectionv2] Client disconnected: 127.0.0.1:51022
01/02 12:28:59 Trace: [remoting/brokerserver] [initconn 127.0.0.1:54301=>127.0.0.1:9332] Resumed Session
01/02 12:28:59 Trace: [remoting/remotingprotocolv2] resume send 3 messages, 0KiB
01/02 12:28:59 Trace: [raat] [sood] Refreshing device list
01/02 12:28:59 Trace: [raatserver] [sood] Refreshing device list
01/02 12:29:00 Trace: [roondns] flushed 8 last-known-good entries
01/02 12:29:00 Trace: [meridian] [192.168.1.219:57368] GOT REQUEST o11,1464
01/02 12:29:00 Trace: [meridian] [192.168.1.219:57368] SENT RESPONSE TO [o11,1464] ack
01/02 12:29:00 Trace: [meridian] [192.168.1.219:57368] GOT REQUEST o11,8192
01/02 12:29:00 Trace: [meridian] [192.168.1.219:57368] SENT RESPONSE TO [o11,8192] ack
01/02 12:29:00 Trace: [meridian] [192.168.1.219:57368] GOT REQUEST o11,8192
01/02 12:29:00 Trace: [meridian] [192.168.1.219:57368] SENT RESPONSE TO [o11,8192] ack
01/02 12:29:00 Trace: [meridian] [192.168.1.219:57368] GOT REQUEST o11,8192
01/02 12:29:00 Trace: [meridian] [192.168.1.219:57368] SENT RESPONSE TO [o11,8192] ack
01/02 12:29:01 Trace: [meridian] [192.168.1.219:57368] GOT REQUEST o11,12288
01/02 12:29:01 Trace: [meridian] [192.168.1.219:57368] SENT RESPONSE TO [o11,12288] ack
01/02 12:29:01 Trace: [meridian] [192.168.1.219:57368] GOT REQUEST o11,8192
01/02 12:29:01 Trace: [meridian] [192.168.1.219:57368] SENT RESPONSE TO [o11,8192] ack
01/02 12:29:01 Trace: [meridian] [192.168.1.219:57368] GOT REQUEST o11,8192
01/02 12:29:01 Trace: [meridian] [192.168.1.219:57368] SENT RESPONSE TO [o11,8192] ack
01/02 12:29:01 Trace: [meridian] [192.168.1.219:57368] GOT REQUEST o11,8192
01/02 12:29:01 Trace: [meridian] [192.168.1.219:57368] SENT RESPONSE TO [o11,8192] ack
01/02 12:29:01 Trace: [meridian] [192.168.1.219:57368] GOT REQUEST o11,8192
01/02 12:29:01 Trace: [meridian] [192.168.1.219:57368] SENT RESPONSE TO [o11,8192] ack
01/02 12:29:01 Trace: GOT RESPONSE done
01/02 12:29:01 Debug: FTMSI-B closed file for qo/4582AE53; open files:0
01/02 12:29:01 Debug: FTMSI-B qo/4582AE53 download status: AllBlocksDownloaded accessTimeout:True openFiles:0 prev:(AllBlocksDownloaded,True,1)
01/02 12:29:01 Info:
--[ SignalPath ]---------------------------------------------
SignalPath Quality = Inactive
Elements:
------------------------------------------------------------
01/02 12:29:01 Warn: inactive signal path :(
01/02 12:29:01 Info: [zone Music Room] OnPlayFeedback StoppedEndOfMediaNatural
01/02 12:29:01 Debug: [zone Music Room] _Advance (Track)
01/02 12:29:01 Trace: [Music Room] [Lossless, 24/88 QOBUZ FLAC => 24/88] [100% buf] [LOADING @ 0:00] Violin Concerto in B minor, Op. 61: II. Andante - Hilary Hahn / Colin Davis / London Symphony Orchestra / Edward Elgar
01/02 12:29:01 Trace: [Sooloos.Broker.Transport.MeridianZonePlayerEndpointStreamingClient disposed]
01/02 12:29:01 Trace: [Sooloos.Audio.Meridian.EndpointManagementClient disposed]
01/02 12:29:01 Info: [meridian] connection failed to 192.168.1.219 management=57369 control=57368 clock=49154
01/02 12:29:01 Info: [transport] destroyed zone Music Room was playing? True
01/02 12:29:01 Trace: [zone Music Room] Suspend
Are you by any chance making use of Sonos devices along with your Meridian gear? If yes, there have been a few other reports, and it looks like there might be beta firmware available through your Meridian dealer that may help:
No Sonos here either. The time before last that the problem occurred was solved by killing and restarting roonserver (no other changes) but in the most recent occurrence, that didnāt work, neither did rebooting the PC, but power cycling the Meridian 818 didā¦
Iām still getting this issue, with the same pattern in the log file that I posted previously. 3 times this afternoon while listening to Shostakovich 4, LSO, Noseda, LSO Live on Qobuz. First time at 15.55 GMT
Iām running the latest Roonserver version - build 1365.
@Support - what further information can I provide for this to be investigated further? As you can see from the posts above I am not the only one experiencing this issue.
Please accept our apologies for the long delay without a conclusion in this topic thread. We havenāt forgotten about you and the team has escalated this case to senior development in the interim with available logs from the reporting period. Hereās what we know.
Diagnostics do show the Meridian dropping out of visibility to RoonServer. However, forcible closures and other network changes are also reported in logs across Roonās services: RAATServer, Qobuz authorizations, and generic HTTP requests upstream all fail at some point.
The failure mechanism weāve identified with Meridian for the ID41ās particular firmware generation will be triggered by higher volumes of incoming packets to the ID41 card. Itās not the ubiquitous experience of Roon users with the ID41 to encounter the issue. Itās also within Meridianās jurisdiction to implement a fix - the issue is within the Meridian firmware itself.
The presence of broader network reachability issues doesnāt prove the failure mechanism for the ID41 one way or the other. However, you can likely improve symptoms by investigating some settings in the setup and topology.
Concerning the ID41, do you notice that playing back lower sample rate/bit-depth files less often triggers a dropout or disconnection with this Zone? What happens if you downsample everything in Roon on that Zone in Device Setup or play back only low-quality FLAC/mp3 files?
The Home Hub 2 doesnāt have selective bandwidth allocation from what I can tell and youāve tested with the WiFi removed as a variable. We want to investigate the forcible network closures. Do you have any third-party security on your network or RoonServer machine? What about anti-virus software on your RoonServer machine that might selectively block Roon background processes from connecting to the internet?
What happens if you bypass the TP-Link switch entirely or try different ports?
Weāll keep an eye out for your response. Thank you again for your ongoing patience.