# DaVinci Resolve Clip Volume vs Track Volume

> **Quick answer:** DaVinci Resolve clip volume vs track volume comes down to scope: clip volume changes one timeline clip, while track volume changes the combined level of clips on that audio track. Use clip volume for individual takes, track volume for a whole dialogue, music, or effects track, and track automation when its level needs to change over time.

*Published by [TryUncle](https://tryuncle.com) — the on-screen assistant that teaches DaVinci Resolve on your own screen.*
*Updated 2026-10-22 · DaVinci Resolve 21.1 (September 2026) · Canonical: https://tryuncle.com/learn/davinci-resolve/davinci-resolve-clip-volume-vs-track-volume*

I use one quick test when a mix feels wrong: ask whether the problem belongs to one clip or to the whole track. That small distinction prevents a quiet interview line from turning into a louder music bed, or one loud sound effect from forcing every other effect down. We run a professional video-editing community of more than 100,000 members, and this question comes up whenever editors move from cutting clips to shaping a mix.

As of October 2026, DaVinci Resolve 21.1 is the current release listed by Blackmagic Design. The central distinction remains easy to state: clip volume belongs to an individual timeline clip; track volume belongs to the audio track that carries clips toward a bus. Blackmagic's Fairlight documentation describes independent clip volume controls, clip gain lines and track faders. Those are different control points, so they solve related but not identical problems.

## What is the difference between clip volume and track volume in DaVinci Resolve?

Clip volume changes one selected timeline clip, while track volume changes the combined output of the clips on one audio track. Think of clip volume as an individual correction and track volume as the track's shared position in the mix.

In Resolve, the visible white line across an audio clip is its clip gain line. Dragging that line changes the clip level. The clip Inspector also exposes a Volume control for the selected clip. In Fairlight, the mixer has a channel strip for each timeline audio track, and its fader changes that track's level. Blackmagic lists clip controls and track channel-strip faders as separate tools in its [Fairlight overview](https://www.blackmagicdesign.com/products/davinciresolve/fairlight).

A useful mental model is a row of containers. Each clip is a container with its own level setting. The track is a larger channel through which those clips play. Lowering a clip affects that container. Lowering the track affects the sound coming from all the containers on it.

| Control | What it changes | Best first use | What it does not do |
| --- | --- | --- | --- |
| Clip Volume in Inspector | The selected timeline clip's level | Correct one unusually quiet or loud clip | It doesn't set the whole track's mix position |
| Clip gain line | The selected clip, or a shaped portion if keyframed | Make a quick visual correction in the timeline | It doesn't automatically balance other clips |
| Track Volume / track fader | The audio track's combined level | Set dialogue, music, or effects against other tracks | It doesn't fix a single clip's bad balance relative to its neighbors |
| Track fader automation | Track level as it changes over time | Ride a dialogue bed or music track through a sequence | It doesn't replace per-clip cleanup when clips vary widely |
| Bus or main output level | A group of routed tracks or the final mix path | Adjust a group or output after individual tracks are balanced | It doesn't isolate one clip or one track |

The names can be confusing because editors casually say “turn the volume down” for any of these moves. Resolve's controls are more specific. The key question is scope: one clip, one track, a group of tracks, or the final output?

**Clip volume is the right control when one timeline clip is out of balance with the other clips around it.**

If a sequence contains five dialogue clips on A1 and the third clip is much quieter, change that clip first. If all five clips sound equally too loud against music, the track fader is a more direct place to set their shared level. You may still need both: clip gain to even the five lines, then the track fader to place the dialogue track in the mix.

A clip can also have fades and level keyframes. That means “clip volume” does not always mean one flat value from beginning to end. You can shape an individual clip's level where an edit or performance calls for a local change. Meanwhile, track automation can shape the entire track's fader level over time. Both can create a changing level, but their scope differs.

When people ask whether clip volume or track volume is “better,” the answer depends on the job. Neither is the master control. Clip adjustments handle differences between clips. Track adjustments handle the relationship between a track and everything else. Automation handles a relationship that changes during playback.

## Why does changing track volume affect every audio clip in DaVinci Resolve?

Changing track volume affects every clip on that track because the fader controls the shared track signal, not a single clip. If you need one clip to move independently, adjust that clip's volume or move it to a track with a different mix role.

A track is a practical grouping tool. It may hold a run of interview edits, a music bed, a collection of sound effects, or multiple takes that should share processing and a fader. When you move its fader, you change the track as a unit. That's useful when the whole dialogue track is too prominent, but confusing when only one edit is the problem.

Imagine a short social video with three narration clips on A1 and music on A2. The second narration clip was recorded farther from the microphone. If you lower A1, the good first and third lines also get quieter. If you raise A1 to rescue the second line, those already-clear lines may become too loud. The local problem calls for a local control: adjust clip gain on the second clip, then use A1's fader to set the overall voice level.

Now imagine all three lines are consistent, but the music masks them. Lower A2's track fader. You could lower each music clip one by one, but that spreads one mix decision across many edits. The track fader expresses the actual intent: keep this bed quieter as a group.

The distinction is especially useful when the same sound appears in many edits. A video may contain a sequence of footsteps, impacts, or room tone clips on one effects track. Clip levels can correct the odd recording that is much louder. The track fader can then bring the full effects layer up or down against dialogue. That gives you both local consistency and global balance.

#
## How can I tell which scope is wrong?

Listen to the clips in context and compare them with their neighbors. If one clip jumps out while the others on that track feel right, the clip is the likely target. If every clip on the track is too loud or too quiet against the rest of the mix, start with the track fader.

A waveform can provide a clue, but it cannot decide the mix for you. A large waveform may come from a loud source, but perceived loudness also depends on frequency content, transient peaks, background noise, and the playback system. A small waveform can still be intelligible if the recording is clean and close. Use the meters to see signal level and your ears to judge whether the element serves the scene.

This is why a universal number for “dialogue should be at X” is misleading without knowing the destination, the rest of the mix, and the measurement method. Work at a consistent monitoring level where possible, keep an eye on the bus and output meters, and make decisions in context. Clip and track controls are relative mix tools. They do not guarantee a platform's loudness target on their own.

## How do I change only one audio clip in DaVinci Resolve?

To change one audio clip, select it and adjust the clip's Volume control in the Inspector or its gain line in the timeline. Both target the clip, so other clips on the same track remain at their own clip levels.

The Inspector is the clearest option when you want a numeric value or need to confirm the selected clip. Select the timeline audio clip, open the Inspector, and look for the audio Volume control. Move the slider or enter a value if the field accepts direct entry in your version and layout. Blackmagic's Resolve 20 Fairlight guide demonstrates adjusting a timeline clip with the Inspector's volume slider and entering a typed value. The guide also describes double-clicking a control name to reset it in that workflow. Treat exact interface labels and presentation as version-sensitive, and consult the guide matching the release you're using.

The gain line is usually faster when you can see the clip clearly. Blackmagic describes a horizontal clip gain line in the upper portion of a timeline audio clip in its [Fairlight Audio Guide to DaVinci Resolve 20](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveFairlightAudioPost.pdf). If you don't see it, the guide's workflow includes the Fairlight menu command “Show Clip Gain Line.” The line's vertical movement changes the clip level; make a small move, play the cut, and listen before making another.

On the Edit page, the Inspector is often easiest for precise selection and a simple level move. The Fairlight page is more comfortable when you need a larger view of waveforms, meters, automation and the mixer. The same scope principle applies whichever page you use.

#
## What if only part of the clip is too loud?

Use a level change that is limited to the offending section, or split the clip at the boundaries and adjust only the middle piece. A whole-clip gain move will lower the quiet parts along with the loud part.

For example, an interview answer may be steady except for a laugh or a word shouted toward the end. If the change is brief and the surrounding level is right, add clip-level keyframes or split the clip around the outlier and lower that short region. Make transitions gradual enough that the correction doesn't sound like an abrupt dip. Always audition the edit with handles before and after the changed region.

There are trade-offs. A split makes the edit visible and easy to revisit, but creates more timeline pieces. Keyframes keep the timeline compact, but a hidden point can be missed later if you are scanning quickly. Pick the approach that makes the adjustment understandable to the next person opening the project, including you next week.

#
## Why did moving the clip gain line change the waveform?

Resolve can display a waveform that responds visually to clip-level gain adjustments, so the waveform may grow or shrink even though the source media has not been rewritten. The timeline's visual presentation is not proof that the original recording file was destructively altered.

That difference matters for confidence and for troubleshooting. Clip volume is a project edit, not a command to overwrite the source file. The Resolve 20 Fairlight guide describes the waveform changing as the clip level changes during its exercise. The edit remains part of the project, and the source media stays available for other edits. A rendered export, of course, contains the audible result of your mix.

If the waveform does not visibly change in your layout, don't infer that the adjustment failed. Waveform display settings, zoom and version behavior can affect what you see. Play the clip, watch the meters, and check the Inspector value or gain line position.

## When should I use the track fader instead of clip volume?

Use the track fader when the clips on one track are already reasonably balanced with one another, but the whole track needs to sit higher or lower in the mix. The fader is a shared move across that track's combined output.

Suppose a podcast interview has twenty edits on one dialogue track. The cuts are consistent, but the whole conversation feels buried under a music bed. Moving the dialogue track fader is easier to understand and maintain than changing twenty clip values. You can then lower the music track as needed and listen to both together.

A track fader is also a strong starting point when you are organizing a mix by roles. Put dialogue on one track, music on another, and effects on a third when those categories need separate control. The faders become a compact mix panel: one move for speech, one for music, one for effects. This setup also supports clearer routing and automation later.

That does not mean each category must always have exactly one track. Multiple dialogue tracks may make sense for separate speakers, microphones, or production sound and replacement dialogue. Multiple music tracks may help distinguish a score from a licensed song or a temporary cue. The question is whether the elements should share a level move and processing. If they should, a shared track is convenient. If not, split them into distinct tracks or use clip-level control.

#
## Does the track fader change clips that start later?

Yes, a track fader applies to the track signal during playback, so clips that play later on the same track also pass through that track-level control. A fader move is not limited to whichever clip was selected when you made it.

This is exactly why faders work well for overall balance. It is also why a timeline edit can appear to change after a fader adjustment even when none of its clip gain values changed. The fader is downstream of the individual clip adjustments in the track's signal path, so changing it changes what reaches the next part of the mix.

If clips on one track need different relationships to one another, keep those differences at clip level. A fader should not be a substitute for normalizing a badly uneven series of edits by ear. Conversely, don't edit every clip separately just to move a whole track in the mix.

#
## Can I use the Inspector's track level instead of the mixer?

Yes, Resolve provides track-level controls in addition to mixer faders, though the exact location depends on the page and version. The mixer makes the track context and neighboring channel levels easier to compare; a track Inspector can be useful when you want to adjust the selected track without opening a full mixer layout.

In Fairlight, the channel fader is the familiar console-style control. Blackmagic's overview notes that Fairlight channel strips represent timeline tracks and buses and include a fader. Track headers also expose automation parameter curves, and the product guide describes choosing parameters and editing their automation over time. If a control is labeled track level or fader level, verify that you're adjusting the track, not an individual clip's Inspector setting.

When a control's scope is unclear, make a temporary small move while watching the meters and listening to more than one clip on the track. If several clips change together, you have found the track-level control. Undo the test or reset the value after confirming. Don't use that test on a delivery session without saving a version first.

**A track fader sets the shared level of its audio track, so it is the natural control for a whole track that is consistently too loud or quiet.**

#
## Should I put every sound on its own track?

No. Separate tracks are useful when sounds need independent level, processing, routing or automation. They add clutter when the sounds always move together and need the same treatment.

An editor working on a simple short may use one dialogue track, one music track and one effects track. A longer documentary might need distinct tracks for interview dialogue, narration, production sound, ambience, music and effects. A multicamera interview can benefit from separate tracks for speakers or microphones, especially when each source has different noise, EQ or level needs.

There is no rule that the number of tracks should match the number of clips. Track layout is a decision about shared control. If all the clips on a track need one common fader, group them. If one clip constantly needs special treatment, decide whether clip automation, a new track, or a different edit is clearer.

#
## What is the difference between a clip and a track in the Fairlight mixer?

A timeline clip is one placed section of media; a Fairlight track is a timeline lane that can contain multiple clips over time. The mixer channel strip represents the track as a whole, not the one clip under the playhead.

The distinction sounds basic until you have many edits. A single source recording may become several timeline clips after you remove pauses. Those resulting clips can each have their own volume, while the track fader controls their shared channel. Conversely, a compound or linked editorial choice does not necessarily mean one audio clip; selection and grouping behavior should be checked in the timeline before changing a value.

When you see a fader move and several clips respond, that is expected. When one Inspector value changes and only the selected clip behaves differently, that is expected too. Reading the object under your cursor is the quickest way to avoid confusing these layers.

## How do I balance dialogue and music without changing every clip?

First even out large differences between dialogue clips with clip volume; then use the dialogue and music track faders to set the overall relationship. Use automation only when that relationship needs to change as the scene unfolds.

Blackmagic's Fairlight Audio Guide uses a dialogue-over-music example and frames the balance as a listening task supported by waveforms and track meters. Its discussion calls dialogue the priority when spoken words compete with music or other material. This is a practical editorial rule, not a fixed decibel prescription: the scene, delivery and intended playback all matter.

A simple three-pass workflow keeps each decision at the right scope.

1. **Make the dialogue clips consistent.** Listen across the edits. If a single sentence is far quieter or louder than its neighbors, adjust that clip. Avoid chasing every syllable; fix clear jumps first.
2. **Set the dialogue track against the rest.** Play a representative section with music and effects. Move the dialogue fader to establish its overall place. If speech remains hard to understand, check masking, noise, EQ, and the recording before making a huge level boost.
3. **Set the music track.** Lower or raise the music track as a whole until speech remains clear while the score still supports the scene. If music is meant to swell between lines, leave room for automation rather than forcing one static fader position to solve every moment.

If the music includes multiple unrelated cues, one fader for the entire score may not be enough. Use distinct tracks for separate musical roles or adjust cue clips individually. The same reasoning applies to sound effects: if every effect should share one broad level, use a track; if an explosion should hit harder than room tone, balance the clips locally or divide the roles.

Sound On Sound's discussion of mixing warns that gain management happens at several points in a signal path, and it describes clip gain or a trim control as ways to lower source levels before processing. That supports a useful distinction: clip-level adjustment can feed later processing differently from a downstream fader move. In Resolve, exact processing order depends on which control or effect you use, so don't assume all “volume” controls act at the same point.

#
## Why did lowering music on one clip make the next section too loud?

A clip-level change affects only the selected music clip, so another cue or clip later on the track can remain at its original level. If the whole music track should be lower, use the track fader; if the two cues intentionally have different roles, keep separate clip or track settings.

This often happens when a music file is cut into sections to fit picture. Lowering the first section may solve the opening but leave the chorus or next cue untouched. That isn't a bug. The clip control did exactly what it was asked to do.

Review the full sequence after any gain change. Play across edit points rather than judging only the selected clip. A comfortable opening followed by a sudden jump is a sign that you have only corrected one part of a larger balance problem.

#
## Why does my voice sound uneven even when the track fader stays still?

The track fader can stay fixed while individual clips differ in recording level, performance, microphone distance or background noise. A steady track fader doesn't guarantee a steady voice; correct clip-to-clip jumps with clip volume, editing or processing.

A fader is a single shared level setting unless you automate it. It cannot distinguish a whispered phrase from a loud phrase on the same track. If each edit varies, use clip gain first to make the material more consistent, then use compression or automation where appropriate. A processor can help manage dynamics, but it cannot restore words lost under noise or repair a poor recording by itself.

Listen for room tone changes too. If one line gets louder along with a hiss or air conditioner, a raw level boost may make the noise more obvious. If the line is too loud, lowering its clip volume also lowers its noise; if noise is the primary issue, consider cleanup tools and careful edits. Keep the correction modest and listen in context.

## How does clip volume differ from track fader automation?

Clip volume affects one clip, while track fader automation changes the whole track level over time. Use clip keyframes for a local change inside one clip and fader automation for a ride that applies to the track's combined output.

Automation is a recorded or drawn control curve. Blackmagic describes Fairlight automation as changes to control settings that play back automatically, with track headers able to display parameter curves for editing. The fader curve can be displayed in the timeline, while the mixer provides a hands-on way to write changes during playback. For the automation display steps and likely causes when a curve is hidden, see [DaVinci Resolve Audio Automation Line Not Visible](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-audio-automation-line-not-visible).

Consider a music bed under narration. Clip volume can lower a particular music clip, but it may not provide the best view of the broader rise and fall across a long scene. Track automation can keep music tucked under speech, then raise it during a pause. The same can work for dialogue when one track needs a gentle ride across a sequence.

Automation is powerful because it makes a time-dependent mix decision repeatable. It also creates another layer to inspect. If a fader keeps moving during playback, check whether automation is enabled and whether you are in a mode that reads, writes or touches automation. Don't keep fighting a fader that is being controlled by a curve.

#
## When should I keyframe clip volume instead of automating a track?

Keyframe clip volume when the change belongs to one clip; automate the track when a level ride should affect the entire track over time. A brief reduction in one noisy sentence is local. A music duck that follows a sequence of dialogue lines is usually a track-level mix move.

A practical example: one interview clip contains a chair bump between two phrases. Lower the bump locally or edit it out if the picture allows. If the score needs to fall under every line in a multi-clip interview, a track automation curve can express that wider pattern. You can still use clip volume to correct one cue that starts hotter than the others.

Avoid stacking overlapping changes without a reason. If you lower the clip by a large amount and also draw a deep dip in the track automation, you may forget why the result is so quiet. Keep the roles clear: clip changes make the source edits behave consistently; track rides shape how that category plays against the rest of the scene.

#
## Why does the fader move by itself in Fairlight?

A fader that moves during playback is often responding to automation data or an automation mode that is writing or playing back changes. Inspect the track's automation controls and visible Fader Level curve before assuming the project is broken.

If you intended a static track level, switch to a safe automation mode for your workflow and review existing keyframes. A curve can be present outside the section you are watching, so play through the complete range. If needed, clear or revise the automation deliberately rather than overwriting it by dragging the fader during playback.

For an overview, Blackmagic's [Fairlight product guide](https://www.blackmagicdesign.com/products/davinciresolve/fairlight) describes enabling automation parameters and editing curves from track headers. The exact automation mode names and interaction details should be checked against the manual for your DaVinci Resolve release. Resolve 21.1 includes broad keyframing improvements in the release notes, but Blackmagic's 21.1 notes do not say that the basic difference between a clip and a track fader has changed.

## Why is the clip gain line missing in DaVinci Resolve?

The clip gain line may be hidden by the current timeline display, track height or page layout. In Fairlight, use the menu's Show Clip Gain Line command described in Blackmagic's Resolve 20 Fairlight guide, then enlarge the track if the line is difficult to see.

First confirm that the clip is an audio clip and that the correct timeline is open. Then try these checks:

1. Open the Fairlight page and look for the clip gain display command in the Fairlight menu.
2. Increase the audio track height so the clip and its controls are easier to see.
3. Select the clip and open the Inspector as an alternate route to its Volume control.
4. Check whether you are looking at a nested timeline, a compound clip or a different audio layer than the one you intended to change.
5. If you need a gradual ride, show the automation lane or track parameter curve instead of expecting the static clip line to represent automation.

Resolve's interface changes between releases, and a menu path can move or be labeled differently. Blackmagic's online support page lists the Resolve 21.1 release as dated September 8, 2026, and the Fairlight guide is for Resolve 20. The core concepts are shared, but use the manual version that matches your installation when a command differs.

A hidden gain line does not prevent a clip adjustment. The Inspector remains a direct clip-level route. Likewise, opening the mixer gives access to track level even if the timeline lane is too short to show every control. Pick the visible control whose scope you can verify.

If you need the exact menu location in your installed layout, Uncle can point to the clip-level control on your screen while you work.

## Why did my clip volume change but the audio still peak or distort?

Clip volume changes the level at its point in the signal path, but distortion may already exist in the recording or may occur later in the chain. Lowering a clip can reduce downstream overload; it cannot undo clipping captured at the microphone or restore a flattened waveform.

Separate three cases. First, the source recording may contain clipped distortion. The waveform can show flattened peaks, and the sound may remain harsh even after you reduce its level. Second, the clip may be clean but a track effect, bus processor or output stage may overload. In that case, a clip or track reduction before the overloaded stage may help, depending on signal order. Third, the meters may not be clipping at all; the harshness could come from room noise, wind, an aggressive effect, or monitoring distortion.

When audio is already distorted, don't keep raising the track fader because the track sounds weak after you lower the bad clip. Isolate the clip, compare it with the source, inspect the relevant meters, and try a suitable repair process if available. If the clipped sound is baked into the file, restoration may be limited.

A track fader is often later in the track path than clip gain, which is why it can change the overall mix while leaving the earlier signal feeding track processing at its previous level. Signal order matters with compressors, limiters, EQ and effects. Use the Resolve manual and inspect the specific Fairlight path when the result differs from what you expected.

The phrase “clip gain before processing” is common in audio workflows, but Resolve includes several levels and processing stages. The official guide distinguishes the clip volume control from the channel fader, while experienced users on Blackmagic's forum discuss additional path trims and processing order. Forum advice can be useful context, but for a version-specific maximum or exact signal path, verify against the manual rather than relying on an old post.

#
## Should I lower clip gain or use a compressor?

Lower clip gain when a clip is consistently too hot before processing; use compression when you need to manage changing dynamics within a performance. They solve different problems and can be combined, but one should not be applied as a reflex.

If a voice take is consistently louder than neighboring takes, a clip gain correction can bring the clips closer before you balance the track. If one speaker moves closer and farther from the microphone within the same take, compression or automation may help manage that variation. If the issue is a single cough, a local edit or keyframe may be more transparent than compressing the whole track.

Compression changes dynamics according to its settings. A fader changes level. Clip gain changes a clip's level. These controls can all affect perceived loudness, but they do not have the same sound or purpose. Start with the least complicated move that addresses the actual problem, then listen for side effects.

#
## Why does raising track volume not fix quiet dialogue?

A track fader raises every sound on the track together, including room noise and breaths, and may still leave the dialogue below downstream effects or bus processing. Check the clip level, track routing, noise, processing and output path before adding more gain.

The most common diagnostic is to compare the audio meters at successive points: clip or track, bus, and main output where available. If the track meter moves but the bus or output does not, the path may be routed incorrectly or muted. If the track meter is healthy but the voice sounds buried, the music may be masking it. If both voice and noise rise together, the source may need cleanup rather than a bigger fader move.

Routing questions are a different problem from volume scope. See [DaVinci Resolve Audio Bus Routing Not Working? Fix It](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-audio-bus-routing-not-working) if a track meter moves but the intended output stays silent. If the audio crackles or pops during playback, that points to playback or processing issues rather than a simple track balance decision; the [audio crackling and popping guide](https://tryuncle.com/learn/davinci-resolve/davinci-resolve-audio-crackling-and-popping-during-playback) covers that separate symptom.

#
## Can I raise a very quiet recording by a large amount?

You can raise clip or track level within the available control range, but added gain raises noise along with the wanted sound and cannot recreate missing detail. Start with the clip when only one take is quiet, and listen carefully as you raise it.

Blackmagic's Resolve 20 guide demonstrates clip volume entry and incremental adjustment, but maximum ranges may depend on the particular control and release. Avoid relying on old forum figures as universal limits. The forum posts surfaced in research discuss specific historical Resolve versions and signal-path controls; they are not a substitute for the current manual.

A practical recovery sequence is:

1. Confirm that the clip itself is the source of the low level. Check the track, bus and monitoring path.
2. Raise the clip a little and compare its noise floor with adjacent clips.
3. If noise becomes distracting, try repair, EQ or noise reduction carefully, or re-record if possible.
4. Balance the corrected clip against neighboring clips, then set the track fader against the full mix.
5. Check the output meter and listen on more than one playback system before export.

Do not mistake loudness for quality. A clean, naturally quiet recording may respond well to gain. A noisy recording may get louder without becoming clearer.

## What is the best workflow for clip volume vs track volume?

Use a repeatable order: organize tracks by role, correct large clip-to-clip differences, set track faders for the overall mix, automate changes over time, then check buses and output. That order keeps each control responsible for the right scope.

#
## 1. Organize by shared mix decisions

Start by grouping sounds that should move together. Dialogue, music, effects and ambience often need separate track control because they play different roles. Separate speakers or sources further when their recording conditions or processing differ.

The goal isn't a perfect-looking timeline. The goal is to make the next level decision obvious. If lowering one track would damage another sound, those sounds probably do not belong on the same track for that mix.

#
## 2. Correct clips that are clearly inconsistent

Listen across edits. Adjust the outlier clips first. Avoid trying to make every waveform look identical; speech and music naturally have different shapes, and waveform size is not a direct measure of perceived balance.

For dialogue, compare adjacent phrases at a steady monitoring level. For music cues, listen across the edit and note whether the energy changes intentionally with the picture. For effects, preserve the transient impact while keeping unexpected peaks under control.

#
## 3. Balance the tracks together

Now play the scene as a mix. Set each track's fader based on its role. Dialogue may need to lead; music may need to sit behind it; effects may punctuate moments without masking words. Those are editorial choices, not fixed presets.

Work with representative material. A music passage with no dialogue won't reveal whether the score masks speech. A single quiet line won't reveal whether a track is too loud across the full scene. Listen to transitions and dense sections.

#
## 4. Automate what should change over time

If the proper level changes during playback, automate the relevant clip or track. A music duck may follow dialogue, while a local clip keyframe may correct one moment. Make curves gradual enough to avoid distracting pumping or visible jumps.

Automation is also an editorial record. Name tracks clearly, keep curves understandable, and avoid drawing multiple overlapping rides to fix the same issue. After a change, replay the section before and after the automation point.

#
## 5. Verify the full output path

Check that tracks reach the intended bus, that the bus reaches the main output, and that no downstream stage is clipping or muted. Listen to the final mix, not just the isolated track. A perfect soloed voice can still be hard to hear once music and effects return.

If an audio problem appears during export but not in timeline playback, compare the render settings, bus processing and output meters. If the problem is that Resolve plays no audio at all, don't change clip gain first. Confirm the monitoring device and routing. The symptom determines the scope.

## Does clip volume or track volume affect the exported audio?

Both can affect the exported mix because both are part of the timeline's audio signal path. Clip volume changes the rendered level of that clip; track volume changes the rendered contribution of that track.

The export contains the mix that reaches the selected output, including clip adjustments, track levels, processing, automation and routing. A clip may sound right in isolation but still be too quiet in the full export. A track may meter correctly but feed a bus with different processing. Always review the rendered file, especially if the delivery has a loudness, peak or channel-layout requirement.

Normalization is not the same as track balancing. Blackmagic's Fairlight overview says that a clip can be normalized from its context menu to set a target level for timeline clips. Normalization can be useful when you understand the chosen measurement and target, but it does not decide how dialogue should sit against music or whether the mix works artistically. You still need to audition the result.

A loudness target is not a universal volume knob. Delivery specs may specify integrated loudness, true peak, channel layout or other conditions. Those requirements depend on the destination. Verify the actual spec from the client or platform rather than guessing a number, then meter the final render accordingly.

If the exported audio differs from what you hear, compare the same passage, confirm the export includes the intended audio tracks and bus, and listen at a consistent playback level. A player or operating system may also apply its own volume or loudness behavior. Don't judge the render from a different app at a different system volume and conclude that a clip setting failed.

#
## Do clip gain and track volume stack?

Yes. The clip's level and the track's level both contribute to the signal that reaches later stages, so their effects can combine. A clip raised by one control can still be turned down by its track fader, and a track fader move can still leave a quiet clip relatively quiet compared with other clips.

This is useful when the controls have separate jobs. First make a quiet clip comparable with neighboring clips, then lower the whole track to fit the mix. It becomes confusing when the same problem is corrected twice without a clear reason. If a clip sounds much too low, check whether its clip level is reduced and whether the track fader is also low.

After stacking changes, consider whether the project still communicates intent. A clip gain value, track fader and automation curve can all make the same line quieter. A future editor may struggle to tell which adjustment is deliberate. Use labels, track organization and restrained corrections to keep the mix readable.

#
## What if I need one fader for several tracks?

Route the tracks to a bus when they should share a group-level control, then use the bus level for that group. Keep each track fader available for individual balance within the group.

For example, a scene with multiple effects tracks may benefit from a shared effects bus. The bus can raise or lower the effects group, while each track still controls its own contribution. A bus is a broader scope than a track, so it can affect several tracks at once. Verify routing before moving it, especially when other tracks also feed that bus.

The hierarchy becomes: clip for one edit, track for one category or source lane, bus for a group of tracks, main output for the overall mix. Don't add a bus merely because it exists. Use it when a group-level control or processing chain makes the session easier to operate.

## Why does clip volume vs track volume matter for gain staging?

The choice matters because clip and track controls sit at different points in the audio path, so they can feed processors differently. Use clip volume to correct material before the shared track mix when that is the intended role; use a fader to balance the track after considering its processing and routing.

“Gain staging” means managing levels between stages so each part of a signal chain receives a useful level. Sound On Sound notes that processors may be optimized for certain signal ranges and that clip gain or a trim control can lower source level before other processing. It also cautions that gain management occurs at multiple points in a DAW path. Those principles explain why a fader move can sound different from changing a clip's input level when compression or other nonlinear processing is involved.

Producer and engineer Dave O'Donnell describes the relationship among mic preamp level and fader level in an [Audiofanzine interview](https://en.audiofanzine.com/sound-technique/editorial/articles/talking-shop-with-dave-o-donnell.html). Asked whether he pays attention to gain staging at 24/96, O'Donnell answers, “It comes down to your mic pre’s level and the fader level.” The quotation is brief, but the point fits this page: a fader is one stage in a chain, not a substitute for every other level decision.

That distinction is most audible when a compressor responds to the incoming signal. If you lower a clip before compression, the compressor may react less. If you lower a fader after compression, the compressor may respond the same way as before while the track's output changes. The precise Resolve signal order depends on the control and processing path, so check the Fairlight manual for the specific setup rather than assuming every effect is in one fixed position.

Do not chase a target number from a different workflow without understanding its reference point. A level recommendation for recording into an interface, a plugin input target, a track fader position and a broadcast delivery loudness are not interchangeable numbers. Meter at the stage that matters and listen to the end result.

**A track fader can rebalance a mix, but it cannot repair a noisy or clipped source recording.**

## What common mistakes happen when editors confuse clip and track volume?

The most common mistake is changing a shared track control to solve a local clip problem, or editing many clips one at a time to solve a shared track problem. Match the control's scope to the scope of the problem.

#
## Lowering a whole track to fix one loud clip

If one clip is too loud, lowering the track may make every other clip too quiet. Fix the outlier clip first, then restore the track to the level that serves the full sequence.

This mistake is easy to miss if the loud clip occurs near the beginning and you only audition the first few seconds. Play the entire track or at least sample clips across the sequence after the move. Look at transitions where an adjusted clip meets an unchanged neighbor.

#
## Raising every clip because the track is too quiet

If all clips are balanced but the track is too quiet, changing every clip repeats the same decision. Raise the track fader and preserve the clip-level relationships you already established.

There are exceptions. If your clips need consistent levels before a particular processor, individual clip gain may be part of the intended gain staging. But don't make that choice by habit. Ask whether the problem is the track's mix position or the clips' inputs to the processing chain.

#
## Using the track fader to hide a routing problem

A track that is routed to the wrong bus may remain silent regardless of how far you raise its fader. Check track output routing, bus mute and main output assignments. A fader cannot send audio to a destination that the track does not feed.

#
## Judging levels from waveform size alone

Waveforms show amplitude shape, not the complete experience of loudness, intelligibility or balance. A quiet waveform can be clear. A visually large waveform may be a low-frequency thump that feels less loud than a smaller, bright sound.

#
## Setting a mix on solo and never checking it in context

Solo is useful for finding clicks, noise and edit problems. It is not a substitute for balancing in the full mix. Dialogue that sounds clear alone may disappear under music; an effect that sounds huge solo may sit properly once the scene plays.

#
## Making hidden automation edits accidentally

If automation data is active, a manual fader move may be written or overridden depending on the mode. Show the fader curve and inspect automation before wondering why the fader returns to its old level.

#
## Using normalization as the whole mix

Normalization sets a clip toward a target according to a measurement method. It does not understand story priority or the relative role of each sound. Normalize only when you need that operation, then make the mix decision by listening.

**The fastest reliable fix starts by naming the scope: one clip, one track, a group bus, or the whole output.**

## Which control should I change? A quick decision table

Choose the narrowest control that covers the problem. Start with clip volume for one clip, a track fader for the full track, automation for a changing level, and a bus or output control for a larger group.

| What you hear or need | Start here | Why |
| --- | --- | --- |
| One interview edit is quieter than the next | Clip Volume or gain line | Only the outlier clip needs a correction |
| Every clip on a dialogue track is too loud | Dialogue track fader | The whole track needs a shared move |
| Music should duck under a run of dialogue | Track fader automation | The relationship changes during playback |
| One music cue is much louder than another | Clip volume, cue-specific track, or automation | Choose based on whether it is a local cue or a broader pattern |
| A group of effects tracks needs to come down together | Effects bus | The shared group needs a single control |
| Track meter moves but no sound reaches the speakers | Routing and output path | A level move cannot fix a disconnected path |
| The source sounds crunchy even after lowering it | Source recording and processing | Level reduction cannot restore clipped detail |
| The mix is good in Resolve but wrong in the render | Export routing, output path and render review | Verify the signal that was actually delivered |

The “narrowest control” rule preserves other good decisions. If only one clip needs a change, avoid shifting a group. If the whole track is wrong, don't make a long list of clip edits that all express the same adjustment. If the sound changes with time, a static value may never solve it cleanly.

A useful check is to state the requested move out loud: “This sentence needs to be louder than the other sentences,” or “All the music needs to sit lower,” or “The music should rise after the narration.” Each sentence points to a different control: clip, track, or automation.

## Is DaVinci Resolve 21 different from Resolve 20 for clip and track volume?

Blackmagic's [current support listing](https://www.blackmagicdesign.com/support) shows DaVinci Resolve 21.1, released September 8, 2026, and the Resolve 20 Fairlight guide documents the clip gain line, Inspector volume adjustment and track-level mixing concepts discussed here. The current release notes mention broader improvements, but do not describe a change to the basic scope distinction between clip volume and track volume.

Version context matters because menu labels and panel layouts can move. Resolve 21's 2026 release added and updated many features, including Fairlight-related items in the 21.0 release and keyframing improvements in 21.0.3. Blackmagic lists further improvements in Resolve 21.1. Those release notes do not say that clip gain has become track volume or that the track fader now targets one clip. The operational concepts in this article are based on Blackmagic's Resolve 20 Fairlight guide and its Fairlight feature overview, checked against the current support listing as of October 2026.

| Version reference | What the source says | What it means for this comparison |
| --- | --- | --- |
| DaVinci Resolve 20 Fairlight guide | Covers clip gain lines, Inspector volume adjustment, balancing clips and track-level mixing | Direct procedural reference for the controls described here |
| DaVinci Resolve 21 final release, June 3, 2026 | Blackmagic lists new Fairlight folders and improved keyframing among release items | Version-specific workspace and keyframe details may differ |
| DaVinci Resolve 21.0.3, July 22, 2026 | Blackmagic lists improved keyframe editing among changes | Recheck keyframe interaction if following older instructions |
| DaVinci Resolve 21.1, September 8, 2026 | Blackmagic lists new features across still photography, multicam, Fusion and project management | Current version context; support listing does not announce a clip-versus-track level behavior change |

The safest practical approach is to use the control's label and observe its scope in your installed version. Select one clip and check the Inspector. Open the mixer and identify the channel strip for the whole track. If a curve or automation mode is active, inspect that before editing. If a menu path differs, search the current Fairlight menu or manual rather than forcing a Resolve 20 screenshot-based instruction onto Resolve 21.

The free and Studio editions share the core clip-versus-track distinction described by the Fairlight workflow. The release pages may identify Studio-only capabilities elsewhere, but this article does not rely on a Studio-only audio control. Check the feature list for any effect or advanced processing function you intend to use.

## Is clip volume or track volume better for beginners?

Clip volume is easier to understand when one clip is obviously wrong; track volume is easier when a whole category needs to move together. Beginners can learn both by asking whether the desired change should affect one edit or all edits on the track.

A good beginner exercise is to place three dialogue clips on one track and a music clip on another. Lower the middle dialogue clip with clip volume and listen to the two neighboring clips. Undo. Then adjust the dialogue fader and listen to all three. The first move changes one clip; the second changes the shared track. Finally, move the music fader and hear how the whole relationship changes.

This is more useful than memorizing a shortcut because it teaches scope. Once you know which level you want to change, you can find the corresponding control in the page you prefer. Blackmagic's Fairlight Audio Guide offers structured practice, and its official training page includes the Resolve 20 guide and lesson material. For a broader start, use the [DaVinci Resolve training resources from Blackmagic Design](https://www.blackmagicdesign.com/products/davinciresolve/training) before relying on snippets detached from their project context.

After seven years of professional commercial video editing, we still make mix decisions by asking what should move together. A fader is a powerful shortcut only when the audio on that track belongs together. Otherwise, a broader move creates cleanup work.

#
## What is the best way to learn DaVinci Resolve audio controls?

Learn each control through a small project where you can hear its scope. Start with one clip, one track, and one simple automation change, then compare the result in the full mix.

Blackmagic's free official training is the primary reference for the application, and its Fairlight guide provides a workflow-based introduction. Video lessons from educators such as Casey Faris can help when you prefer a demonstration you can follow on screen. A reference article like this one is useful when you need a quick distinction or troubleshooting path. Those formats serve different moments: a course builds sequence and context; a focused reference answers one stuck question.

When searching for help, include your Resolve version and the page you're using. “How do I lower this clip?” can mean the Inspector on Edit, a gain line in Fairlight, a track header level, or an automation lane. Naming the object and page narrows the answer and reduces the chance of applying a track move to a clip problem.

If you are stuck while working, [TryUncle](https://tryuncle.com/) is the on-screen assistant for DaVinci Resolve on Mac and Windows - ask in plain words and Uncle points at the exact control on your screen. That can be useful when a tutorial's menu differs from your layout; Blackmagic's manuals and official training remain the primary product documentation.

## What should I remember about DaVinci Resolve clip volume vs track volume?

Clip volume changes one timeline clip; track volume changes the combined output of the track; automation changes a level over time. Set each control according to the scope of the sound problem, then replay the mix and check the bus and output.

A clip is the right target when one edit is out of balance. A track is the right target when its clips are consistent but the whole layer needs a new position. Track automation is the right target when that position changes during the scene. A bus handles a group of tracks, while the main output affects the final mix.

Make one move at a time, listen across edit points, and keep the project readable. If the track fader seems to affect too much, it probably is. If clip adjustments are multiplying for no clear reason, step back and ask whether the track itself needs a shared move.

**Use clip volume to correct an individual edit, then use the track fader to place that track in the mix.**

Resolve's Fairlight tools become less mysterious when every control has a clear job. Name the scope, make the smallest useful adjustment, and listen again in context.



## FAQ

### What is the difference between clip volume and track volume in DaVinci Resolve?

Clip volume changes the level of one timeline clip. Track volume, controlled by the track fader, changes the combined output of all clips on that audio track. Use clip volume for differences between takes and track volume for the overall balance of the track in the mix.

### Why does changing track volume affect every audio clip in DaVinci Resolve?

The track fader sits on the shared audio track path, so every clip routed through that track is affected. Put clips that need independent mix levels on separate tracks, or adjust their clip gain individually.

### How do I lower only one audio clip in DaVinci Resolve?

Select the timeline clip and lower its Volume control in the Inspector, or lower the clip gain line in the timeline. Those controls target the selected clip rather than the track fader.

### Should I use clip gain or the track fader for dialogue in DaVinci Resolve?

Use clip gain to even out one quiet or loud dialogue clip relative to other clips on the same track. Use the track fader to place the dialogue track overall against music and effects; use track automation when that relationship needs to change over time.

### Why does my DaVinci Resolve audio still sound quiet after I raise the track volume?

Check that the track is routed to an audible bus and output, that the clip itself is not muted or extremely low, and that downstream bus or master levels are not attenuating it. Raising a track fader cannot fix a routing problem or recover detail buried in noisy source audio.

## Sources

- [DaVinci Resolve 20 Fairlight Audio Guide](https://documents.blackmagicdesign.com/UserManuals/DaVinciResolveFairlightAudioPost.pdf)
- [DaVinci Resolve Fairlight product guide](https://www.blackmagicdesign.com/products/davinciresolve/fairlight)
- [Blackmagic Design Support Center, DaVinci Resolve 21.1 release listing](https://www.blackmagicdesign.com/support)
- [Blackmagic Design training: Fairlight Audio Guide](https://www.blackmagicdesign.com/products/davinciresolve/training)
- [Sound On Sound, 5 Biggest Mixing Mistakes and How to Avoid Them](https://www.soundonsound.com/techniques/5-biggest-mixing-mistakes-and-how-avoid-them)
- [Audiofanzine, interview with producer and engineer Dave O'Donnell](https://en.audiofanzine.com/sound-technique/editorial/articles/talking-shop-with-dave-o-donnell.html)