If an effect should change every clip on one AI-shot track and leave other tracks alone, add it to that track’s effect stack. Use the Master stack only when the effect is intended for the project’s global output across all tracks. This is a scope decision, not a preference about where the controls look most convenient. Kdenlive also warns that not every effect can be used at track or Master level, so verify the selected effect before committing.
Decide the scope and apply it
Use this sequence:
- Write the target in one sentence: for example, “apply this treatment to every clip on V2, but do not change V1 titles or A1 audio.” If the sentence names one track, a track effect is the candidate. If it names the finished mix from every track, a Master effect is the candidate.
- Inspect the effect in the Effects widget and its documentation link. Look for an indication that the effect is available at the intended level. The official Effects and Filters manual states that track and Master support is not universal.
- For a track-wide treatment, drag the effect to the header of the selected track or use that track’s effect stack. Kdenlive defines this as affecting all clips on that track. For a project-wide treatment, click Master above the track headers and add the effect to the Master Effect Stack; the manual defines this as applying to the global output.
- Preview a section where the target track and at least one unrelated track are visible or audible. Compare the target change with the unrelated track’s unchanged reference. Do not infer scope merely from the effect appearing in a stack: inspect the result.
- If the effect is unavailable at the chosen level, move it to a supported level. That may mean applying it to timeline clips individually, to the source clip in the Project Bin when all its timeline occurrences should share the treatment, or choosing another effect. Do not place a substitute on Master just to make the control available.
Acceptance worksheet for a two-track assumption
The following is a hypothetical acceptance case, not a software test or a guarantee of rendering behavior. Assume V2 contains three AI-shot clips, V1 contains a title and background plate, and A1 contains dialogue. The intended treatment is a visible color change on V2 only.
| Effect name | Target clips | Track | Other tracks | Proposed level | Official availability check | Preview observation | Decision |
|---|---|---|---|---|---|---|---|
| Hypothetical color effect | V2-01, V2-02, V2-03 | V2 | V1 title/plate, A1 dialogue | Track | Confirm the effect’s level support in its entry or panel | V2 changes across all three clips; V1 and A1 remain as reference | Keep on V2 if the observation matches the sentence |
| Hypothetical color effect | Clips on all tracks, including V2, V1, and A1 in this assumed project | V2, V1, and A1 | All tracks are in scope | Master | Confirm Master support; do not assume it from track support | Video changes on V2 and V1; A1 changes only if the effect is audio-capable | Keep on Master only if that project-wide result is intended |
The table records observations and a decision; it does not claim that a particular effect will produce a particular color value. If the preview contradicts the target sentence, the scope is wrong or the effect is unsuitable for that level.
Limits and the next step after failure
Placement support can be narrow: the manual says built-in Flip and Transform are available on video clips, while Volume is available on audio clips; on track headers only Flip on video tracks and Volume on audio tracks are available, and as Master effects only Flip and Volume are available. Check the target effect’s supported placement rather than inferring it from another level.
If an effect works on a clip but not on the track, first keep the same target sentence and change only the implementation: apply it to the relevant timeline clips, or consider a Project Bin clip effect if every occurrence of that source should share it. If it works on a track but changes an unwanted layer, remove that scope choice and reassess the track layout rather than compensating with an opposite effect elsewhere. Also remember that effects are stacked in order, and the order can change the result; this is a separate troubleshooting question from choosing the owner of the effect.
Three quick questions
Does a track effect change clips added later?
The documented rule is coverage of all clips on that track. For a new edit, check the resulting track stack and preview the new clip instead of assuming how your particular workflow will propagate settings.
Should a final look always go on Master?
No. Put it on Master only when every track should receive it and the effect supports Master. A look intended for one AI-shot track belongs at that track level when the other tracks must remain unchanged.
What if I need the same effect on two, but not all, tracks?
A single Master effect is too broad. Use supported track-level placements on the selected tracks, or apply the effect to their clips when track-level support is unavailable, then check the unselected tracks as the protected comparison.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.