The soundoutput of latest foo_mod v0.92 (6.9.2004) sounds better to me than its predecessors, especially .it files do sound clearer.
I permanently have interpolation switched off since it tends to surpress some of the audible things that you hear with no interpoltation.
Also this seems more true to the soundoutput of the original trackers IMHO.

So i take it that your plugin does have some influence on the soundoutput from bass.dll instead of ~importing~ its outpu to foobar?

I wonder why you provide v.2.0.0.18 of bass.dll with foo_mod instead of the current release v2.0.0.22. There's a noticable difference
in soundoutput, v2.0.0.18 seems not to process resonant filters of .it files. I can send you some files for easy comparison on that matter.

I've just found one .it file that won't load with your plugin,  error WARNING (Foo_Mod) : BASS_MusicGetLength() returned error: 20.
Xmplay v3.0.0.6 loads the file, so does Winamp v5.0.4 with in_mod v2.11. Is it related to bass.dll or to foo_mod? Please let me know if
you want to have a look on the file and where i should send it to.

Could you please implement display of instrument/sample info of .XM files?

Except for FastTracker 2.x and Impulse Tracker, which featured optional resampling.

Nope. Not one difference, just straight from 32-bit floating point to the player's 64-bit floating point audio pipeline.

I cannot hear a difference between 2.0.0.18 and 2.0.0.22 with the one resonant filter example I have, jeff93.it. Also, it's hard to keep up with minor releases when the author doesn't mention them on the webpage, and rarely on the forum. (Slightly off-topic, the standard in_mod is not a proper reference for resonant filters, as it gets them completely wrong.)

You can use the Foobar2000 uploads forum.

I already implemented XM info display in foo_dumb, but I can borrow that much of DUMB to process and display XM information.

Quote

I cannot hear a difference between 2.0.0.18 and 2.0.0.22 with the one resonant filter example I have, jeff93.it. Also, it's hard to keep up with minor releases when the author doesn't mention them on the webpage, and rarely on the forum. (Slightly off-topic, the standard in_mod is not a proper reference for resonant filters, as it gets them completely wrong.)

I can asure you there is a difference in replay quality between v2.0.0.18 and v2.0.0.22. I'll load up a file which makes heavy use of resonant filters. Compare both dll's with it, you'll hear it.[a href="index.php?act=findpost&pid=240611"][{POST_SNAPBACK}][/a]

    {
  float inv_angle = (float)(sampfreq * pow(0.5, 0.25 + cutoff*(1.0/(24<<IT_ENVELOPE_SHIFT))) * (1.0/(2*3.14159265358979323846*110.0)));
  float loss = (float)exp(resonance*(-LOG10*1.2/128.0));
  float d, e;
#if 0
  loss *= 2; // This is the mistake most players seem to make!
#endif

#if 1
  d = (1.0f - loss) / inv_angle;
  if (d > 2.0f) d = 2.0f;
  d = (loss - d) * inv_angle;
  e = inv_angle * inv_angle;
  a = 1.0f / (1.0f + d + e);
  c = -e * a;
  b = 1.0f - a - c;
#else
  a = 1.0f / (inv_angle*inv_angle + inv_angle*loss + loss);
  c = -(inv_angle*inv_angle) * a;
  b = 1.0f - a - c;
#endif
    }

Regarding standard in_mod, you're talking about the winamp plugin here i guess? Yes, it's support of impulse tracker format lacks resonant filters.[a href="index.php?act=findpost&pid=240611"][{POST_SNAPBACK}][/a]

Quote

I already implemented XM info display in foo_dumb, but I can borrow that much of DUMB to process and display XM information.

That would be very nice. I plan to comment on foo_dumb, too. I'll open a new topic for it.[a href="index.php?act=findpost&pid=240611"][{POST_SNAPBACK}][/a]

I tried implementing XM info reading using just the XM parser from DUMB, and it bloated foo_mod by 50KB.

With foo_dumb, the detected song length comes out to about 90 minutes. ModPlug Tracker detects a length of about 5 minutes.

