Here’s a new feedback today. He shared his feedback after receiving Fidelizer Pro license as below.
Hi, Fidelizer product works over the top. A+++ Many thanks.
I’m happy to hear that Fidelizer Pro is working well in his system and happy listening. 🙂
Here’s another feedback today. He shared his feedback after receiving Fidelizer Pro 8 years ago.
Works great! Thank you so much for your program. It’s so nice! 🙂 Everything sounds so new and dynamic!!
After launching Fidelizer 8, there was a lot of testimonials that I didn’t have time to add back then and I’ll start adding more now. 🙂
Here’s a new feedback today. He shared his feedback after receiving Fidelizer Pro as below.
I was right trusting in you ! I was hesitating since some months but friends of mine encouraged me. They were wright: My server sounds even smoother less aggressive.
I’m glad to hear that his trust wasn’t misplaced and also thanks to his friend’s recommendation too. 🙂

After Roon 1.8 update, Fidelizer starts developing unique Roon optimization for Fidelizer Nimitra as Roon core and things have been going well so far. There’s some sound signature changes during Roon 2.0 updates but still sound acceptable for serious listening.
However, Roon 2.0 starts adopting CarPlay support in recent updates and some audiophiles feel they can’t enjoy music from Roon as they used based on feedback received from customers and friends asking me if I notice changes in sound with recent Roon update.
I investigated and tested different 2.0 builds and found that Roon 2.0 build 1182 sounds more preferable as the last build before CarPlay support. I shared my findings in Roon’s community hoping devs can test things out but my feedback wasn’t well received.
It looks like Roon 2.0 will focus on adopting more features to provide more accessibility such as Roon ARC and CarPlay and those changes may cause sound signature changes in some systems over time. For audiophiles using Roon solely for serious stereo system, this isn’t good news.
So, I went back to Roon 1.8 Legacy and start fresh since Roon’s database can’t be downgraded from 2.0 to 1.8 release. To my findings, it sounds decent, get the jobs done and I won’t have to worry about new updates causing change in sound signature like Roon 2.0.
After testing Roon 1.8 Legacy today, I decided to add Roon core version in Fidelizer Nimitra Computer Audio Server with Roon 1.8 Legacy as default option. You can also upgrade to 2.0 at any time from backup and Roon 2.0 that can’t be downgraded.
If you’re using Fidelizer Nimitra as Roon core running version 2.0 and want to setup Roon 1.8 Legacy version, I can backup your Roon 2.0 repository and start new Roon core 1.8 legacy for you to try and see if you want to keep using Roon 1.8 Legacy version.
I’d like to assure you that Fidelizer Nimitra server is still fully compatible with Roon 2.0. This option is a matter of personal and subjective experience about sound changes in different version updates. As old saying goes “If it ain’t broke, don’t fix it”.