Since version 2.2 we have introduced new System Modes which allow to choose between different ways to use the system, namely:
* Roon Core
* innuOS (Squeezelite)
* Roon Bridge
* HQ Player
When set in Endpoint Mode, we have turned off a lot of the library functions on the system so that the server runs as a playback engine as efficiently as possible. The assumption was that if there was another server doing the Music Library Management role, then that server should have the storage connected to it directly and have the necessary management functions. After all, if a system is used as an endpoint but also as storage with an external server as the music library, this means each track will need to be sent over the network from the Innuos server to the music library engine and then back to the Innuos Server for playback, which uses a lot of network bandwidth affecting performance in both sound quality and user experience.
However, we did have a number of users reporting they would indeed prefer to use their Innuos Music Server in Endpoint mode but with access to the Shared Folders as well as the storage management features such as CD Ripping, Backup and Import. If you do want this possibility then please vote in this feature request and if there is indeed a reasonable number of users requesting it we will consider to re-enable this on a future update.
thanX so much. i must say, in my decades of listening , i’ve come to realize that the proof is in the listening. i know there were other changes in 2.2. when i get 2.2.3, i will, mos’ def’, listen again in both end point and standalone mode. you know, how businesses solve customer issues is the premier criterion for judging customer service. in this regard, you have succeeded wildly. huge kudos to you and many, many thanX!!!
Let me start by saying that yes, we will prepare a 2.2.3 update that we will launch in the next couple days that will re-enable network sharing and CD Ripping / Import / Backup when in endpoint mode.
Having said this, let's take some time to discuss why this was done. When you are using the Innuos Server as storage and then as endpoint , particularly with Roon, you are adding an extraordinary amount of network traffic to your system. This is what happens when you press play on Roon using this architecture:
1. There is a request from your mobile device to the Roon Core
2. Roon Core requests the file from the server to the Roon Core
3. Roon processes whatever DSP it needs to process and sends the processed audio back to the server for playback.
The network traffic this generates has a lot more activity on the network interfaces when playing back, which, in our opinion, does not yield the best results. I do not agree this is the best way to run Innuos Servers: We aim for simplicity in design, with shorter and more direct paths, simplifying the landscape so you don't need lots of boxes. But we are here to listen to our users and there can be many different circumstances we are not seeing. This is what the Feedback Zone is for. All in all, we have learned that when making more profound changes to the way the system work, it will be better to consult with the community and do some further due dilligence. Our apologies for not having done that.
Stay tuned for 2.2.3, will be out very soon - we will annouce it here.
Please restore this feature ASAP. This is a horrible update and disables the best way to use the Innuos servers: with a Roon Nucleus Plus and having the Innuos in endpoint mode. Please fix right away!
and, using the SSD on the statement yields the best on line performance when using an eXternal roon core i. .e. MUCH faster navigation of my library. so this is a downgrade in that sense as well.
further thought — i did a lot of research before buying a statement w 8TB SSD. i hope u agree that is a major purchase (and let’s not forget that you charge a whopping additional $3K for the SSD). once i got it, i put 6TB of music on the SSD. i did a lot of listening. i listened using your SW, i listened using the statement as a roon core, i listened w an eXternal roon core (nucleus+). using the nucleus plus is sonically superior to the other two. finally, with the nucleus plus, i listened with my music attached to the nucleus+, pointing the roon nucleus+ to the statement SSD and pointing it to another NAS. i listened both with and without a custom linear power supply on the nucleus+. my choice was definitely using the nucleus+ with LPS pointing to the statement’s SSD (i will not debate what i should or should not prefer). so, by making this change, you have, effectively, downgraded me. if you are going to force me to downgrade, you must offer a full refund as an alternative. believe me, i do not desire the latter, even a little bit. so, please, i implore you, put a little customer care thought into the decision you made. just a touch of customer care should yield a decision to undo this change. i have run many successful businesses. my golden rule always was that eXising users’/customers’ needs are the number one priority. anything else is, from my eXperience, a business’ kiss of desth.
pardon my language, but this is total bullshit. i choose to use it the way i paid for it. you can’t just take a function away from me after i’ve been using it this way for quite some time. this is not a matter of voting. i bought a unit for $18,000. you cannot simply render features unusable after the fact. either give me my functionality back or give me my money back!!!! NOW, please.