Convert MOD to AVI Online for Free

Render a MOD accurately, add a deliberate visual stream, and create an AVI movie only when a named workflow requires it.

TO
  1. Add a file Choose or drop it here
  2. Pick the format Change it whenever needed
  3. Download the result After conversion completes

MOD Music Has to Be Performed Before an AVI Can Exist

A .mod file is tracker music, not a movie. It originated with Amiga-era software: Ultimate Soundtracker established the form in 1987 and ProTracker-style modules later became common in demos, games, and music archives. The file stores short instrument samples with pattern instructions and an order list. It does not store camera footage, frames, captions, album art, or any other timed picture stream.

A common ProTracker-style MOD contains 31 sample slots, a 128-entry order table, pattern data, and sample data. Patterns are normally 64 rows long; their cells can hold a sample number, note period, effect, and parameter. A command can alter pitch or volume, jump to a later order position, break a pattern, delay playback, or cause a loop. The final duration therefore comes from a tracker player following the sequence, not from simply decoding a fixed audio stream.

An AVI must have at least a deliberately created visual track if the actual requirement is a movie. First select a tracker engine and render audio. Then provide a still image, graphic, waveform animation, visualizer, or ordinary video, and give it the same planned duration. Calling an audio-only export an AVI video would hide an important missing step: no image data can be recovered from MOD music.


A reproducible render begins with tracker playback decisions.

Classic tracker timing is dynamic. A conventional starting setting is speed 6 and tempo 125, with a tick lasting 2.5 divided by the tempo in seconds. Speed controls ticks per row and tempo controls their rate, but effects can change both values during a module. Position jumps, pattern breaks, loop commands, sample loops, and delayed rows can alter the route. Decide whether the AVI needs a natural ending, one pass, a stated number of cycles, or a fixed-length presentation with a clear fade.

The choice of player matters as well. OpenMPT documents that MOD files do not have space for playback settings, so a player must guess the proper playback quirks when opening one. Its current software distinguishes a ProTracker-compatible four-channel MOD option from PC extensions that can use eight channels and different frequency and resampling behavior. If a reference player and your renderer handle an edge-case effect differently, the new AVI will permanently contain one interpretation.

Write down the engine and version, compatibility setting, sample rate, channel or panning policy, gain/normalization choice, visual source, frame rate, picture size, and final-loop rule. Check a section with effects, an order transition, and the intended ending before committing the visual timeline. That record is more useful than claiming that every MOD conversion is automatically identical.


AVI Uses RIFF Chunks, Streams, and Indexes for the New Movie

AVI is a Microsoft RIFF-based container. Microsoft’s AVI RIFF reference identifies an AVI file with the FOURCC AVI in its RIFF header. Its required high-level lists are hdrl, which describes the streams, and movi, which holds the sequence data. An idx1 chunk can point to the media chunks; the OpenDML extensions also define an indx index. The container organizes already-made audio and video streams. It does not know how to play MOD patterns.

AVI compatibility is not a single condition. The video stream might use one of many codecs and the audio stream might be PCM or a compressed codec. A legacy editor, device, or import system may recognize only a narrow combination, even though another player opens the same AVI. Ask the actual receiver what it expects: codec, width and height, frame rate, audio format, maximum file size, and whether it handles OpenDML indexing for larger files. The extension offers almost none of that information.

The conversion therefore renders the tracker to sound, turns the selected picture source into frames, encodes compatible audio/video streams, and writes them into RIFF. An AVI can preserve that resulting waveform and image sequence, but it cannot restore MOD samples, rows, pattern order, or tracker effects as editable source data.


The Useful Gains Come With Clear Source-Level Losses

  • It meets video-only inputs: a MOD performance can be paired with a title card or visualizer where an application requires a movie.
  • It locks one interpretation: chosen tracker timing, panning, effects, and loop policy become ordinary audio in the AVI.
  • It supports workflow-specific codecs: AVI may suit an older tool only when its exact stream choices match that tool.
  • It adds a visual decision: source music contains no picture, so the image track must be honestly chosen and retained separately.
  • It can grow quickly: raw PCM or lightly compressed AVI streams occupy far more space than compact MOD instructions and samples.

