It allows users to import valid.NSF files (see below) and subsequently save the result into a.FTM file.

It was developed by rainwarrior, and its initial release was on July 8, 2011.

Editing is disabled on purpose to encourage using the official version of FamiTracker for editing.

NotSoFatso then analyses any and all data it finds on a per-frame basis, and retranscribes it in FamiTracker in the form of a 900-bpm (or 750-bpm for PAL) module.

This means that the resulting module plays at full speed, and that any vibrato, pitch envelopes, duty cycle envelopes etc.

It helps if, in the Importer Options dialog, you set it up so that the pattern length matches with the tune; that way, the only thing left is to add a Bxx command on the last pattern to make the pattern loop to position xx.

In some cases, however, this is impossible (for instance if the original.NSF s tempo is uneven or the tune uses a time signature change halfway through).

As of version 0.5, the program is subject to the following limitations.

For the shortest settings the sound may turn on and off faster than a single frame and be missed entirely.

This problem is sometimes seen in hi-hat sounds on the noise channel, or blips in the triangle channel.

For the fastest setting this gives a small loss of smoothness; for other settings the difference is negligible.

If a sample is played with a low (or no) offset first, and then a higher offset later, the higher offset will be picked up and the sample will be reused.

If the higher offset is played first, there will be redundant copies of that sample.

The importer only does one pass, so it will not go back to replace earlier offset samples.) This feature seems more or less particular to FamiTracker NSFs; examples in original NSF ROMs have yet to be discovered.

This has not been seen yet in original NSF ROMs, but is sometimes used in modern tracks.

Where it is used, samples that have overlapping memory addresses may sound corrupt.

This is not a bug in the NSF importer, but the resulting import may not sound like you expect in FamiTracker.

Exporting back to.NSF will help verify that it is getting the correct values.

Nsf To Midi Converter