Module file

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Lua error in package.lua at line 80: module 'strict' not found. Module files (MOD music, tracker music) are a family of music file formats originating from the MOD file format on Amiga systems used in the late 1980s. Those who produce these files (using the software called trackers) and listen to them, form the worldwide MOD scene, a part of the demoscene subculture. Module files are often chiptunes.

The mass interchange of "MOD music" or "tracker music" (music stored in module files created with trackers) evolves from early FIDO networks. Many websites host large numbers of these files, the most comprehensive of them being the Mod Archive.

Nowadays most module files, including ones in zipped form, are supported by most popular media players such as Winamp, VLC, Foobar2000, Amarok, Exaile and many others (mainly due to inclusion of common playback libraries such as libmodplug for gstreamer).

Structure

Module files store several "patterns" or "pages" of music data in a form similar to that of a spreadsheet.[1] These patterns contain note numbers, instrument numbers, and controller messages.[2] The number of notes that can be played simultaneously depends on how many "tracks" there are per pattern. They also contain digitally recorded samples as well as coding for sequencing the samples in playback.[3][4] The programs that are used to create these files provide composers with the means to control and manipulate sound samples in almost limitless ways to produce music.

A disadvantage of module files is that there is no real standard specification in how the modules should be played back properly, which may result in modules sounding slightly different in different players. This is mostly due to effects that can be applied to the samples in the module file and how the authors of different players choose to implement them.[5]

Popular formats

Each module file format builds on concepts introduced in its predecessors.

The MOD format (.mod)
The MOD format was the first file format for tracked music on the Commodore Amiga.[6] A very basic version of this format (with only very few pattern commands and short samples supported) was introduced by Karsten Obarski’s Ultimate Soundtracker in 1987.[7] It was designed to use 4 channels and sixteen samples.[8] Ultimate SoundTracker was soon superseded by NoiseTracker and ProTracker, which allowed for more tracker commands (effects), longer samples, more patterns and other improvements.[9] Later, variants of the MOD format that appeared on the Personal Computer extended the number of channels, added panning commands (the Amiga’s four hardware channels had a pre-defined stereo setup) and expanded the Amiga’s frequency limit, allowing for more octaves of notes to be supported.[10]
Arguably one of the most widespread tracker formats (also due to its use in many computer games and demos), it is also one of the simplest to use, but also only provides few pattern commands to use.
The Oktalyzer format (.OCT)
This was an early effort to bring 8 channel sound to the Amiga. Later replayers have improved on the sound quality attainable from these modules by more demanding mixing technologies.
The MED/OctaMED format (.MED)
This format is very similar to sound/pro/noisetracker, but the way the data is stored is different. MED was not a direct clone of SoundTracker, and had different features and file formats. OctaMED was an 8-channel version of MED, which eventually evolved into OctaMED Soundstudio (which offers 128-channel sound, optional synth sounds, MIDI support and lots of other high-end features).[11]
The AHX format (.AHX)
This format is a synth-tracker. There are no samples in the module file, rather descriptions of how to synthesize the required sound. This results in very small audio files (AHX modules are typically 1k-4k in size), and a very characteristic sound. AHX is designed for music with chiptune sound. The AHX tracker requires Kickstart 2.0 and 2 mb RAM memory.
The ScreamTracker 3 format (.s3m)
Scream Tracker 3's S3M format added sample tuning (defining the exact frequency of the middle C for samples), increased the number of playback channels, made use of an extra column specifically for volume control (which was extended by other trackers to handle panning commands as well), and compressed pattern data for smaller file sizes.[10]
File:Elwood - Dead Lock (Open Cubic Player).webm
Open Cubic playing a FastTracker 2 module. Credit: Elwood - "Dead Lock" (1995)
The FastTracker 2 format (.xm)
With the XM format, FastTracker 2 introduced the concept of "instruments", which applied volume and panning envelopes to samples.[12] It also added the ability to map several samples to the same instrument for multi-sampled instruments or drum sets. XM uses instrument-based panning – instrument numbers in patterns always reset the channel’s panning to the current sample's initial panning. It uses MOD effect command letters, plus a few of its own for more sound control. The composer can define initial tempos and speeds; provide envelopes to samples by assigning them to instruments; set sample looping and apply automatic sample vibrato oscillation.[10]
The Impulse Tracker format (.it)
Impulse Tracker introduced the IT format, which, in comparison to the XM format, allows instruments to also specify the transposition of assigned samples depending on the note being played, applying resonant filters to samples, and defining “New Note Actions” (NNAs) for instruments to release playing notes on a pattern channel while a new note is already playing, which helps to keep the number of pattern channels to while still being able to have a high polyphony. Like S3M files (and contrary to XM files), panning is channel-based, meaning that channels have an initial pan position which can be overridden by panning commands or instruments’ and samples’ default panning settings.[10]

Scene

The process of composing module files, known as tracking, is a highly creative and skillful activity that involves a much closer contact with musical sound than conventional composition, because every aspect of each sonic event is coded, from pitch and duration to exact volume, panning, and laying in numerous effects such as echo, tremolo and fades.[13] Once the module file is finished, it is released to the tracker community. The composer uploads the new composition to one or more of several sites where module files are archived, making it available to his or her audience, who will download the file on their own computers. By encoding textual information within each module file, composers maintain contact with their audiences and with one another by including their email addresses, greetings to fans and other composers, and virtual signatures.[13]

Although trackers can be considered to have some technical limitations,[14] they do not prevent a creative individual from producing music that is indiscernible from professionally created music.[15] Many tracker musicians gained international prominence within MOD software users and some of them went on to work for high-profile video game studios, or began to appear on record labels.[16][9] Notable artists include Andrew Sega, Jeroen Tel, Bjørn Lynne, Darude, Alexander Brandon, Peter Hajba, Purple Motion, Axwell, 4mat, Jesper Kyd, Brothomstates, Elwood, Markus Kaarlonen, Michiel van den Bos and Dan Gardopée. Deadmau5 and Erez Eisen of Infected Mushroom have both used Impulse Tracker in their early career.[17][18]

Music disk

Music disk, or musicdisk, is a term used by the demoscene to describe a collection of songs made on a computer. They are essentially the computer equivalent of an album. A music disk is typically packaged in the form of a program with a custom user interface, so the listener does not need other software to play the songs.[19] The "disk" part of the term comes from the fact that music disks were once made to fit on a single floppy disk, so they could be easily distributed at demo parties. On modern platforms, music disks are usually downloaded to a hard disk drive.

Amiga music disks usually consist of MOD files, while PC music disks often contain multichannel formats such as XM or IT. Music disks are also common on the Commodore 64 and Atari ST, where they use their own native formats.[20]

Related terms include music pack, which can refer to a demoscene music collection that does not include its own player, and chipdisk, a music disk containing only chiptunes, which have become popular on the PC given the large size of MP3 music disks.

Software module file players and converters

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Many of the listed software use the modplug engine from the open source multimedia framework gstreamer.[21]

Players

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Converters and trackers

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 10.2 10.3 Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. GStreamer Bad Plugins 0.10 Plugins Reference Manual
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links