// generate FT2's pan table [round(65536*sqrt(n/256)) for n = 0...256] for (i = 0; i < 257; ++i) p->PanningTab[i] = sqrtf((float)(i) / 256.0f);
Channel 2? Or 01 in the DUMB control. Check it, it's still panned.FT2's panning isn't strictly linear:Code: [Select] // generate FT2's pan table [round(65536*sqrt(n/256)) for n = 0...256] for (i = 0; i < 257; ++i) p->PanningTab[i] = sqrtf((float)(i) / 256.0f);Where the panning range is 0 through 256, left volume is PanningTab[256 - pan] and right is PanningTab[pan].
Track gain : +7.16 dBTrack peak : 0.554683Album gain : -1.66 dBAlbum peak : 1.000000
EDIT: Fixed the Shadow of the Beast 2 module, at least. Which is technically incorrect, as Protracker never had a configurable restart position, and always wrote the same value to that field in the file.
Hi kode54,very much enjoyable plugin, indeed! Is ever be planned a support to David Whittaker files?I know they have their own play routine, but it would be grat! They are so good!Thank you very much
Any reason foo_dumb 1.0.124 still includes an old BASS DLL?
Quote from: sandy.v on 10 August, 2014, 12:24:46 AMAny reason foo_dumb 1.0.124 still includes an old BASS DLL?It's the same version which is bundled with foo_midi, version 2.4.9. I'll update it whenever the next version comes out, as nothing relevant to either component has changed.
Loading time is irrelevant, unless you either have some really ancient machine, or are stupid enough to add hundreds of thousands of files to your playlist in one go. The latter will always be a problem with current foobar2000, because it always must pre-load information from all tracks before returning control to the user. If you don't like that, find another player for your module collection.
If you like XMPlay so much, go ahead and use it. It doesn't support half of the formats I support with DUMB, but I'm sure you can convince Ian Luck to add those some day, assuming you care about any of them. Last time I asked him to add formats, he told me to just convert them to IT/XM/S3M, as if any of the formats in question were 100% compatible. He also suggested keeping full format parsers around for little things like song title and sample info reading, and for probing for subsongs.
OpenMPT, on the other hand, is exactly compatible with one thing: OpenMPT. Anything else is merely approaching or simply throwing compatibility out the window. Expect songs made in OpenMPT to sound a hell of a lot louder in any reasonable facsimile of Impulse Tracker. And don't get me started on those DirectX effects. (If you want them in Wine, you have to locate a copy of dsdmo.dll and install/register it in your Wine prefix before they'll work. The versions of BASS for all other non-Windows platforms have their own built-in imitation of the effects.)
Nah, it's okay, but you're right, I do have a bit of a problem with mixing speed. It still has to step through the entire playback process, sans mixing samples, to calculate song lengths and gauge if any orders go unplayed and may potentially be sub songs.
The load time becomes especially excruciating if you try to do something like, say, loading the entire Modarchive collection in its double zip files. Something that does work, however. Well, to a point. There are a few songs/archives with same names if compared using case insensitive matching. So you'll get the songs loaded into the playlist and displaying the correct info on first load, but if you try to play them, it will pick the first instance in the outer archive to match, due to case insensitive matching inside foo_archive ZIP support. Maybe something to get fixed by the next release of that component.