It’s IT speak and it’s a barrier to common sense operation, and a way of generating traffic on support forums.
The other lesson learned here is that once you have a stable Roon environment a backup is required but even that will probably fail without the appropriate apk file (for Android) or equivalent for IOS.
I understand the frustration, but I feel that Roon have just never got around to updating the wording on this. I don’t think they enjoy reading these post’s, but they could certainly make it easier for the average user to understand.
Personally I have never kept an APK beyond old Android beta versions and then quickly got rid of them. On iOS this is not really possible at all.
Many of us have discussed the possibility of a slow ring release for Roon, but the closest thing to it now is legacy 1.8 release and while that has its fans, it is now way out of date.
I gave my Roon Rock NUC a period of 24 hours after re-installing the original version 258 and then having to update to build 261. Server version is now build 1442. Upsampling to DSD512 is still broken and unusable. DSD256 seems OK. My previous config before the upgrade worked fine and I cannot rollback. Where next? The NUC has the following spec and is on Roon’s list of compatible NUC’s:
I know it’s over specced but if I ever decided to throw Roon in the bin the computer could be used for something else instead. And at this point the bin is ready and waiting.
What are your DSD settings in the Sample Rate conversion screen, and do you want to share a screenshot of it.
You might want to try tweaking the settings to 5th order converter, Enable parallel conversion and this might well help.
Also is it possible that you had an update on the Auralic that might be causing some issue as well. My ears cannot really notice any difference between DSD256 and DSD512, but it is always annoying to lose something you have previously had
I’ve had no updates on the Auralic and the Roon settings are the same the settings before Roon updated and was working. Roon should provide a way of rolling back if the users are going to be treated as testers.
Thanks for taking the time to write in and share your report.
I’d suggest sharing any feedback or feature suggestions over in our Feature Suggestions to ensure the right eyes see your comments.
In regards to your issue, we were able to review a recent diagnostic report, and see some additional DSP taking place during playback when you’re hearing the distortion.
Could you please disable all other DSP outside of your upsampling, and see if the issue returns? If it does, share the track name when you experience the distortion.
Thanks for the follow-up! You have my apologies in that the additional DSP recognized was intentional, so we can move on.
As a next step, could you please upload a few of the DSD512 tracks you’re having issues with? Out team would like to attempt to reproduce in house. Upload via this link.
In addition to this, could you perform a firmware reinstall on the Aries device?
Lastly, and my apologies if I’ve missed this mentioned prior - are you able to play DSD512 files with your setup when using a different media player outside of Roon?
What if you cut out the Auralic from the chain and try something different.
If you have a Windows PC you could load the T+A drivers (if needed) and Roonbridge and see if that combination works better directly connected to the T+A.
2 x USB DAC: Device-Mode 44,1 … 768 kSps (PCM) and up to DSD1024*, supports asynchronous data transfer. *DSD 512 and DSD 1024 with Windows PC and appropriate driver installed
Edit: @benjamin sorry we seem to have cross posted.
Please keep this open. I am currently dealing with some turntable and loudspeaker issues but should be able to respond to your requests at the weekend. One thing. I cannot reload firmware on the Aries and the Aries needs to stay in the audio chain. I’d prefer to stop using Roon if a choice had to be made.
Looks like it’s an issue with the streamer. I have been able to play a native DSD file on the SSD and I get the same problem. Don’t believe it’s the DAC but checking with the manufacturer. Please close the ticket.