And so it goes in the world of software. Guess things are better in a closed software world. Pretty tough to keep it 100% closed though: Tidal/Qobuz…
@fdemello exactly! Here is a similar issue, only there is no network involved… so to continuous blame this on my network is getting old (from all sides, including Roon)… Moreover, I have had far, far, far fewer problems steaming with MConnet… That said, there has been a handful of times in the past 48 hours of continuous streaming where I got a “Renderer has stopped responding” error… but one can expect an interruption or two over several hours… not one or two every half hour.
@Paul … Paul, I am totally inclined to believe PS Audio on this, but I guess my (and @fdemello) point is, what role does PS Audio play in helping resolve this issue by working with the folks at Roon? Surely, you guys have an “industry insider” or “back channel” contact with their technical people and can have a conversation about why this might be happening? IF you look at the Roon support forums, it’s not just the two of us…there are others. You should ask one of your people to talk to their people about fixing this for both of your customers sake… Roon doesn’t seem to be having this problem with most Streamers, so there is something unique to how it’s interfacing with Bridge that’s causing this… maybe they need to a test unit to play around with at their offices?
1 Like
@Serhan they make MConnect, right? Do they also make Bridge II? confused now.
The Bridge II and Mconnect come from ConversDigital. They may be old, But network errors can be difficult to identify. The other thing that can cause this error are background , processes in ROON and an underpowered core. You need to prevent any of the unnecessary ones from running. If your core doesn’t have enough power, failures Ike these occur. The ROON forum can help. Once it’s sorted out ROON can be rock solid. Mine has been running for years with an odd restart required.
@watchdog507 not a network issue, as I’ve stated a half dozen times, but thanks for the input… As to underpowered core… if a 2019 MacBook Pro 2.9Ghz i9 isn’t enough power, what is?
Are you running it with the DS with Bridge II? And what are you using for a core?
1 Like
Let me start by saying that Roon is probably having issues with DHCP protocols over the network. As for the South Korean company, Converse Digital, they seem to be an OEM hardware provider of components that go into various devices. MConnect comes in a free version that works with devices that have their components, and a paid version which is almost the same as the free one but can stream videos as well. Bridge II works with both the free and the paid versions.
Being a current owner of two Naim Uniti multi-room streamers and two Naim servers, by comparison with Naim proprietary software application, I find MConnect quite anaemic for an otherwise magnificent product, i.e. Bridge II. But it does a great job with Qobuz and Tidal MQA. I use it for streaming DSD 64 via the LAN and it reads from all servers around the house without issues. However, I find it convenient to play directly from Naim Uniti Core into DIrectStream DAC using AQ Coffee cable recommended by Paul and that sounds great.
I wrote converse digital two times to suggest improvements. To start with, they need to merge the portrait and landscape versions into a single version.
1 Like
How do you KNOW this to be true? Your basis for this certainty may help with troubleshooting.
[Asked with all due respect/not intended to be provacotive.]
FWIW.
[Edit/PS: My limited experience in this regard has been related to network interruptions and computer/modem/router “handshake” interruptions or power saving functions.]
1 Like
a) The guy above (@fdemello) who is having the identical issue with a HARDWIRE setup is having the issue
b) MConnect over the SAME network isn’t having the issue
c) I did a “ping” (still am) that I posted above as a screen shot for the card via my unix terminal on my laptop and the speeds/latency were VERY much inside the parameters for a high speed network.
Thoughts?
Three comments, FWIW:
- I am far from qualified when it comes to technical issues related to IT information systems;
- That said, IME the speed, capabilities, measured performance of the network (i.e, technical specifications like how fast it runs, latency, etc.) are not usually an issue. Rather, the occurrence of “disconnections” or interruptions in the delivery of data and something I (probably, ignorantly) call loss of equipment “handshakes” have been an issue; and
- Mconnect/Mcontrol is really buggy (IME, terrible) control software. I abandoned it due to UI preferences and buggy performance issues a long time ago.
I hope this helps some.
By the way, RE: MConnect for future reference – make sure the control application you are using is “mconnectControl”. There is a variant out there that is the wrong application for use with the PS Audio Network Bridge cards. I have version 2.4.24 on my iPhone and it works, when it works. 
One more thought in closing – EVERYTHING seems to matter when it comes to network audio. So, if you have not done so already, please lay out your signal path in some detail (in terms of all of the different equipment handling and transferring your Ethernet AND Wi-Fi signal) for the forum denizens. Someone smarter than me may be able to identify “the fly in your ointment”.
Good luck.
1 Like
well as an update… Roon tech support had me completely uninstall Roon from my Mac… we deleted all sorts of other files that were in various folders… re-installed it.
Guess what? It’s been streaming uninterrupted now for 9 hours… with the SAME network… the issue was software as I’ve been saying… there seems to be a corruption that occurs sometimes and I was victim. That said, he said they’re working on an update that prevents this from happening.
Worth a try for those who are experiencing similar symptoms.
4 Likes
Glad they were able to fix the issue for you. I know nothing about Apple computers but it still had to be network related as the network is being used to play the music and transfer playback commands back and forth. Dang computers anyway.
It’s a good question. Normally the way this works is folks with such a problem will contact us or Roon directly and our customer service department (or theirs) goes to work to try and narrow the problem down to a system level or a product level. If, for example, we found a repeatable trend between Roon and the Bridge, or we were able to duplicate the problem, we can then get engineering involved and that may escalate to where we need to work with the engineers at Roon. But that’s rare because most problems in streaming tend to be specific to user circumstances.
The fact that Roon keeps stopping is more of a Roon issue not a Bridge issue. My suggestion is to reach out directly to Roon’s customer service department. They’re good and usually can help. Maybe they will have you uninstall and reinstall the software, or find a software toggle. It’s always more complicated when marrying 3d party software to hardware.
The problem you’re experiencing is not one we see very often and to my knowledge isn’t something we’ve been able to duplicate. So, a few instances like this are more easily handled on a case by case basis. I would encourage you to reach out to Roon first and then us if that doesn’t work. If we can duplicate it and there is an actual problem specific to Roon and the Bridge, then we can and will work directly with Roon to fix it.
1 Like
Yes, thank you. This is what I have been trying to express in my bumbling way. Roon is the server. If it stops playing or stutters there’s likely something going on in the server itself. It’s a computer. Sometimes you need to take drastic measures like this.
Network problems are common though rarely because of bandwidth with most modern LAN.
2 Likes
Oh boy, what a relief! Thanks for keeping us in the loop and I hope it keeps on truckin’.
Hey @Paul - since you’re on the topic of Roon, do you have any updates you can share regarding the status of Roon integration in the Octave Player?? I feel like I’ve read a couple of opinions from you on the topic earlier in the year, but none were firm decisions.