Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: [TOS #8 + misinformation] From: Patched foo_input_sacd version for hig (Read 2072 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[TOS #8 + misinformation] From: Patched foo_input_sacd version for hig

I compared all the various DSD->PCM algorithms in the regular foo_input_sacd and then compared what I felt was the best sounding algorithm to this HQ mod and I also found that this HQ mod sounds better.  It's subtle and you need audiophile equipment to hear the difference.

Since the whole point of SACD is these subtle improvements, I'm now using this HQ mod instead of the regular version. So, thanks for posting it here !

By the way, why did you remove the option to add gain digitally ?  Isn't that transparent since it is done in the digital domain ?  Without it, the DSD->PCM output is always lower than other music files.

[TOS #8 + misinformation] From: Patched foo_input_sacd version for hig

Reply #1
Echo AudioFire drivers don't support WASAPI

False. I've been using AudioFire2 with WASAPI for years. Echo drivers have excellent WASAPI support.

[TOS #8 + misinformation] From: Patched foo_input_sacd version for hig

Reply #2
Echo AudioFire drivers don't support WASAPI

False. I've been using AudioFire2 with WASAPI for years. Echo drivers have excellent WASAPI support.

Just FYI, if you do a web search on WASAPI, you'll see that the "perfect sound forever"-style claims for the theory did not actually correspond to the actual implementation (which, of course, is true for just about everything).
What actually sounds better depends on other specifics of the individual implementation.