Found this masterpiece which fails to load with foo_mod, error: WARNING (Foo_Mod) : BASS_MusicLoad() returned error: -1.
Spx-Bubbles.it loads with Xmplay and foo_dumb.

Can you offer foo_mod plugin for download with implemented DUMB .xm-parser? I don't mind the extra KB as long as i can access sample/instrument info of .xm's too.

Thank you and regards, deus-ex.
[{POST_SNAPBACK}][/a]

[a href="http://www.hydrogenaudio.org/forums/index.php?act=Attach&type=post&id=1003]Jos-Dr4k.xm[/url] fails to load both with foo_dumb and foo_mod.
Foo_Mod error message: WARNING (Foo_Mod) : BASS_MusicGetLength() returned error: 20.
Foo_Dumb does'nt emit any message.

Regards, deus-ex.
[{POST_SNAPBACK}][/a]

previous_global_volume = global_volume;

(process a tick or row or such worth of pattern)

if ((global_volume == 0) &&
  (previous_global_volume != global_volume) &&
  (previous_global_volume != (file's starting global volume)))
{
  do something, perhaps cut playback here
}

I wondered if bassmod.dll v2.0 can be used instead of bass.dll. It is a MOD only version of BASS, filesize is only a third of bass.dll.
If that's an interesting option i'll have to ask Ian to update bassmod.dll to the same level of bass.dll.

Since bass.dll has enclosed support for .mp3 is it possible to access its .mp3 routines through foo_mod? That would enable a third option to play .mp3 files which i'd find to be interesting for comparison, i.e. how XMPlay's .mp3 routine sounds through foobar in conjunction with foobars dsp options which are far more advanced than XMPlay's.

deus-ex
[a href="index.php?act=findpost&pid=242491"][{POST_SNAPBACK}][/a]

As for BASS's internal MP3 decoder, I doubt there would be any noticeable difference between it and the standard mpglib decoder, if it is a compliant decoder. If someone else wants to take up the task, they're welcome to it.
[a href="index.php?act=findpost&pid=243920"][{POST_SNAPBACK}][/a]

I was just thinking about this last night. Foobar2000's "Standard Inputs" prefs page has a select box entitled "MP2/MP3 decoder", with only one option, mpglib, in the 0.8.3 Special Edition installer.[a href="index.php?act=findpost&pid=246622"][{POST_SNAPBACK}][/a]

I think it would be great to add BASS.DLL's MP3 playback[a href="index.php?act=findpost&pid=246622"][{POST_SNAPBACK}][/a]

(and perhaps also OGG playback)[a href="index.php?act=findpost&pid=246622"][{POST_SNAPBACK}][/a]

given that the DLL is already shipped with the installer.[a href="index.php?act=findpost&pid=246622"][{POST_SNAPBACK}][/a]

The rationale for this is that on older computers like mine, BASS.DLL is substantially quicker than mpglib at playback (CPU usage on PII 333: XMPlay ~8% for both MP3 and OGG, FB2K ~13-14% with MP3 slightly lower; I assume BASS.DLL is similar to XMPlay). I can't tell any different between them, but I haven't tried to ABX it.[a href="index.php?act=findpost&pid=246622"][{POST_SNAPBACK}][/a]

I don't have a copy of MSVC++ but if anyone does, and is looking for an idea for a Foobar plugin, this would be appreciated!
[a href="index.php?act=findpost&pid=246622"][{POST_SNAPBACK}][/a]

The API does not support decoding MP3 files one packet at a time, so it would have to be a separate input altogether....

Check Preferences -> Playback, see if dithering is enabled. This is a possible bottleneck which is not enabled by default...
This may just be the overhead of the 64-bit floating point audio pipeline.

Quote

I don't have a copy of MSVC++ but if anyone does, and is looking for an idea for a Foobar plugin, this would be appreciated!

If, by that, you mean that someone should donate money or a physical copy of Visual Studio to you, or you mean that you wish to purchase it from someone here, this is spamish.

If you are asking for an illegal copy, you are asking for someone to violate TOS #9. Please do that somewhere else.