Note: It is strongly suggested that the import feature is used only as a basis for a conversion, manual work will be needed in most cases.

Protracker

4-32 channel modules are supported. It is assumed a file with no signature bytes (M.K. etc.) are original The Ultimate Soundtracker modules, which may not be the case.

Some effects are converted but because Protracker works on sample periods and not notes when e.g. pitch bending, the actual speeds will be off.

FastTracker II

Song data is loaded, however multisample instruments only load the first sample. Pitch bends speed most likely will be off, but almost all effects are imported.

AHX

klystrack attempts to load AHX modules as perfectly as the differences between AHX and klystrack permit. Here are some things that can't be converted perfectly:

• AHX envelopes are not ADSR like in klystrack, additionally the envelope timing is not perfect
• AHX noise is a looping sample, in klystrack the noise is generated and does not loop
• klystrack PWM is oscillator-based while in AHX it works between upper and lower limits
• There is no automatic filter modulation in klystrack
• The same precautions apply to portamento etc. as in Protracker
• In AHX the pattern commands override the instrument commands while in klystrack it is the other way around (e.g. if an instrument sets the cutoff with a command, a pattern command will might not change the cutoff at all). If the filter commands look like they do not do anything, check the instrument program and remove the filter commands there.

Organya

Simple note data import without samples.

Flizzer Tracker

Attempts to load as perfect as possible (since Flizzer Tracker has a lot of klystrack code). The differences may be in volume and filter sound texture which may require further manual adjustment. Samples are converted to usual klystrack 16-bit signed mono PCM, so the module with long samples will weigh more than .fzt source file.

Envelope timings may differ, they are imported with minimum difference search algorithm. Vibrato and PWM speeds may differ significantly.

FamiTracker

.ftm, .0cc, .dnm files are supported except, maybe, very old .ftm ones (you can try to re-save them in Dn-FamiTracker). A lot of weird or chip-specific effects are not supported. FDS FM not supported. VRC7 instruments not supported, left as generic pulse 2A03 instruments. You may encounter effect spam in imported data, that's because FamiTracker effects work differently, and to resemble their behaviour the automatic effect spam is used (e.g. portamento and hardware sweep, volume fade).

If klystrack freezes for more then 10-15 seconds during import, it means that it crashed because (most likely) file is corrupt.

.eft files are supported, but support is very limited. Most likely klystrack will crash while trying to import them (the reason is because I don't have the most recent E-FamiTracker source code to use it as a reference).

Instrument copies are created if instrument is used on different channels (e.g. pulse, triangle, noise, DPCM). Cross-chip instruments supported for VRC6.

If FamiTracker instrument has no arpeggio macro, a special loop-through 3 notes arpeggio macro is generated to make arpeggio pattern effects work.