If you have the needed amount of RAM and you are OK with a bit of extra boot delay, it is fine. I use it too on my UP Gateway. Since it doesn’t have easily accessible proper power button to start/stop the system nicely, and it is running 24/7/365.
The storage used to boot it up doesn’t affect the choice of image.
I’m not sure what you are referring to here?
It is not very useful, but you can login as “root” if you want to, there’s no password.
Then you would likely want to use the regular NAA OS image instead. Since it has now (IIRC) has ssh server included. You just need to create a user account and set password for it to be able to remotely login.
Not included on ramfs version, since any such things would get lost on every reboot.
Yes, seems to be. And that’s how I expected it to be, since the 44.1k is mentioned first = 0 and 48k is mentioned second = 1. But maybe it’s just my programmer’s logic…
For my click/plop problems when changing the frequency of songs, I put “Adaptive rate” in gray instead of checked in output. There seems to be a lot less of this click/plop phenomenon.
With “Adaptive rate” checked:
44.1 and multiples => DSD256
48 and multiples => DSD256x48
With “Adaptive rate” grayed out:
44.1 and multiples => DSD256x48
48 and multiples => DSD256x48
I would tend to think that 1) is better in terms of frequencies, but I don’t hear any particular difference when listening between 1) and 2)
Do you’ve also tested the automatical input switching? Is this working without problems?
I’m thinking to buy a further Holo Audio DAC (very satisfied with my May, but here I’ve a remote) for my bedroom.
Haven’t tried because I would only feed this with DSD256 via USB.
From what i read from other users, you need to physically unplug USB for it to ‘automatically’ switch to another input.
A nice ‘feature’ to keep the price down ! No complaints from me
I would have Cyan2 direct USB connected to my Mac Mini. There is no ‘noise’ I measured from the Mac to the DAC output, even with Chrome browser playing 4K video.
Cyan2’s USB input is top notch clean as a whistle.
Basically the gear to do all the measurements I’ve shown - is good to do a QA/QC check.
This is exactly how I found the bug at DSD512 with SMSL D-6 which SMSL fixed.
The “how to do this” has taken me a couple years to reach the point where I can be confident to publish measurements knowing they are reasonably accurate. Like if @GoldenSound decides to measure Cyan2, I’m confident they’ll be like mine (if he actually measures properly at DSD256 of course, not in NOS mode). The links below are a great resource as well as ASR forum to ask for help. It would take me hours to write.
But ideally you need a measurement laptop running Room EQ Wizard and Multitone Analyzer and this:
Due to the NOS focus, Holo has such 50 kHz fc (-3 dB point). If you like wider bandwidth, T+A gives you option to choose between two analog filters. A 60 kHz one and a “wide” one. Of course the price is pretty different, which is also affected by the Made in Germany aspect.
I believe you recommend putting the DSD filter at 50 Hz for DSD 256.
The RME ADI2 documentation indicates instead to use 150 Hz for DSD 256 (and 128), and 50 Hz for DSD 64.
Ultimately what is preferable?
