· I bought a Vitus RI-101 MK1 with their steamer module in January 2020. At the same time I purchased a lifetime subscription to Roon. The Core was installed on a PC in my house. The Core recognised the RI 101 and all worked well.
Earlier this month the PC on which the Core was located needs a major repair / replacement.
Instead of installing the core on a new PC, I decided to purchase a Nucleus One.
The benefit is that I would not need to turn on the PC to have access to Roon.
The problem is that the Nucleus One does not allow me to connect with the Mk1 streamer other than through AirPlay. Apparently Roon have revoked the ability for devices such as the old Vitus streamer to be used with Roon software, despite this being available to me when I made my initial purchase.
The quality through AirPlay is significantly inferior and unacceptable.
So I now have a Nucleus One which is of no use to me and I have to revert back to the Core in my old PC which does allow access to the Vitus streamer in high quality.
I had no idea that I would not be able to use my streaming facility via the Nucleus One.
Do I attempt to return the Nucleus One or can you offer a no cost solution to allow me to listen to my MK1 streamer via the Core in the Nucleus One?
Having a lifetime subscription leaves me at your mercy, but I could either be a very happy customer and tell all my friends about the benefits of Roon and their understanding of customer issues, or I could be a very disgruntled customer.
Thank you for taking the time to explain your situation in detail — I understand how frustrating this experience is, especially given your long history with Roon and a lifetime subscription.
At the moment, we’d like to double-check this internally with our team to fully understand the behavior you’re seeing with the Vitus RI-101 MK1 streamer when used with Nucleus One. As far as I see from the internal information, this device was never certified as Roon Ready
Once we have clarity from the internal teams, we’ll come back to you with a definitive answer and next steps.
Thank you for your patience — we’ll follow up as soon as we have more information to share.
Thank you for your patience. One item for due diligence as we sort this out behind the scenes: these two RoonServer machines are using the same Roon account, correct? Did you migrate your server between them or create a fresh database on the second machine?
· I raised a question on 8th February about my Vitus working on Roon core in a PC for the last 6 years + but not working on a Nucleus One I recently bought. I was told that my problem was being considered behind the scenes, but then I was advised that t support thread was closed because there had been no activity for a week. I am still waiting an answer please!
They will reopen the old thread when they have something to announce. However, the last thing in the old thread was a question you didn’t answer. I suppose this would be helpful if you told them:
Thank you for your patience while our hardware partner team investigated the history of the Vitus RI-101 MK1.
I completely understand your frustration. It is incredibly disappointing to invest in a dedicated Roon server like the Nucleus One, only to find that your high-end streamer is no longer connecting at its full, high-resolution potential.
Here is exactly what we found:
The reality is that the Vitus RI-101 MK1 has never been officially certified as a Roon Ready device (though the MK2 version is fully certified). Sometimes allowed uncertified network devices to connect via our RAAT protocol through technical loopholes or unofficial workarounds.
As Roon’s architecture has evolved over the years to enforce strict performance, synchronization, and network standards, those loopholes were closed. Because your new Nucleus One is running the latest, most strictly managed Roon OS, it enforces these official certification rules. This is why it is defaulting your MK1 to the next available standard protocol, which is AirPlay.
Please know that Roon did not maliciously revoke access for your specific device; rather, your MK1 was operating on an uncertified workaround that is simply no longer compatible with our current, updated infrastructure.
How to move forward: Because Roon cannot write integration code for third-party hardware, the ball is in the manufacturer’s court. We strongly recommend reaching out to Vitus Audio directly. Please ask them to work with Roon to officially certify the MK1 streamer module, or provide a firmware update that brings it into compliance.
Vadim. I think you know full well the response from Vitus.
As you are well aware, your answer does not provide a solution.
My only realistic option is to return the Nucleus One and require a full refund.
The Roon Core worked perfectly with the Mk1 Vitus when it was purchased.
I would not have bought Roon software if it did not.
However, Roon has changed how the software works and Roon have created this problem. That is why I expecting Roon to provide a solution.
All I have left is a brand new and useless Nucleus One and, if you don’t provide a solution to me a determination to influence as many of my friends from buying Roon software, especially life contracts.
Please either provide a solution to the problem that Roon has created, permit the Nucleus One to be returned for a full refund and/or to refund my subscription to Roon.
Please do not blame Vitus. They have not changed anything.