1. What does looping checkbox next to Interpolation do?
2. Which is the best for interpolation? FIR or cubic?

3. Noise Reduction checkbox next to Sample Rate, what's the noise?
4. What's this sample rate, how is it different from the sample rate under resample?

5. For Bass extension, if I use a high quality headphone, does it make any difference if I uncheck it or check it and move the slider to 10Hz (like to prevent bass rolloff?)

6. For DSP plug-ins, what do soft clipping limiter and ddvanced Limiter do?

7. Before when I use foobar v0.43 the bitrate of the MP3 file which is being played is showed on the bottom of the window, now it is replaced by [unknown], does it mean I didn't turn this function on or does it mean the foobar cannot get the data anymore?

8. For reverb and pro-logic surround, the difference is very subtle. Any thoughts on this?

6. search the forums, answered numerous times.

im not familiar with foo_mod so i cant answer the first few -- which i think theyre about.

7. titltry returning to default title formatting

Could you explain a little more? I did a search on "titltry" and even "titletry" (thought you made a typo) but found nothing.

1 and 2. Gee, you missed the part where these are in the Module Decoder property page. Looping means modules with backwards jumps will loop endlessly rather than just flow past the jump effects. Interpolation modes are arranged by order of quality and/or cost of use. Cubic is slower than linear, but sounds better. FIR is also slower than cubic, but should sound sharper, depending on the samples. The choice is up to you. See #8 below.

3. Noise Reduction, as Modplug calls it, is a simple low pass filter. Maybe I should have removed the option... See #8 below.

4. Mixing frequency of the module decoder. Either set it to match your resampler setting, or set it to the highest rate your sound card supports, ie. 48000 or 44100. Set lower if your system can't handle it. See #8 below.

5. It boosts bass below the frequency you specify. Disabling it will not attenuate the signal. Enabling it will not magically give your headphones the ability to generate frequencies they were not designed to handle. See #8 below.

6. For redundancy's sake, Soft clipping limiter is the same old 6dB limiter, and Advanced Limiter is a new clipping protection DSP. Buffers 100ms of audio and smoothly attenuates the entire signal if necessary to prevent clipping, rather than smoothly chopping off peaks.

7. Either delete your configuration, or go to Preferences and press the Reset all button. Or, I can give you the default formatting string, but I will not paste it here in the topic as it will screw up the formatting. (No, I will not chop it in half and expect you to know how to assemble it properly.)

8. Again, part of the Module Decoder preferences, will only affect modules. See the list of extensions in the file associations section of the installer, under File associations, Modules (foo_mod).

I think he meant for you to try resetting your formatting options to the default ones.

Call me slow but I want to confirm it again. Everything under Module Decoder has no effect whatsoever on MP3 files correct?

Update: Reinstalled foobar, now the bitrate info is working.

So would this be similar to the auto-attenuate function in MAD /w winamp 2?

When I use M-audio Sonica with foobar, usually a loud spike of noise occurs about 1-5 seconds after a MP3 file has been started playing, I can also make it happen by forward the sound (Crl + right arrow) sometimes. However this issue only exists when I use kernel streaming, so I think it's an isolated problem.

Any possible fix?

Possibly, but I wouldn't have any idea without looking at the latest MAD source.


As Kernel Streaming is experimental and does not work for everyone, the current solution is to simply not use it. Try DirectSound with or without hardware acceleration, or WaveOut. Or you can try updating your drivers, unless they're already the newest.

I just received my Sonica so I didn't test it much on v0.43, but from what I remember I did not get as much noise spike in 0.43 compare to 0.5 for kernel streaming. Could someone tell me if the codes for kernel streaming was changed in 0.5 or not? If it's the same exact codes then I guess something else contributed to the problem.

Yes, it is. But its got some more thought put into it, using 100 ms buffer instead of the somewhat outdated MAD attenuation, which I forget how to explain. Therefore, its more effective. By how much, I dunno.