Looping a sound

From Valve Developer Community
Jump to: navigation, search
English (en)Русский (ru)

A looped sound will repeat endlessly without any gap between its end and start. It is up to the sound artist to ensure that the end and start of the file match up however, or there will be a "pop" as the waveform jumps from one shape to another.

GoldSrc GoldSrc and Source Source detect looped sounds ONLY through cue points embedded in the file. This is a WAV-only feature, so MP3s cannot be looped. Microsoft ADPCM compressed WAVs can be looped, but due to the way they are encoded, there may a pop when the sound restarts if the sound is shorter than a few seconds.

Note.pngNote:Source 2 Source 2 supports looping both WAV and MP3, but only S&box S&box's tools can set the looping flag in a VSND for MP3 files; first-party Valve tools still rely upon WAV cues points to determine when a VSND should loop.
Note.pngFix:With custom audio backends, it is theoretically possible to loop filetypes other than WAV. Compressed audio formats usually have a small decoding delay upon restarting a track, which can appear as a small pop or stutter, with MP3 being worse due to its fixed frame size and Ogg Vorbis being the cleanest. This can theoretically be avoided for any compressed format, including MP3.
Note.pngNote:There is no need to mark a sound as looping when playing it, but if using ambient_generic you will find that the "Is NOT Looped" flag must be set correctly if you want to stop the sound after it starts!
Warning.pngWarning:Left 4 Dead 2 During development: editing the contents of an existing sound file stored in your campaign's sound.cache will not show any change until the sound cache is rebuilt! See Creating a sound.cache file or L4D2 Custom Sound and Music Tutorial for further instructions.

Looping a WAV

These free programs can add cue points to a WAV:


Open Goldwave and open the sound you want to loop. Click the cues icon. (Cues button.jpg) Then in the new window click on the New button and add a cue point At Start. Then click New for another cue point and add a point At End. So it looks similar to this:

Cue dialog.jpg


Open Wavosaur and open the sound you want to loop. Go to Tools > Loop > Create loop points. It should create loop points. You can change their positions by dragging them.

After that, click "Save" or "Save As".

If the sound doesn't loop, then go to Tools > Markers > Create marker, or RMB on the track and click Create marker.

Move the first marker to the start and second one to the end.

After that, click "Save" or "Save As".

Warning.pngWarning:Wavosaur does not support ADPCM-compressed WAV files; attempting to open one will result in the application crashing!
Icon-Important.pngImportant:In GoldSrc GoldSrc, the sound may fail to loop if two cue points are set via the Create loop points function in Wavosaur. If this happens, try setting only the starting cue by using a marker instead (Tools > Loop > Create marker).

With a hex editor

Appending the following bytes to the end of a non-looping WAV file will make it loop in its entirety:

63 75 65 20 1C 00 00 00 01 00 00 00 01 00 00 00 00 00 00 00 64 61 74 61 00 00 00 00 00 00 00 00 00 00 00 00
Tip.pngTip:If using Linux or macOS, put the above into a file named cue.bin, then run cat my_nonlooping_sound.wav cue.bin > my_looping_sound.wav.

The bash shell script used to generate the above cue chunk is provided below, based upon documentation from recordingblogs.com.


# Wave file cue chunk according to https://www.recordingblogs.com/wiki/cue-chunk-of-a-wave-file
# Original script by SavageX; permission is granted to modify as needed.

ECHO="echo -en"

function append_bytes() {
    $ECHO $1 >> $OUT

function append_cue() {

    # chunk ID, "cue "
    append_bytes "cue\x20"

    # size of the chunk: (12 + 24) - 8 = 28
    # Why -8? ID and size don't count.
    append_bytes "\x1C\x00\x00\x00"

    # number of data points: 1
    append_bytes "\x01\x00\x00\x00"

    # ID of data point: 1
    append_bytes "\x01\x00\x00\x00"

    # position: If there is no playlist chunk, this is zero
    append_bytes "\x00\x00\x00\x00"

    # data chunk ID
    append_bytes "data"

    # chunk start: 0
    append_bytes "\x00\x00\x00\x00"

    # block start: 0
    append_bytes "\x00\x00\x00\x00"

    # sample start: 0
    append_bytes "\x00\x00\x00\x00"

rm -f cue.bin
append_cue cue.bin

Cue location

Your cues do not have to be at the start and end of the file. If you place them in the middle Source will start playing the sound normally, then when it reaches the end cue will loop back to the start cue. From then on only what's between the cues will play.

Warning.pngWarning:It seems that the end cue maybe doesn't have any effect at all. See the Discussion page for more details.
Warning.pngWarning:ADPCM-compressed WAV files may ignore the location of the start cue when looping, and loop the entire sound instead!

This can be used to give a sound a "winding up" effect that only plays once (e.g. a motor starting).

Looping an MP3

The name of the ambient_generic is "MP3".

In Source Source, MP3 files can't be looped with start/end queues like a WAV. A logic_timer can be a good workaround; have it start playing the sound again after it has fully played (or has played to the point desired).

This could also be done using User I/O from the ambient_generic to itself, and an input delay.

Note.pngNote:In singleplayer games prior to Portal 2 Portal 2, pausing the game pauses entity I/O but not music, causing the timer to go out of sync and leave a gap at the end of the song before looping.

See also

External links