No biggie, I missed that note by Vincent in the manual. I do wonder why he would put that in there as I have not had any issues when sample rate changes. I did have to use this setting with the Chord M-Scaler as it has a slight delay due the processing of the incoming signal.
Not to derail this, not a fan of the internal streamer on the totaldac which I am using with the USB Gigafilter cable. Feel the AES is a better input for the totaldac so far.
I use it with a small value (500ms I think) to fix chain delays when switching bitrates. I would sometimes hear the song after it really started and this fixed it.
That’s interesting because it’s the same card that he uses on the d1-streamer afaik. This was the reason I had gotten the unity with the streamer as he had said I could get it moved into the d1-streamer later and he would take that off the price. Perhaps it sounds better with the clocks as a package.
Yeah same card, plus the d1-reclocker mkii and the USB Gigafilter. Plus a separate Live Power PSU and there is some extra isolation inside that box I think?
Nah, its cool. I really appreciate this, but don’t worry about it. I talked to another Mojo Evo owner already and Ben does utilize older DAC chips from time to time. I am not too sure what DAC chip I have in my B4B 21, but it probably have some compatibility issues with probably newer products. The AES port never worked perfectly with my NS1 streamer to B4B 21 DAC (it worked perfectly with teh basic Evo). I used a Silver Sonic AES cable and I had to upsample to 176.4 kHz get it working. With the Boomslang, its the opposite, I had to downsample to 44.1 kHz. It’s not really an issue for me at the moment. I already have my eye on a certain CD transport late 2024, so I am not really too bother with the AES port on the my Mystique Evo.
Also, I will say that I never had issues at all with my previous Mystique Evo Basic, so its probably the DAC Ben uses in the 2021 model Mystique Evo or maybe just my specific one I gotten. I have gotten report on other owners that the AES works on certain streamers, but just doesn’t get along with another streamer they were using. It’s probably the same case scenario for me. Best thing to do is really just get a DDC and a good spdif cable or just wait for this certain CD transport to show up and I will scoop that up. Either way, I think I am going to be moving to spdif, but that’s a whatever process (down the priority list) because I already trying to think of the next upgrade path I am trying to take. So before buying any cables, gotta make sure what I am going to do is what I stay with the next 5 years lol.
Again, I really appreciate the concern, but its working now and I am happy with the new cable and results I am getting from my audio chain.
If I have two internal SSDs with music on them but no room in my Roon ROCK to connect them, what’s the recommended way to still get them part of the library?
You should be able to use them externally either directly connected via USB or if you put the drives on a NAS, then point ROCK to the network destination if you’re using a NAS or it should see it as an external drive if connected directly via USB. Here’s where you’d configure it all. Multiple drives, just add folder and the path.
A rock is just a Linux server, running a streamlined version of Linux and Roon Server.
You have basically 3 options.
As db_cooper states
Stick them in a NAS, and point at the share.
Attach them via USB.
And the final option is to buy a bigger case, and move everything into that.
I’ll take what costs mo’ money for $400 Alec.
Finally!!! I just upped to AT&T Fiber (1gig speed up and down) and Roon Arc started working beautifully. I have fought with this for a long time and as soon as I upgraded it just worked !!. Happy camper here now!!
ROON is getting on my last nerve, months ago i started having issues playing more than a few songs in a row. The core would simply disappear and i would have to back out of the app, or sometimes power down and restart the core. All this would be repeated once every 4-5 songs. I waited for an update hoping this would fix things…
Months later it has gotten worse, we are down to an average of 2 songs before the core simply disappears and I have to try clear the cache, power down the controller, the tablet, the core, the NAS, shit the whole system has to get powered down sometimes to reconnect for another 2 or 3 songs.
Unless my ROON core computer has simply outlived it’s life my desktop and HP system are basically inoperable currently, i’m stumped and out of ideas.
If i were not so computer inept i don’t think i would be this frustrated, i can’t find anyone else with the same issues as me so i am almost 100% sure it has to be something wrong with one of my computers.
That is all, i needed to vent 
i just don’t know what to do next you can’t just call someone and the ROON forum people ask for info i don’t know how to provide.
There’s a bad memory leak in the current server, you have to comb the forums to find the thread, I can run for a couple of days before it shits the bed, but my server has 32GB’s of RAM.
They are supposed to have a fix, but they don’t appear to have actually released it.
Why I have no idea, but it’s unacceptable.
I am so happy i finally spoke up, i felt like a moron, i searched and searched multiple times over and was not stumbling across anyone who had a consistent problem like me. Thank you @Polygonhell for speaking up 
Do you know if it effects both server and ROCK? Or just server?
I would assume rock is running server.
It’s both Linux and windows affected, as I understand it, it’s not strictly a leak, it’s a combination of the GC policy settings, and probably not disposing of some limited resource.
It’s been going on for over a month.
My server gets spotty, I load up task manager, and it’s using 20+GB’s. With less memory, I’d guess the machine would become unusable, for a while eventually server would probably crash and restart.
Restart the server and it’s magically back to working again.
1311 is the bad one, but it doesn’t seem to effect everyone, and one of the fixes was an OS configuration.
There was a version after 1311 which is supposed to have a fix but, they removed the update because it was broken.
The last post on the issue thread is from roon support 5 days ago, with the usual still looking at it.
Seriously @Polygonhell thank you for the info. Knowing there is hope and the problem is not anything particular to my equipment has much calmed me, i was getting ready to either figure out UPNP protocol to try and get my SOTM to act as an Innuos Sense endpoint and also getting ready to contact my dealer for a 3rd innuos streamer 
which in all seriousness i would rather avoid.
Looks like the fix is starting to roll out:
fwiw, in my case it was solved by updating the firmware on my SOtM Ultra Neo to the latest
