Background Music Management and Loops

Introduction: Background Music in Game Design

Background music (often abbreviated as BGM) is one of the most impactful elements shaping a player's experience. While sound effects (SFX) communicate immediate actions like shots, jumps, or impacts, music establishes the emotional tone, dramatic tension, and overall pacing of a level. In our retro 2D platformer, an upbeat, rhythmic track conveys fluidity and momentum during gameplay, while a calmer, ambient piece on the main menu sets the stage before starting a run.

From a software development perspective, playing music presents very different challenges than triggering a half-second sound effect. Music tracks are long audio files, typically lasting anywhere from one to three minutes. If configured incorrectly, they can consume excessive amounts of system RAM or introduce noticeable stutters when looping. Achieving an infinite, seamless loop without silent gaps or abrupt cutoffs when switching rooms or restarting a level requires a solid understanding of GameMaker's audio engine and a centralized management system.

Sound Asset Configuration: Streaming vs. Preloading

In GameMaker, both short sound effects and full musical compositions are imported into the Asset Browser inside the Sounds folder. However, their internal settings must be handled completely differently. When importing an audio file (typically in .ogg or .mp3 format for music), the Sound Editor allows you to configure its compression mode and memory loading behavior.

For sound effects, the standard approach is to decompress the entire audio file into RAM when the game boots or when loading a room, ensuring zero-latency playback upon triggering. If you applied that same strategy to a three-minute uncompressed stereo track, it would consume tens of megabytes of RAM per song. For background music, streaming is the preferred solution. With streaming enabled, GameMaker keeps only a small temporary buffer in memory and decodes the compressed file on the fly from disk or storage as playback progresses.

To configure your background track in GameMaker, double-click the sound asset (for example, snd_musica_nivel1). In the Inspector or Sound Editor window, locate the 'Type' dropdown and select 'Compressed - Streamed'. Set the compression bitrate between 128 kbps and 192 kbps, which provides an ideal balance between acoustic fidelity and file size for a 2D platformer.

Looping Playback with audio_play_sound

The core function for playing any sound in GML Code is audio_play_sound(). In modern versions of GameMaker, this function accepts both basic positional parameters and extended arguments for gain, offset, and pitch. Its traditional signature is structured as follows:

audio_play_sound(index, priority, loop, [gain], [offset], [pitch], [listener_mask]);

Let's break down each essential parameter involved in playing background music: 1. index: The identifier of the audio asset created in the Asset Browser, such as snd_musica_menu or snd_musica_nivel1. 2. priority: An integer value (typically between 0 and 100). If the game reaches the hardware channel limit for simultaneous voices, GameMaker drops lower-priority sounds in favor of higher-priority ones. Background music should have a high priority (such as 10 or 50), whereas footsteps or coin pickup sounds generally carry low priority (1 or 2). 3. loop: A boolean value (true or false). Passing true instructs the audio engine to immediately restart the track once it reaches the end, looping indefinitely until your code explicitly stops it.

It is crucial to understand what this function returns: audio_play_sound does not return a boolean indicating success; instead, it returns a Sound Instance ID (a unique handle for that specific playing voice). GameMaker differentiates between the Sound Asset (the blueprint in the Asset Browser) and the Sound Instance (the active playback stream). Storing this ID in a variable allows you to adjust the volume of that specific track, pause it, or stop it later without affecting any other sound in the game.

The Duplication Problem and the Audio Controller Object

A common beginner mistake in game development is placing the audio_play_sound call directly inside the player object's Create event (obj_player) or in the Room Creation Code. If music playback is tied to the player, every time the player loses a life and the level reloads via room_restart(), a new player instance is created, triggering playback again. The result is an unbearable cacophony where two or more out-of-sync copies of the same song play simultaneously.

The standard architectural solution is to centralize audio management within a single dedicated object: obj_audio_controller. This object is marked as Persistent (by checking the 'Persistent' box in its Object Properties). Persistent objects survive room transitions; once spawned in the game's initial room, they persist in the background across all subsequent levels without being destroyed or re-created.

Technical Implementation of obj_audio_controller

Next, we will implement a complete music management system in GML Code. Create the obj_audio_controller object, enable its Persistent property, and set up two events: the Create event (where we initialize tracking variables) and the Room Start event (which executes automatically whenever entering a new room).

// ========================================================
// OBJECT: obj_audio_controller
// EVENT: Create
// ========================================================

// Variable to store the sound instance ID of active music
musica_actual_instancia = -1;

// Variable to track which audio asset is currently playing
musica_actual_asset = noone;

// Default baseline music volume (range from 0.0 to 1.0)
volumen_musica = 0.8;

In the Create event, we set musica_actual_instancia to -1 (indicating no active instance) and musica_actual_asset to noone (a GML keyword representing the absence of an asset or instance). Next, we will use the Room Start event to dynamically determine which track should play based on the active room, avoiding restarting the melody if the incoming room shares the same music.

// ========================================================
// OBJECT: obj_audio_controller
// EVENT: Other -> Room Start
// ========================================================

// Local variable to determine which track belongs to this room
var _musica_a_reproducir = noone;

// Evaluate which room is currently active
switch (room)
{
    case rm_menu:
        _musica_a_reproducir = snd_musica_menu;
        break;
        
    case rm_nivel_1:
    case rm_nivel_2:
        // Both gameplay rooms can share the same action theme
        _musica_a_reproducir = snd_musica_nivel1;
        break;
        
    case rm_game_over:
        _musica_a_reproducir = snd_musica_derrota;
        break;
        
    default:
        _musica_a_reproducir = noone;
        break;
}

// Check if the requested music differs from what is already playing
if (_musica_a_reproducir != musica_actual_asset)
{
    // 1. If music is already playing, stop it
    if (audio_is_playing(musica_actual_instancia))
    {
        audio_stop_sound(musica_actual_instancia);
    }
    
    // 2. If the new room requires music, start it in a continuous loop
    if (_musica_a_reproducir != noone)
    {
        // Priority 10 ensures playback persistence, loop = true
        musica_actual_instancia = audio_play_sound(_musica_a_reproducir, 10, true);
        
        // Apply the desired volume to the newly spawned instance
        audio_sound_gain(musica_actual_instancia, volumen_musica, 0);
        
        // Update tracked asset record
        musica_actual_asset = _musica_a_reproducir;
    }
    else
    {
        // If the room has no assigned music, reset variables
        musica_actual_instancia = -1;
        musica_actual_asset = noone;
    }
}

Take note of the conditional check `if (_musica_a_reproducir != musica_actual_asset)`. When the player transitions from `rm_nivel_1` to `rm_nivel_2`, both rooms request `snd_musica_nivel1`. Because the requested asset matches the one already running, the block does not interrupt playback. The track continues playing uninterrupted across the room transition without resetting its tempo, delivering a polished and immersive player experience.