Why does pygame.mixer.music end event not fire?

You must call mixer.music.set_endevent() with a custom event id, then poll pygame.event.get() each frame to receive it. The end event also does not fire if music is set to loop infinitely (loops=-1) because it never reaches end.

How do I detect when pygame music finishes playing?

Define an event id like SONG_END = pygame.USEREVENT + 1, call pygame.mixer.music.set_endevent(SONG_END), then in your main loop check for event.type == SONG_END inside your event handling. The event posts when the current track finishes, including each loop iteration if loops is finite.

Why does my song end event fire too early or too late?

The end event fires when the audio buffer drains, not when the perceived audio ends. If your file has trailing silence, the event fires after the silent tail. Trim trailing silence in audio editing or pre-compute the actual play length and use a timer alongside the event.

Fix: Pygame mixer.music End Event Not Firing

Quick answer: Pygame end-of-music events require mixer.music.set_endevent(SONG_END) and active polling via pygame.event.get(). The event also never fires when play(loops=-1) is used, because the music never ends. Use get_busy() or finite loops if you need to detect completion.

Here is how to fix Pygame mixer.music end events that never deliver. You expect a callback when the song finishes so you can queue the next track, but the loop simply ends with silence and your handler never runs. Pygame uses an event-queue model for music end notifications; you have to set the event id and consume it from the queue.

The Symptom

You set up music playback, expect to know when the track ends, and nothing fires. The track plays out, the mixer goes silent, and your code keeps polling without ever advancing to the next song.

What Causes This

set_endevent never called. Without it, pygame does not post any event when music ends. Music quietly stops and the queue stays empty.

Event queue not polled. Even if set_endevent is configured, the event sits in the queue until pygame.event.get() or pygame.event.poll() consumes it.

Looping infinitely. play(loops=-1) repeats forever — the track never reaches end, so no end event ever posts.

Event id collision. If your code uses USEREVENT directly without an offset, multiple subsystems may post events with the same id and stomp on each other.

The Fix

Step 1: Define a unique end event id.

import pygame

pygame.init()
pygame.mixer.init()

SONG_END = pygame.USEREVENT + 1
pygame.mixer.music.set_endevent(SONG_END)

Use USEREVENT + N where N is unique per subsystem. USEREVENT + 1 for music end, USEREVENT + 2 for a custom timer, and so on.

Step 2: Poll for the event.

pygame.mixer.music.load("assets/song.ogg")
pygame.mixer.music.play()

playlist = ["song1.ogg", "song2.ogg", "song3.ogg"]
idx = 0

running = True
while running:
    for event in pygame.event.get():
        if event.type == pygame.QUIT:
            running = False
        elif event.type == SONG_END:
            idx = (idx + 1) % len(playlist)
            pygame.mixer.music.load(playlist[idx])
            pygame.mixer.music.play()

Step 3: Use finite loops if you also want event firing.

# loops=-1 -> never ends, no end event
# loops=0  -> play once, end event after
# loops=2  -> play three times, end event after the third
pygame.mixer.music.play(loops=2)

Step 4: Fall back to get_busy polling. If you cannot rely on events (for example, if your code is in a thread without an event loop), poll directly:

if not pygame.mixer.music.get_busy():
    # Music finished, advance playlist
    next_track()

get_busy() returns False when no music is playing, including after the track ends. It works without event-queue polling but does not give you exact timing.

Step 5: Trim trailing silence in audio. If the end event fires later than expected, your file probably has silent tail. Use Audacity or ffmpeg to trim:

ffmpeg -i input.ogg -af silenceremove=stop_periods=-1:stop_duration=0.1:stop_threshold=-50dB output.ogg

Subtleties of get_busy

Calling pygame.mixer.music.pause() makes get_busy() return False even though the track is paused, not finished. Use get_pos() in addition to verify whether the track has actually ended (returns -1 when no track loaded, or 0+ for current ms position).

Streaming formats like OGG can have buffer-related delays at end. The end event posts when the streaming buffer drains, which is typically a few hundred milliseconds after the perceived audio end. For frame-perfect transitions, blend the next track with a short crossfade rather than waiting for end exactly.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Pygame, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Pygame. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Pygame-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within Pygame, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Set the event id, poll the queue, avoid infinite loops if you want to be told when it ends.”

Related Issues

For other Pygame audio issues, see Joystick Not Detected. For draw order issues, see Sprite Group Draw Order.

USEREVENT + 1. set_endevent. Poll the queue. Music plays end-to-end and tells you about it.