Hello, I tried Early Access about 1 month ago to fix another issue. But my Matrix Mini iPro 3 DAC has been playing fine until today. I did see Roon update a week-ish ago, and worked on the Sonos Speakers.
Today I tried the Matrix DAC, but Roon wouldn’t show the Matrix DAC in my Zones. I rebooted the Roon server app, still no luck. Then I restarted the machine at least 2 times trying different scenarios of killing other apps on that PC. One small correction, Roon only saw the DAC as an AirPlay device when the Zone I normally use is under “Roon Ready” (not the AirPlay instance).
The only way I got my Matrix DAC Roon Ready zone back was to roll back the 1544 Production Roon on the server. The Dac showed Immediately after that. So for now, I fixed it but I wanted to report it to ensure my future build use.
I hope this isn’t the case next week when the EA is going production. I have 2 MA devices that are Roon Ready and neither has ever given me the slightest issue with Roon
1 Like
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
3
Yes that makes myself nervous as well.
My ipro3 has been flawless since purchase.
It would really surprise me if there was an issue as it is a Room Ready device. I have never used toe 3 pro for any other protocols (excluding USB and Optical inputs which I use).
The mini-4 is a bit more flexible as it also supports Tidal Connect and UPNP so I have used that, and sometimes play through the WIIM Pro plus for Qobuz, LMS and other services.
I did not try resetting my Router. But it is more of an industrial Cisco network, and should not need to.
That being said, it all worked perfectly after rolling back 1555 to 1544 Prod. No Router or PC reboot needed after that.
Also, the Matrix was working a couple of weeks ago. I suspect that was the version before the 1555 update that was just pushed recently. I know for sure what I had this morning was 1555
Well there might be quite a few more of us shouting in a few days, so I hope this is just a one off
Though I hope you get your issue sorted out quickly
Judging by the surprising number of responses here, etc. I downloaded a fresh EA build (turned out to be 1553) and installed it in my Roon Server.
The Matrix Dac was working on 1544 Prod, and also still working after installing the EA 1553 today.
How I got the 1555? I for sure saw Roon update in the last week when I was on the EA build. I guess without a screen shot, I can’t prove I had 1555. So take that for what it is worth.
Last, maybe the “incremental auto update” built into Roon failed, and just needed a full reinstall to fix the Dac visibility? I guess we will never really know as the Prod 1544 install fixed my Dac not being seen, and going back to Beta 1553 today didn’t break it again.
There is another perspective here, it is working. I have said that in two posts above. I reported so that Roon could take a peek, not because I needed to wait for them to solve something.
You also have two tested (possibly 3) resolutions from the people that experienced issues:
Restart your router (worked for someone else)
Download the 1544 Prod build, and manually install it (worked for me)
Or possibly the 1553 EA build as it still works after going back the EA 1553
I get there are some issues in 1544 like my report of Zone lists getting too full, and Tidal playlist imports not completing. I had both before going to Beta. I want those fixed too, and I am testing them in EA.
I’ll go one step further and test the new Prod build for my Matrix Dac friends without fear. Just like I did today by going back the EA 1553 to hopefully give you some peace of mind. I have my backups, a plan, and great with computers. Just hit no on the update screen for a few more days if Roon is that critical to your day to day. That should be standard practice on critical components, don’t upgrade on day one of any release of anything. iOS, Android, Windows, Roon, anything can have issues and the tech savvy will take to the forums it it will get worked out.
Feedback is important when testing Beta/Early Access builds. That was the spirit of this thread. I won’t be as lazy next time and I’ll get screen shot proof.
Let’s see what Roon has to say when they get back online Monday. If I am the only one that reported it, then this post should be treated as an anomaly, that two people also described how to fix. That should be seen as a non-issue.
Perhaps I spoke too soon. EA build 1553 was good for a bit. I didn’t use it for a while and now it is not showing my DAC again, just the AirPlay one, which I don’t use.
Thank you for letting us know. We reviewed your logs and did notice an issue with the Matrix device, though it appears to be more network-related than tied to recent changes.
We also confirmed from the logs that you’ve been running build 1553 throughout August - there’s no evidence of build 1555 being installed.
Looks like the DAC is still a zone days later after only the initial Router reset. So that might be the preferred fix.
Still very strange that my router would need to refresh/change something depending on the version of Roon, because when I roll Roon back the unrebooted router it was also able to find the DAC again.
Bottom line, as long as I am not rebooting the router regularly to get the DAC back, once is acceptable to adapt to the new Roon version.
