{"id":11246,"date":"2026-10-30T08:00:00","date_gmt":"2026-10-30T08:00:00","guid":{"rendered":"https:\/\/licensing.routenote.com\/blog\/?p=11246"},"modified":"2026-10-29T11:28:42","modified_gmt":"2026-10-29T11:28:42","slug":"pre-fader-post-fader-sends","status":"publish","type":"post","link":"https:\/\/licensing.routenote.com\/blog\/pre-fader-post-fader-sends\/","title":{"rendered":"Pre-Fader vs Post-Fader Sends: A Practical Audio Guide"},"content":{"rendered":"\n

A pre-fader send takes its signal before the track\u2019s volume fader; a post-fader send takes it after that fader. The practical question is whether changing the main track level should also change the signal feeding another destination.<\/p>\n\n\n\n

Use a post-fader send when you want an effect feed to follow track-level changes. Consider a pre-fader send when you intentionally need a separate balance. Always test the complete route in your application.<\/p>\n\n\n\n

Adobe\u2019s Audition routing guide<\/a> documents this distinction. A send\u2019s behaviour is not the same question as where an insert effect sits in a processing chain.<\/p>\n\n\n\n

Start with one source and one destination<\/h3>\n\n\n\n

Before changing a complicated session, make a small test.<\/p>\n\n\n\n

Use a short voice recording, its ordinary output and one send to an effect bus. Name the bus for its purpose.<\/p>\n\n\n\n

Play the phrase, then lower the source track\u2019s fader. Listen separately to the direct output and the bus return where the application permits it.<\/p>\n\n\n\n

The test shows what the route does. A button label alone can be harder to interpret when several outputs, automation lanes and effects are active.<\/p>\n\n\n\n

Save the original project before investigating its routing.<\/p>\n\n\n\n

Understand the separate paths<\/h3>\n\n\n\n

A send feeds another destination in addition to whatever ordinary output route the track uses.<\/p>\n\n\n\n

That destination might contain an effect. The result returns through its own path and level control.<\/p>\n\n\n\n

This means a low source-track fader does not necessarily explain every sound you hear. Another path may still carry the signal.<\/p>\n\n\n\n

Draw a short route list in your notes: source, ordinary output, send destination and final output. Include any processing that matters.<\/p>\n\n\n\n

If two unexpected copies of the source are audible, check routing before adding processing to conceal the result. The problem may be an unintended path rather than the source recording.<\/p>\n\n\n\n

Choose post fader for a following effect feed<\/h3>\n\n\n\n

Imagine a voice with an added reverberant contribution.<\/p>\n\n\n\n

If the creative intention is for the effect feed to reduce as you lower the track, a post-fader send is a useful starting point.<\/p>\n\n\n\n

Test both a gradual fade and a sudden level change. Listen to what happens after the last word.<\/p>\n\n\n\n

The effect\u2019s own response matters too. Audio already feeding a reverberation can continue as a tail; post-fader routing does not mean all existing effect output vanishes instantly.<\/p>\n\n\n\n

Judge the actual result against the scene, rather than treating the routing choice as a complete sound-design decision.<\/p>\n\n\n\n

Use pre fader deliberately<\/h3>\n\n\n\n

A pre-fader send can support a separate balance that does not follow the track fader in the same way.<\/p>\n\n\n\n

That independence is useful when it is intentional. It is confusing when you expect the main fader to control everything you hear.<\/p>\n\n\n\n

For example, lowering the direct voice may leave an effect feed active. The result can sound like the voice has moved into a distant space.<\/p>\n\n\n\n

That could serve a fictional transition, or it could be an accidental routing fault.<\/p>\n\n\n\n

Check the behaviour of mutes, automation and other controls in your application. Do not assume every control behaves like the volume fader.<\/p>\n\n\n\n

Work through a scene change<\/h3>\n\n\n\n

Picture a character speaking in a room before the film cuts to a memory.<\/p>\n\n\n\n

The director wants the last phrase to recede into an effect while the direct voice becomes less prominent.<\/p>\n\n\n\n

Make one test with a following send and another with an independently controlled feed. Match the initial listening balance before comparing them.<\/p>\n\n\n\n

Listen through the whole transition. Does the final word remain understandable? Does the effect suggest the intended change, or merely sound like an accidental echo?<\/p>\n\n\n\n

Keep the simpler version if both achieve the same result. Name any independent effect automation so a later editor can understand why the direct voice and effect differ.<\/p>\n\n\n\n

Diagnose a sound that will not fade<\/h3>\n\n\n\n

If you lower a track and still hear its content, pause before deleting the clip.<\/p>\n\n\n\n

Check whether a send feeds a bus that remains audible. Look for duplicate tracks, alternate outputs or rendered effect copies.<\/p>\n\n\n\n

Mute and inspect paths one at a time on a test copy, using the application’s documented controls. Avoid changing several routes together because that makes the cause harder to identify.<\/p>\n\n\n\n

Once you find the path, decide whether it is necessary.<\/p>\n\n\n\n

If the design requires it, make its level intentional. If it is accidental, correct the route and replay the full section.<\/p>\n\n\n\n

Keep effects and sends distinct<\/h3>\n\n\n\n

\u201cPre-fader\u201d can appear in more than one part of an application.<\/p>\n\n\n\n

A send position describes where a separate feed is taken. An effect position describes where processing occurs in a path. Those settings can interact, but they are not interchangeable labels.<\/p>\n\n\n\n

Use the software\u2019s current documentation for the control you are changing.<\/p>\n\n\n\n

Do not copy another editor\u2019s settings without understanding their route. A preset may assume a bus, output or effect configuration absent from your project.<\/p>\n\n\n\n

Describe the purpose in plain language, such as \u201ceffect follows voice level\u201d, before choosing the control.<\/p>\n\n\n\n

Review the complete production<\/h3>\n\n\n\n

Restore the other tracks and listen in context. A carefully designed effect can still cover dialogue or feel too prominent beside music.<\/p>\n\n\n\n

Check the route at the beginning, through the level change and after the last source event. Review the exported file as well as session playback.<\/p>\n\n\n\n

Keep a reference of the approved transition and retain the editable session. That makes it easier to distinguish a later routing error from a requested creative change.<\/p>\n\n\n\n

There is no requirement to use sends in every project. A simple edit may need only a direct path and a clear level decision.<\/p>\n\n\n\n

Use a routing checklist<\/h3>\n\n\n\n

Before approving the mix, confirm that:<\/p>\n\n\n\n