Settings: s/pdif as default device supported formats DTS and Dolby digital sample rates 48 & 96 enhancements off advanced->default format 2 channel 16/32->16/192 & 24/44.1->24/192
BEST BITPERFECT SETTINGS FOR ODAC WINDOWS 10
My set up: PC Windows 10 (asus z87-expert using optical out) Receiver Yamaha HTR-5920 (old and not great but it's what I've got) 3.1 speaker setup
BEST BITPERFECT SETTINGS FOR ODAC 32 BIT
Now, what would be nice? The ability to drop SoX or SRC in as Window's resampler straight up, because it'd be nice to have good quality everywhere, not just in Foobar.Īlso, as a side note, why I don't do 16/176.4 in Windows and in Foobar2k? SoX and SRC are 32 bit native, they can hide their imprecision better at that high of a bit depth.Īlso, also, if I'm doing straight up sound analysis? I WASAPI the exact output, however, yes, it means it screws up all other apps: some apps you need to restart completely, others, like individual Chrome tabs, just need to be refreshed.Īs long as we're talking windows settings, any chance someone could explain. Now, what I do personally? My Bifrost can't do 24/176.4 (although it can do 16/176.4, I've never gotten around to bugging Schiit why), so I do 24/192 in Windows, then use a plugin in Foobar2k for SoX resampling (better than SRC's src-sinc-best, uses less CPU, alas neither ALSA nor PulseAudio offer it yet, at least, they didn't the last time I used Linux).ĪBing SoX 24/192 vs original 16/44.1, I couldn't tell the difference, however, I just barely could with SoX (or any resampler) 24/96 at least, I think I could, it made sibilant parts in songs worse if they were hitting my headphones hard enough. Window's resampler has no added noise, as far as I can tell, with 44.1 or 88.2 to 176.4, or 48 or 96 to 192.Ĥ4.148 is verboten under even the most perfect of resamplers, you can never get a convincing output. Quadrupling the sample rate, instead of merely doubling it, is enough for linear samplers (which is what Windows uses, or some similar enough algo) to perform well enough. What I recommend is (24,32)/176.4 if your device has it. That isn't a correct analysis either, although close.
0 kommentar(er)
