Guide

Why is my export silent? Fixing a silent bounce or render

You bounced or exported a track and the file came back silent, or only part of it made a sound. The export ran without an error, which is why it is confusing. Nearly every case is one of a few ordinary things, and one of them catches self-playing and generative instruments in particular.

This is DAW-agnostic, with Logic Pro named as the example. The idea is the same in every host; only the menu names differ, so check the wording in your own bounce or export dialog.

Why is my exported track silent?

Because something stopped the audio from reaching the file, and the export ran anyway without warning you. A bounce or render only writes what actually arrives at the output it is reading, so if nothing arrives, you get a silent file that is exactly as long as you asked for. Almost every silent or half-silent export is one of these:

  1. A track is muted, or a solo is left on. One muted track, or a solo switched on somewhere else in the project, can silence the whole export or drop the part you wanted.
  2. The export range covers empty bars. If the cycle or the selected range sits over a gap, the render is the right length and completely silent.
  3. The audio is routed away from the main output. A track or group feeding a bus or submix that never reaches the main stereo output can move the meters while nothing lands in the file.
  4. The wrong track is being exported. Bouncing or exporting one selected track, rather than the mix, gives you only that track, which is silent if it was the empty one.
  5. It is a self-playing or generative instrument bounced offline. This is the big one, and it has its own section below.

Work down the checklist next and stop as soon as sound appears.

The quick checklist

Run these in order and stop the moment the export makes a sound. They are listed by how often each one is the real cause.

  1. Clear every mute and solo. Unmute all tracks, then make sure no solo is left on anywhere. A stray solo is easy to miss because the track it isolates may be nowhere near the one you are exporting.
  2. Check the range sits over real audio. Confirm the cycle region, or the selection you are exporting, actually covers bars that contain sound, not the silence before or after the take.
  3. Follow the routing to the main output. Make sure the track, and any bus or submix it feeds, ends up at the main stereo output the bounce is reading, and that nothing in that path is muted or turned down.
  4. Confirm what you are exporting. Check whether you are bouncing the whole mix or a single selected track, and that the selected one is the track you meant.
  5. If the sound is a self-playing or generative instrument, bounce it in realtime. An offline bounce can capture silence from these. This is covered next, and it is the most common cause for instruments that play themselves.

Why does a self-playing or generative instrument bounce silent?

Because an offline bounce renders faster than realtime, and a self-playing or generative instrument makes its sound against the live audio clock. When the host renders offline it is not playing the project in real time, it is calculating the result as fast as it can, and an instrument that generates its notes and audio as time passes does not get the running clock it depends on. So it produces nothing, or only a fragment, and the file comes out silent even though the instrument plays perfectly when you press play.

A plain recorded audio region is fixed samples, so it renders the same whether the bounce is offline or in real time. A self-playing instrument is not fixed. It is composing and producing audio while the transport moves, and that only happens properly when the clock advances in real time. A faster-than-realtime render skips past that, which is where the silence comes from.

The fix that matters

Bounce it in realtime. Use your DAW's realtime or online bounce option instead of the default offline one, or record the instrument's output live to an audio track and export that. In real time the instrument runs against the live clock exactly as it does on playback, so the whole performance is written to the file. This one switch resolves almost every silent bounce of a self-playing or generative instrument, and it is the single most common support question about them.

How do I bounce it in realtime?

Turn on the realtime option in your DAW's bounce or export dialog, or record the instrument's output onto an audio track and export that instead. Either way the instrument gets played through in real time, which is what it needs.

In Logic Pro, the Bounce dialog offers Realtime as an alternative to Offline. Choose Realtime and Logic plays the project through as it writes the file, so a self-playing instrument is captured live rather than skipped. Other hosts have the same idea under their own names, an online or realtime bounce as opposed to a faster-than-realtime one, so look for that wording in your host's bounce or export dialog rather than accepting the default offline render.

If you cannot find a realtime option, the method that always works is to record the instrument's output onto a plain audio track. Route the instrument to an audio track, arm it, play the project through once in real time so it records what it plays, then export that recorded audio. Because it is now ordinary samples, it exports cleanly whether the render is offline or online.

One trade to expect: a realtime bounce takes as long as the music itself, because it plays through in full. That is the cost of capturing an instrument that plays itself, and it is worth it for a file that is not silent.

A self-playing instrument, if you want to hear this in practice

Most of this page is about the general case. The one place it bites hardest is an instrument that composes on its own, because that is exactly the kind of sound an offline bounce tends to drop.

One of ours, since you are here

ARGISH is a self-playing drone synth. You set a mood and a key, build a progression on the chord wheel, and it composes on its own, so there is music moving before you have written a note. Because it composes against the live clock, it is exactly the kind of instrument this page is about: bounce it with your DAW's realtime or online option, or record its output to a track, and the whole performance lands in the file perfectly. It ships as an Audio Unit, a VST3, an AAX for Pro Tools, and a standalone app.

Hear the whole thing free in your browser first, no install and no account.

More guides like this

We write these when there is something worth writing down. One email when a new one lands or a new Tunary instrument ships. No newsletter, no schedule.

See all guides