A pre-fader send takes its signal before the track’s 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.

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.

Adobe’s Audition routing guide documents this distinction. A send’s behaviour is not the same question as where an insert effect sits in a processing chain.

Start with one source and one destination

Before changing a complicated session, make a small test.

Use a short voice recording, its ordinary output and one send to an effect bus. Name the bus for its purpose.

Play the phrase, then lower the source track’s fader. Listen separately to the direct output and the bus return where the application permits it.

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.

Save the original project before investigating its routing.

Understand the separate paths

A send feeds another destination in addition to whatever ordinary output route the track uses.

That destination might contain an effect. The result returns through its own path and level control.

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

Draw a short route list in your notes: source, ordinary output, send destination and final output. Include any processing that matters.

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.

Choose post fader for a following effect feed

Imagine a voice with an added reverberant contribution.

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.

Test both a gradual fade and a sudden level change. Listen to what happens after the last word.

The effect’s 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.

Judge the actual result against the scene, rather than treating the routing choice as a complete sound-design decision.

Use pre fader deliberately

A pre-fader send can support a separate balance that does not follow the track fader in the same way.

That independence is useful when it is intentional. It is confusing when you expect the main fader to control everything you hear.

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.

That could serve a fictional transition, or it could be an accidental routing fault.

Check the behaviour of mutes, automation and other controls in your application. Do not assume every control behaves like the volume fader.

Work through a scene change

Picture a character speaking in a room before the film cuts to a memory.

The director wants the last phrase to recede into an effect while the direct voice becomes less prominent.

Make one test with a following send and another with an independently controlled feed. Match the initial listening balance before comparing them.

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?

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.

Diagnose a sound that will not fade

If you lower a track and still hear its content, pause before deleting the clip.

Check whether a send feeds a bus that remains audible. Look for duplicate tracks, alternate outputs or rendered effect copies.

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.

Once you find the path, decide whether it is necessary.

If the design requires it, make its level intentional. If it is accidental, correct the route and replay the full section.

Keep effects and sends distinct

“Pre-fader” can appear in more than one part of an application.

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.

Use the software’s current documentation for the control you are changing.

Do not copy another editor’s settings without understanding their route. A preset may assume a bus, output or effect configuration absent from your project.

Describe the purpose in plain language, such as “effect follows voice level”, before choosing the control.

Review the complete production

Restore the other tracks and listen in context. A carefully designed effect can still cover dialogue or feel too prominent beside music.

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.

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.

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

Use a routing checklist

Before approving the mix, confirm that:

• Each send has a named destination and a reason to exist.
• The effect feed responds as intended when the track level changes.
• Any independent path is deliberate.
• Mute and automation behaviour have been tested.
• The final export contains the expected transition.

When selecting RouteNote Licensing sound effects, begin with a source that suits the scene. Confirm the applicable terms for processing it, and choose routing that makes the intended sound easy to control.