Print

[Svetlana]

Hi, I've noticed a problem when saving .MODs under MilkyTracker .86 (I haven't noticed it in the last update, .85, so I assume it could be new.)

The samples have their offsets (data pointers?) shifted around, and a sample might have the first few bytes be the last few bytes of the previous samples. Like so:

Original file (MOD):


Milky-resaved file (MOD):


These images both show the same sample, and the bit added at the start is the end of the previous sample in the module.

Here are a couple of files, this is a song I've composed for a game using Lotus 3 samples. The song was composed in Milky by opening the original MOD and zapping the entire song to leave only the samples, I've saved it as a XM (fully abiding MOD limitations) then re-saved as MOD in OpenMPT. The second file is the song composed in Milky then saved straight to MOD. The difference is quite blatant from the first few seconds.

https://dl.dropboxusercontent.com/u/9435923/music/turbo/CD4-Cadmium.mod
https://dl.dropboxusercontent.com/u/9435923/music/turbo/CD4-Cadmium_milky.mod

Let me know if there's any more info I can provide.

[Deltafire]

Fixed (github).

Thanks for the detailed bug report

[Svetlana]

Is there anywhere to download the fixed version as a binary?

[Deltafire]

For which platform?

[Svetlana]

Windows. I'm currently using 7 x64. Would be nice to get an Mac OS X (G3) build as well, if that's at all possible. (I'm still using the old version available in the website)