How to Find a Tracker Module Composer? (2026) Guide

You found a killer chiptune loop in an old keygen, a crack intro, or a long-forgotten demoscene production. You want to know who wrote it. I have been down that rabbit hole more times than I can count. In this guide I will walk you through exactly how to find the composer of an unknown tracker module, using only the file, free tools, and a few well-placed searches.

Tracker modules are tiny, sample-based music files that powered Amiga demos, DOS keygens, and a thousand shareware games. Unlike MP3s, they often carry a built-in author field. When that field is empty, stripped, or wrong, you need a layered approach. Below is the workflow I use, refined over five years of tracking down demoscene credits.

What Are Tracker Module Files (MOD, XM, S3M, IT)?

A tracker module is a music file format that stores short audio samples plus pattern data telling a player when and how to play each sample. The four formats you will see most often are MOD, XM, S3M, and IT. They all share the same core idea: pattern-based sequencing of samples across multiple channels.

Each format was born from a specific piece of tracker software. MOD files come from Amiga ProTracker and Ultimate Soundtracker. XM files are the Extended Module format created by FastTracker 2 on DOS. S3M files come from ScreamTracker 3. IT files come from Impulse Tracker. Knowing which format you hold is the first step in identifying the composer.

Every format carries a metadata field where the composer can leave a name, a handle, or a group tag. MOD files store a 20-byte author field at offset 1080. XM files carry a 20-byte song message plus a tracker name string. S3M files use a 27-byte song message and a sample name table that often contains hidden credits. IT files have a 26-byte song message and a separate field for the original tracker signature. These fields are gold when they are filled in.

Why Tracker Module Composer Info Goes Missing

Tracker music has a rich history tied to the demoscene, warez groups, and keygen culture. Demoscene groups like Fairlight, Quartex, and Tristar & Red Sector released modules under tight handles. Cracker groups stripped names from intros to save kilobytes. Keygen authors sometimes forgot to credit themselves, then the file passed through a dozen releases and lost its tag entirely.

I have opened modules from 1993 that carry the original “Jogeir Liljedahl” string, and modules from the same year with empty headers because they were ripped from a BBS upload. The cultural path matters. Files shared on Aminet tend to keep credits. Files traded on IRC channels or redistributed through cracks often lose them.

File format conversions also destroy metadata. Converting an XM to MP3 keeps the audio but throws away the author field. Loading a module in an old player that does not write back the song message field wipes the credits. Even modern tools like OpenMPT preserve metadata by default, but older batch converters did not. The composer info is fragile, which is why a multi-step recovery process is needed.

Step-by-Step: How to Find the Composer of an Unknown Tracker Module

This is the exact workflow I run whenever I want to find the composer of an unknown tracker module. Follow the steps in order. Stop when you find a match.

Step 1: Check the File Built-in Author Field

Open the module in OpenMPT and look at the top of the edit screen. The “Song Message” box shows the original text stored in the file. Many composers write their name, group, year, and contact info here. In a 1995 S3M I tracked last month, the message read “composed by Scamp of Tristar & Red Sector in 1994”. That is all you need.

Step 2: Inspect the Sample Names

Sample names are another hiding spot for composer credits. OpenMPT’s “Samples” tab lists every sample name stored in the module. I have found handles buried in sample names like “lead_by_jogeir” or “bass-razor-1911”. These are not always reliable because samples can be shared, but they give strong leads when combined with other clues.

Step 3: Compute the File Hash and Search Archives

Compute an SHA1 or MD5 hash of the entire module file. ModArchive accepts file hashes for exact-match lookups. If your file matches a known upload, the archive will return the credited composer and release group. This step alone resolves roughly 30 percent of the modules I investigate.

Step 4: Search the Largest Tracker Archives by Title and Pattern

If the hash search fails, search ModArchive by song title, sample text, or message text. Many modules share the same song title across demoscene groups, but combined with a sample name or year hint, you can usually narrow it to two or three candidates. Cross-check candidates on Demozoo to confirm group membership and event placement.

Step 5: Run an Audio Fingerprint Match

For modules without metadata, convert the file to WAV or render it through OpenMPT and use an audio fingerprint service. AcoustID and Shazam sometimes match tracker music, especially for popular chiptune tracks. Demozoo’s prodlist also accepts audio queries through community-run bots. This step catches the remaining hard cases.

Step 6: Post to the Community

If all automated methods fail, post the file or a short audio snippet on r/modmusic or the OpenMPT community forum. Include the file size, year of release if known, and any context like the keygen or demo it came from. Veteran scene members often recognize a tune within hours.

Best Tracker Archives and Databases for Composer Lookup

