Print

[Deltafire]

Since MOD is predominantly used for Amiga modules, I have modified the MOD exporter to limit sample sizes to 64k.

[raina]

I think this could be handy but should be optional. Why limit editing/making non-Amiga MODs? It's 20+ years too late.

[Deltafire]

What is a non-Amiga mod anyway?  Surely you'd use .XM for anything on the PC.

Creating .mod files that aren't compatible with Protracker/Amiga is like creating .XM files that aren't compatible with FastTrackerII!

[Saga Musix]

Well, people create MOD files for all kinds of reasons, being able to play them with ProTracker isn't always one. Also keep in mind that there's ProTracker for Atari platforms for example, not sure if there's a 64k limit there, same with various Amiga replayers (since there are many Amiga trackers that can actually handle bigger samples). So yeah, as raina said, this should probably be optional. Especially when considering MOD files with more than 4 channels.

Creating .mod files that aren't compatible with Protracker/Amiga is like creating .XM files that aren't compatible with FastTrackerII!

ProTracker is just a big hack upon an existing format (Ultimate Soundtracker), remember that? So why shouldn't we just limit our MODs to 1xx/2xx effects, 9kb per sample and only 15 samples? MOD is a very loosely defined format, there are many variations of it and many programs that support it, and while ProTracker might have been the most common tool on the Amiga to create MODs, there are dozens of other popular MOD trackers out there.

[Deltafire]

I've changed it to display a warning when samples are over 64k in size, but limit the sample size to 128k (the maximum possible in the mod format).