Do not scale a small still image to a huge frame merely to make a larger file, and do not increase audio rate expecting historic 8-bit samples to gain original detail. Use settings based on the destination. If you only need a listening copy, a lossless audio render or standard audio file is more direct; AVI is justified when the receiving workflow truly needs a video container.


An AVI Receiver May Care More About Codecs Than About AVI Itself

A program that says it accepts AVI can still reject a particular AVI because it lacks the selected video or audio decoder. Test the actual receiving application, not merely one broad desktop player. For an older Windows workflow, uncompressed or PCM audio may be accepted where a newer audio codec is not; for another workflow, the opposite is true because size limits are strict. Check both streams after export and use the application’s documented requirements if they exist.

Tracker compatibility requires a different test. Open the source in the chosen tracker-oriented player, such as OpenMPT, and compare the effect-heavy passage and pattern transition with the rendered audio. A media player can verify that AVI chunks are playable, but it cannot confirm that a ProTracker quirk was interpreted as intended. Keep the original source so another engine can be used later without trying to reverse-engineer music instructions from the movie.

A fixed still image is a legitimate visual track when it is what you intend, but describe it accurately. It does not make the MOD visual media, and an AVI built from it is not footage. Store the still or project file beside the MOD and final AVI so its origin and timing can be changed without degradation later.


Diagnose Audio, Picture, and Container Problems Separately

No image, a black picture, or a short movie usually means the visual source was absent, its duration was too short, or its frames did not encode into the selected video stream. Confirm that the output has one video and one audio stream, then compare their durations. Supply a defined still, visualizer, animation, or video and rebuild the timeline. Do not try to repair a missing video stream by changing MOD sample settings; they are unrelated data types.

Wrong musical duration or an unexpected silent tail points back to tracker rendering. Inspect order positions, tempo commands, loops, and the selected ending rule. A job that stops after the first pattern may have ignored a position jump; one that seems endless may be following a deliberate loop. Re-render the audio before muxing it into AVI. If effects, pitch, or loops differ from a reference, compare player compatibility modes rather than blaming RIFF indexing.

If an application rejects the AVI, identify whether it dislikes the video codec, audio codec, dimensions, index style, or file size. The RIFF layout can be valid while a restricted receiver lacks a needed decoder. Use a small test with the target’s known requirements before committing a long looped render, and preserve the source assets for a new export.


Tracker Data Compared With an AVI Delivery Presentation

PropertyMOD sourceAVI output
Core materialSamples, patterns, effects, and an order list.Timed audio plus a selected video stream.
Picture contentNone.Must be supplied as a still, animation, or video.
Timing authorityRows, speed, tempo, jumps, and loops.Fixed stream timestamps and frame sequence.
Container layoutTracker-specific headers/pattern/sample data.RIFF AVI , hdrl, movi, and possible indexes.
Editable music structureAvailable in tracker software.Not recoverable from rendered audio.
Primary checkChosen tracker playback.Both streams in the receiving AVI application.

Practical MOD-to-AVI Questions Before You Export

Can a MOD become video without adding an image?
No. MOD music has no frames. Create or provide a visual stream if the output must be a real AVI movie.

Why does a valid AVI not open in my old program?
AVI is only the container. The program may lack the chosen audio/video decoder or reject its size, dimensions, or indexing style.

Why did the music end at the wrong time?
Review MOD order jumps, tempo, effects, loops, and the selected render cutoff in the tracker engine.

Will converting to AVI improve old module samples?
No. It only fixes a chosen render into audio and adds visuals. It cannot recover unavailable source detail.

Which files should remain after conversion?
Keep the MOD, visual source, render notes, and the AVI. They serve different purposes and avoid a second lossy rebuild later.