Hi @Michael_Yeaman,
Is your Vault up-to-date on newest firmware?
Is the behavior the same when you have both the endpoint + Core connected via Ethernet?
Yes, when I check for upgrades on the Vault 2i, it tells me I have the most recent versions. I am not sure what you mean by “Is the behavior the same when you have both the endpoint + Core connected via Ethernet?”
Thanks
Michael
Hi @Michael_Yeaman,
For the Ethernet aspect, your Core and Vault 2i are currently connected on WiFi, correct? Is the behavior the same if you plug them in via the network cable (CAT5/6 cable)? Often times WiFi is more unreliable than a cabled connection, so I would like to verify this.
Noris
Unfortunately my PC and Vault are in different areas of my home and are not connectable by network cable. Is true that Roon will only work on devices that are connected by cable? I am currently connected by 2.4G WiFi, I might be able to get a 5G connection if a added an extender, but it seems rather hard to beleive that Roon would not work with a WiFi network. Your thoughts?
Thanks
Michael
Hi @Michael_Yeaman,
No, this is not the case. While Roon may work over WiFi, the most stable way to connect your devices are via Ethernet cable.
If you want, we can take a look at logs when this issue occurs next and see if there’s more clues that way. Can you please note the exact local time + date + track you experience this behavior next on?
After, please send me your Roon logs by following these instructions and your BlueSound logs by using these instructions:
Navigate to Bluesound’s IP Address in a web browser -> Diagnostics -> More -> Copy+ paste the text into a text editor.
Once you have both log sets, please send them as a shared Dropbox / Google Drive / Send.firefox.com link and I can take a look
Noris
I followed your instructions and sent you a Dropbox link with the requested Roon and Blusound logs. I noticed the dropout event at about 2:45 local time.
Thanks again for your help.
Michael
Hi @Michael_Yeaman,
Where did you send the link? I’m not seeing any new messages from you on my end.
Can you please click my name on this forum, press “message” and send it there?
Thanks!
Hi @Michael_Yeaman,
Thanks again for sending those logs over. I have spoke to the technical team regarding your logs and it appears that Roon is operating as expected, but your Bluesound Vault 2i endpoint itself is experiencing the audio drop-outs.
The relevant traces from the Roon logs are as follows:
02/18 14:46:52 Trace: [HOME VAULT 2i - 5E9A8] [Lossless, 16/44 FLAC => 16/44] [100% buf] [PLAYING @ 9:57/32:54] Two2, for two pianos (indeterminate) - Edmund Niemann / Double Edge
02/18 14:46:52 Debug: [raat/tcpaudiosource] disconnecting
02/18 14:46:52 Warn: [raat/tcpaudiosource] send failed: Object reference not set to an instance of an object.
02/18 14:46:52 Warn: [raat/tcpaudiosource] disconnecting + retrying
02/18 14:46:52 Warn: [zoneplayer/raat] Error during streaming: System.Exception: serverside buffer overrun
at Sooloos.Broker.Transport.RaatTcpAudioSource.SendFrames(IPEndPoint ep, Int32 stream_id, Int64 streamsample, Double buffersize, StreamFormat format, Double gain, Double peak, Byte[] buf, Int32 nsamples)
at Sooloos.Broker.Transport.RaatZonePlayer.<>c__DisplayClass31_0.<_StartStream4>b__1()
02/18 14:46:52 Warn: Track Stopped Due to Error
02/18 14:46:52 Info: [zone HOME VAULT 2i - 5E9A8] OnPlayFeedback StoppedEndOfMediaUnnatural
On the Bluesound log side, we are seeing the dropouts logged as such:
Feb 18 22:46:57 (none) user.info ./ms.pl: Controller::resumeRaat Controller.pm (1777) resumeRaat
Feb 18 22:46:57 (none) user.info dspout: Command(l=48): R66017186
Feb 18 22:46:57 (none) user.info dspout: raat_start(uncorrected, REALTIME) 1582066017400450731 ns
Feb 18 22:46:57 (none) user.info dspout: Command(l=5): I5000
Feb 18 22:46:59 (none) user.info dspout: [warning] dropout of 100 samples at 105000 [2]
Feb 18 22:46:59 (none) user.info dspout: [warning] dropout of 441 samples at 105100 [2]
Feb 18 22:46:59 (none) user.info dspout: [warning] dropout of 441 samples at 105541 [2]
Feb 18 22:46:59 (none) user.info dspout: [warning] dropout of 441 samples at 105982 [2]
Feb 18 22:46:59 (none) user.info dspout: [warning] dropout of 441 samples at 106423 [2]
Feb 18 22:46:59 (none) user.info dspout: [warning] dropout of 441 samples at 106864 [2]
Feb 18 22:46:59 (none) user.info dspout: [warning] dropout of 441 samples at 107305 [2]
Feb 18 22:46:59 (none) user.info dspout: [warning] dropout of 441 samples at 107746 [2]
Feb 18 22:46:59 (none) user.info dspout: [warning] dropout of 441 samples at 108187 [2]
As for the follow-up step, I would suggest you reach out directly to Bluesound support and provide them the above traces I quoted, as well as the full Bluesound log which you also sent me. Thank you.
Problem Solved!
Well after all this effort, it did just boil down to establishing an ethernet link between my PC (which hosts the Roon Core) and my network Blusound Vault 2i. Once this was created I have had no dropouts and Roon has performed perfectly. Spread the word, this appears to be the solution to systems that try an rely on wireless connections between the Core and Music Servers.
1 Like
Hi @Michael_Yeaman,
Glad to hear you’ve been able to resolve this behavior with an Ethernet link for your Core/Vault.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.