Originally posted by: xtknight
Is the X-Fi really worth it over the Audigy 2?
I've not used it myself, but I would think so. It has a much better SRC and it's output quality is overall a step higher. The crystalizer is a gimmick, and CMSS is not something I'd ever use myself, but the HRTFs are something that would benefit headphone mode over Audigy2. If you don't intend to game on the card however you can get higher quality output for a similar if not lower price (ex, EMU 0404) which is yet again significantly better than the X-Fi.
And BTW that reminds me, if you have speaker options configured as headphones in either the windows or creative config panels, be sure to change that to stereo speakers.
Wow, nice. I tried the out_wave_ssrc.dll resampled to 96kHz/24bits, the difference is actually stunning. It makes it sound like 384kbps audio instead of muffled 128kbps. Should I limit myself to 48 kHz or is 96 any better since my Audigy (supposedly) supports that?
I would limit myself to 48kHz. The reason for this is that the Audigy2 DSP operates at 48kHz. A 44.1kHz source has to be upsampled to 48kHz and as per output instructions of the output plugin, it's also typically forced to downsample again to 44.1kHz. Allowing the resampler to work at 48kHz, you're effectively not resampling to 48kHz but preventing downsampling to 44.1kHz. Setting higher than 48kHz would cause a resample that would be mostly unnecessary. Some DACs however function better at higher bit-rates/sampling rates even though fundamentally you're not getting any extra information by upsampling. The Audigy2 doesn't really benefit from this. Harmonic distortion is lower yet Intermodulation distortion is higher, but there's still the disadvantage of unnecessary resampling, it's 2 against 1 really, but wouldn't hurt to try both.
With Shoutcast the out_wave_ssrc.dll makes the sound buffer/pause a lot. Is that fixable or is it just the nature of the beast? Reducing buffer in its options to the lowest 200 ms. doesn't seem to help.
Try increasing buffer length to around 10 seconds, and track-change buffer to around half a second. Otherwise just play around and you should get it.
Any idea about 'distribution': rectangular, triangular, Gaussian? Which would be better or is it just subjective?
Triangular would be best, though I believe this only applies to bit-depth changes so if you keep it at 16 that will be overlooked. You probably should keep it at 16, but then again doesn't hurt to try otherwise.