Thanks for the reply TJ Max. Yes, exclusive mode enabled.
I use the regular ASIO driver. Is ASIO4ALL the same? I've heard of it and read that it can help some issues where regular ASIO driver is causing problems. I've also read sound quality is inferior with ASIO4ALL. Is it not a user-made ASIO driver for PCs that don't support the regular one for some reason?
Anyway, as per your recommendation, I set a larger buffer length. However, my BSODs seem to be the result of RAM usage. I worry that reserving more RAM for foobar will only exacerbate the problem. Maxing the buffer length seems to make no change in the crackles/pops when selecting songs and changing the time position of the track. These are still there
That's good to hear. Do you notice crackles/pops when selecting songs or changing their position in the progress bar? And a noticeable delay, too? I sure do. I just brushed it off as a cnotsequence of ASIO but is this supposed to happen?
And yes, I'm nearly 100% positive it's foobar. Had no BSODs whatsoever until installing it and using the bit perfect feature. The last one was a result of stopping the song being played and opening a youtube video. As soon as the youtube video sound was sent to the E1 (while foobar was still open), I heard a subtle crackle/pop and the BSOD occured.
Can you share what drivers and firmware you have at the moment for your E1?
ASIO4ALL is not a driver, but a utility that manages the driver.
If you were trying the buffer length within foobar, then try 1360 or 1920, those worked for me.
Maybe I missed it but can't you use WASAPI?
Edited by TJ Max - 2/8/14 at 11:24pm