Originally Posted by dukeReinhardt
Thanks for the response. So presumably with the resampling option unchecked in the ASIO plugin, no resampling will be done at all? In that case I'll leave it as is.
Not necessarily. ASIO is designed to provide a low latency direct access from the software to the output hardware. The goal is that you aren't un/re-locking constantly (which takes time and can screw things up if you're armed and live). So what more likely will happen is that non-native simply won't playback.
And thanks for the advice, I do know it takes a monumental effort to distinguish 192khz from 96khz
Here's the rub - you have to have files that are natively cut at 192khz or 96khz. Simply setting up your 16/44.1 mp3s to output at 96 or 192 is not doing anything for you - there MUST BE SRC to make that happen. There is absolutely ZERO potential for quality improvements there.
, but my reasoning is that I have cpu cycles to spare, and it costs me nothing to change sample rates around or tweak some things which is why I came here to ask and hopefully get a quick response from people in the know
. Conversely I have no money to spare for speaker/headphone upgrades right now!
On a true X-Fi (EMU20kx) chip, that's actually not done in the CPU. It's done in the X-Fi DSP. The chip does it so cleanly that it exists below the noise floor of any equipment you will have downstream (including the DtoA) - there is absolutely no quality benefit to be derived by re-sampling higher than native. You cannot "add in" quality in this manner. The perfect best-case scenario is native playback, but native versus SRC with something like the X-Fi is a total non-issue because the SRC is done so cleanly that every other device that touches the audio will inherently do more damage (so any "problems" with the X-Fi SRC are completely masked).
Regarding ASIO bypassing windows, how come with bit-matched enabled I can still control volume with the volume bar in windows? Actually I just noticed in mediamonkey using ASIO, I can change volume with the windows volume bar, but the green bar that indicates volume levels doesn't show. But say in youtube the green thing indicating volume movement does show - presumably this means mediamonkey uses ASIO while other programs don't? In which case windows is upsampling to 192khz outside of mediamonkey, but outputting bit-matched in mediamonkey. As I say if this is right I'll just leave it on 192khz since I don't mind cpu cycles or anything...
ASIO is a direct low-latency access from software to hardware, bypassing things like kmixer, but the volume control is a separate UI element and unrelated to the audio signal path inside of the OS (at least, for our purposes; the Windows Audio Stack is fairly complex).
There really is no reason to have it set to 192khz, but there's no reason not to - you can basically set it to whatever you want, because the X-Fi will resample and make it work. Almost nothing exists at 192khz, so that means it is always resampling (again, doesn't matter). Like I said, drop it in Entertainment Mode and let it run default - life is easier.