Music Production > MilkyTracker Feature Requests

Add an option to lower .mod pitch?

(1/2) > >>

MovieMovies1:
As far as I can tell, Amiga modules in at least ProTracker have a slightly lower pitch than XM files do in both FastTracker2 and Milky. Milky as of now uses XM pitches while playing back mod files, which is what FT2 does. This often makes mod files that rely on drumloops and related things sound off.

Considering all the other amigamod compatibility options that are already added to MilkyTracker, I don't think adding an option to lower the pitch to the Amiga's standard to improve compatibility with modules that rely on drumloops and stuff would be too much of a stretch. It would certainly help when I try to make amigamods myself, so I don't have to drop it off in another editor just to make sure my samples line up right.

Do forgive me if this is something that has been asked about before.

Deltafire:
This is the first I've heard of this.

Could you check that the playback mode is set to "Protracker 2/3.x" in Options?  You could also try setting the frequency table to Amiga in the config section.

MovieMovies1:
It's definitely all set to the correct ProTracker 2/3 playback settings and the Amiga frequency table, and the samples are definitely playing back slightly faster than they should.

I've provided two sample recordings in the attached zip file. Both play MilkyTracker's output first, then it plays ProTracker-win32's output.

 - "01 Pitch Difference.mp3" showcases the pitch difference, short and simple.
 - "02 Drumloop Mismatch.mp3" shows how this can be especially problematic, as MilkyTracker's output has a hiccupy feel in addition to having a serious click problem towards the end due to this sample speed mismatch.

I wish I had an actual Amiga to record this off, but sadly I don't, so this is the next best thing I can really do. It may also be something that actually differs between PAL and NTSC machines, so adding this as a switch option would probably be the best way if it is to be implemented.

Nikku4211:
How about using WinUAE and emulating ProTracker? Will that work out for you?

MovieMovies1:
So I did set up WinUAE and managed to load up ProTracker 2.3d to test both PAL and NTSC modes to see if my hypothesis of PAL/NTSC differences being the cause. PAL matches the output of the Windows ProTracker clone and whatever other tools that match PAL pitch. NTSC matches up with MilkyTracker's current pitch output. It probably all comes down to overall machine clockspeed.

Considering a great big deal of Amiga modules were made with PAL machines, I'd say it'd be a good idea to implement an option for this via a switch, to keep compatibility with both PAL and NTSC Amiga modules alike, as well as .mod files not made for Amiga machines as well.

Navigation

[0] Message Index

[#] Next page