What is a .667 file?
A DOS tracker module from Composer 667, an early Tomasz Pytel release that preceded the better-known Composer 669. The two are separate formats rather than variants of one another.
- Did you know
- The 669 family is not named after its own magic bytes - a Composer 669 file begins with the letters "if", and the extended UNIS 669 variant begins with "JN", the initials of its author Jason Nunn.
- Analyser handles .667 alongside related formats such as .MOD, .XM, .IT and more.
- In Analyser's format library, .667 sits in the System & disk category.
- What Analyser shows you
- Play and analyse tracker modules - MOD, XM, IT, S3M and around sixty relatives from the demoscene and the Amiga and DOS eras. A module is not recorded audio: it is a bank of instrument samples plus a pattern score saying which sample to trigger, on which channel, at which row, so playing one means running a tracker engine. Analyser renders the song on your device with libopenmpt - the engine behind OpenMPT - and then treats the result like any other audio, so you get the full Sound section: waveform, spectrogram, transport, loudness, key and BPM. Above it sits the module itself - the tracker that wrote it, the channel, pattern and order counts, the song message, and the sample and instrument name lists, which is traditionally where authors left their greetings. The rendered song can be saved as a WAV.
- Open a .667 file
- Drag a .667 file onto the Analyser home page (or tap to pick one). It opens entirely in your browser - nothing is uploaded, there is no account, and it works offline once installed.