Tough, people who own the IO and the Olympus together probably have a vested/biased interest in finding the IO to be superiorOut of curiosity, has anyone compared the Olympus to the IO?
Last couple days Qobuz has stopped.. Pressing play resumes music. Not sure if this is a Roon or Qobuz issue.Question for others.
I have not seen many posts on the "Roon abruptly stops playing" issue recently. Has that resolved for others?
I am relatively recent to my O and IO, but have started seeing recently (but not in the initial month) incidents where Roon is playing, but no sound comes out through my Horizon/amps.
I have been able to restore sound by going into the Roon setup -> Audio and going into the XDMI zone/device.
This i assume resets the XDMI interface, and sound comes back. Is this similar at all to what others have experienced?
The sound from my O and I/O has otherwise been superlative and truly paradigm changing for me, like others have posted. I will add more subjective impressions this weekend.
Out of curiosity, has anyone compared the Olympus to the IO?
I don't grasp this, or understand. Could someone or Ray break this down for the limited capacity minded such as myself...Thanks in advance...EDIT The Olympus with and without the IO??This is on my list to do a deep dive on. Waiting for some pieces to dig in, but even with only the NIC in the I/O there is a significant uplift (take the uplift one gets from the Taiko network stack and jack it up another 50%) With the NIC in the I/O, the sensitivity of the Taiko network stack to energizing power is less (vs NIC being in Olympus), but still significant.
XDMI Analog impact TBD here
AHH okay much clearer...Thank you Ray...Sorry, that's what I get for posting while I'm supposed to be in a work meeting
* My base line is the Olympus server with XDMI Analog card, and the full Taiko network stack
* I currently have an I/O, but for reasons, only the Taiko NIC is in the I/O (my XDMI analog card is still in my Olympus server)
* Because of this, I can evaluate the impact of moving the Taiko NIC from the Olympus server to the Olympus I/O
TL;DR - impact of NIC moving from Olympus server to the I/O is significant here. If I take what I'm hearing as I add better power to the Taiko network stack (DCD, router, switch), the impact of moving the NIC to the I/O is a huge uplift (the 50% qualitative guess I had above)
Interestingly, I still hear significant differences between different power supplies on the Taiko network stack, even with the NIC in the I/O. It is less impactful than when the NIC was in the Olympus server, but still there (the I/O doesn't take away the benefit of the Taiko network stack and top power to it)
I have a bunch of business travel over the next several weeks, but looking forward to moving the XDMI analog card from the Olympus server to Olympus I/O next, and hearing what difference that makes here.
Still happens for me with both Qobuz and NAS files on my local network. Usually it's that the Play bar just stops entirely and I have to reinitiate Play to get music - - simple, and frustrating. However, sometimes the Play bar shows things moving along, but I have no sound, and it takes extreme fiddling to get sound again (like stopping and going back a couple of tracks and restarting, or simply deleting the queue and refilling). It's pretty annoying! Just to note, I've been listening with the internal DAC daughter card for some time now.Question for others.
I have not seen many posts on the "Roon abruptly stops playing" issue recently. Has that resolved for others?
I am relatively recent to my O and IO, but have started seeing recently (but not in the initial month) incidents where Roon is playing, but no sound comes out through my Horizon/amps.
I have been able to restore sound by going into the Roon setup -> Audio and going into the XDMI zone/device.
This i assume resets the XDMI interface, and sound comes back. Is this similar at all to what others have experienced?
The sound from my O and I/O has otherwise been superlative and truly paradigm changing for me, like others have posted. I will add more subjective impressions this weekend.
Tough, people who own the IO and the Olympus together probably have a vested/biased interest in finding the IO to be superior
It's not trivial to move the XDMI card around either. So quite a bit of energy barrier to do so.
Exciting! This got me thinking ... could this new Taiko LPS be the ultimate power source for the Olympus DC / Router / Switch combo?One highlight: we’ve developed a linear power supply capable of 20A current that sounds just as good—if not better—than 1A supplies. It’s versatile enough to power an entire network stack, NAS included, and will be a core part of the upcoming Extreme upgrades.
Exciting! This got me thinking ... could this new Taiko LPS be the ultimate power source for the Olympus DC / Router / Switch combo?
I might have missed this, but have you been able to compare the analog card to your Lampi with XDMI daugher board?Yes. From what I am being told it will take a while for the analog card to settle down. Once it does I will share my impressions.
Great to know - thank you Emile. I just needed to know that this was in line with what some others were experiencing and not a outlier with my need to "reset" it via audio settings. Since this is the case I'm happy to live with this minor inconvenience knowing your team has it on the timeline to be worked on. Just didn't want it to be a sign of any other underlying hardware issues particular to my system.Update on RAAT/XDMI Dropouts
We know some of you have been running into occasional RAAT (Roon Advanced Audio Transport) dropouts on the XDMI zone. At the moment, about 15 registered users are affected, with frequency ranging from once every few hours to once every few days. For some, it’s tied to certain Roon builds, for others it happens in every build. In most cases it only appears with Qobuz, but some have also seen it with Tidal or even local/NAS playback.
What actually happens is that RAAT temporarily “loses” the XDMI zone. Most of the time it reconnects within milliseconds, so all you notice is a pause. In a smaller number of cases it won’t reconnect automatically, a quick “reset” via the audio or zone settings gets it going again.
We’re working on this from two angles:
- Avoiding the drop — adjusting what RAAT sees so it doesn’t think the link is gone.
- Finding the root cause — since it only affects about 10% of systems, the most likely culprit is something network-related.
We could take a “quick fix” approach by throttling the XDMI transport protocol to be more like USB bulk transfer, but that would be a step backwards for audio performance. So we’re focused on a proper solution.
Right now, most of our in-house resources are going into completing the remaining Olympus orders. Additional external engineering help is lined up and will join the investigation after the summer holiday period.
We’re committed to getting this fixed the right way, and we appreciate everyone who’s shared feedback and logs, it’s making a difference.
Great to know - thank you Emile. I just needed to know that this was in line with what some others were experiencing and not a outlier with my need to "reset" it via audio settings. Since this is the case I'm happy to live with this minor inconvenience knowing your team has it on the timeline to be worked on. Just didn't want it to be a sign of any other underlying hardware issues particular to my system.
Thanks! I'd offer to send logs but i can't find a good way to do it now we don't have access to the underlying OS via VNC.
Hi Vassil, thanks - already done, #3714Can you please open a ticket with support if you haven't done so yet?
| Steve Williams Site Founder | Site Owner | Administrator | Ron Resnick Site Owner | Administrator | Julian (The Fixer) Website Build | Marketing Managersing |