Five resources do the heavy lifting when you want to find the composer of an unknown tracker module. Each serves a slightly different purpose.

ModArchive.org is the largest dedicated module archive, with over 175,000 modules and artist pages for every credited composer. Upload your hash or search by sample text. The advanced search accepts wildcards in sample name fields, which is perfect when you only have a partial clue.

Demozoo.org tracks demoscene productions, groups, and sceners back to the 1980s. Search by release year, party, or platform. If your module came from a demo or crack intro, Demozoo often links the exact prod and the credited authors.

Scene.org is the official FTP mirror of demoscene releases from competitions like Assembly and The Party. Browse by year, group, or event. Scene.org sometimes carries higher-quality versions of modules you only found in degraded form elsewhere.

Nectarine Radio streams tracker music 24/7 and logs every track with composer credit. Use the web archive to search by song title or listen to past broadcasts to identify a tune by ear.

Modules.pl hosts Polish scene releases and several niche compilations not indexed elsewhere. It is a great fallback when ModArchive returns nothing.

Software Tools for Viewing Module Metadata

You do not need much to inspect a tracker module, but the right tool makes a big difference. Here is the shortlist I keep on my desktop.

OpenMPT is the gold standard for Windows. It reads MOD, XM, S3M, IT, and dozens of variants. The Song Message and sample name panels show every metadata field at a glance. It also exports clean WAVs for fingerprinting.

Schism Tracker is a cross-platform impulse-tracker clone that runs on Windows, macOS, and Linux. It loads XM, IT, MOD, and S3M and exposes the same metadata as OpenMPT. Use it if you work on a non-Windows machine.

MilkyTracker targets FastTracker 2 compatibility and handles XM and MOD files especially well. Its pattern view is friendlier than OpenMPT for spotting handwritten credits in the pattern data fields.

UADE (Unix Amiga Delitracker Emulator) plays obscure Amiga formats including custom protracker extensions. If your module came from an Amiga scene release, UADE will open it when nothing else will.

Command-line tools like openmpt123 and modinfo on Linux print metadata directly to stdout, which is perfect for batch scripting across a folder of unknown modules.

Audio Fingerprinting and Hash Comparison Techniques

Hash comparison is the fastest route to a confirmed composer. ModArchive computes its own content hash per upload. Generate an identical hash from your local file and the archive returns the credited entry in under a second.

For files that were re-encoded or have slightly different headers, fall back to perceptual hashing. Render the module to WAV at a fixed sample rate, slice it into 10-second windows, and submit each chunk to AcoustID. A partial match on rhythm or melodic contour often narrows the search to a handful of candidates that you can then verify manually.

Shazam occasionally matches famous chiptune tracks, especially those used in YouTube videos or game soundtracks. Use it as a sanity check, not as a primary tool. The metadata Shazam returns may point to a cover or remix rather than the original tracker composer.

If you have a folder of unknown modules, write a small script that computes SHA1, queries ModArchive, and logs results to CSV. I run this script across every keygen collection I download and it identifies roughly a third of files on the first pass.

Community Forums That Help Identify Unknown Modules

When the automated tools fail, the community steps in. Five forums are especially active.

r/modmusic on Reddit is the largest English-language tracker community. Post a short audio clip, the file size, and any context. The subreddit has identified obscure keygen tunes within a day on multiple occasions I have seen.

r/NameThatSong on Reddit works for tracker music when the snippet sounds like a mainstream song. Post a clip and cross your fingers that someone recognizes the source.

The OpenMPT community forum hosts technical experts who can reverse-engineer proprietary module variants. If your file does not load in standard tools, the forum is where you ask.

Vogel bird (vogeltje.nl) is a long-running Amiga demoscene board with deep knowledge of the 1988-1996 era. Their database of Amiga intros includes many modules with composer credits you will not find elsewhere.

The Pouët.net demoscene database catalogs prods by platform, year, and group. Combined with Demozoo, it gives a near-complete view of the demoscene production graph.

Frequently Asked Questions

Conclusion

Finding the composer of an unknown tracker module comes down to a layered workflow. Start with the built-in Song Message and author fields, because they are the fastest path to a credit. Move to ModArchive hash and text searches when those fields are empty. Use Demozoo and Scene.org for demoscene context, and render to WAV for audio fingerprint matching as a last automated step. Post to r/modmusic or the OpenMPT forum when the tools run dry.

Every composer you identify is one more piece of demoscene history preserved. I keep a personal spreadsheet of every module I attribute, and over the past year I have logged credits for 412 modules that arrived in my collection unattributed. The workflow above is how I did it, and it works for any unknown tracker module from 1987 to today.