RPMC Music
RPMC stores editable tracker music. It preserves the song structure and sample assets needed by a player, rather than compressing a finished audio recording.
A little technical detail
Sparse sample and instrument slots avoid storing empty entries. Orders, patterns, events, key maps, names, channel mixing and surround state are serialized through the existing Music_Format song contract. A compatible tracker renderer supplies playback.
Format definitionHistoryPureBasic modulePureBasic source bundleC sourceC headerJavaScript sourceC / JavaScript bundlePort contracts
Comparison & examples
The release-corpus song is a structured music fixture. Comparing its size with WAV or MP3 would compare an editable song with a rendered performance and would be misleading. The example can be decoded, exported and played locally through the tracker renderer.
| Representation | Download / size | Decoded preview |
|---|---|---|
| Example song | 4,172 bytes |
Encode & decode
Exchange supports standard 31-sample MOD and XM 1.04 with PCM samples. The shared tracker contract uses 8-bit sample data; imported 16-bit XM samples are reduced accordingly. MOD/XM exports cannot retain every RPMC setting, including surround, mute state, messages and extended instruments. MOD rejects unrepresentable events. Keep RPMC for the complete song; browser playback uses libopenmpt and requires HTTPS or localhost. Processing stays in your browser. Input limit: 64 MiB.
No file loaded.