Map the repeated elements before building
A small presentation can repeat the same camera, title, media clip or logo in several layouts. Decide which repetitions should always change together and which need independent behavior. This is a design decision about ownership, not a reason to create a new source for every visible object.
Make an inventory with the source’s purpose, the scenes that use it and the intended change scope. A presenter camera may be shared throughout. A clip used as a looping background and the same clip used as a one-time demonstration may need separately understood playback states. Choose deliberately and label the reason.
| Presentation element | Intended ownership | Review consequence |
|---|---|---|
| Presenter camera | Shared across explanation and closing scenes | Device or source-filter change must be reviewed in both |
| Tighter camera placement | Specific to the diagram scene | Check that the wider explanation framing stays intact |
| One-time demonstration clip | Independent from a looping background role | Review activation and ending behaviour separately |
Distinguish source settings from placement
OBS’s Sources guide allows existing sources to be reused across scenes. The Crop/Pad documentation explicitly distinguishes a base-source filter from scene-item cropping. This distinction explains why an underlying change can follow the source while each scene has its own composition.
Use a source name for identity and scene names for presentation roles. A name such as camera does not say which scene is live, and a scene called closing does not establish which media file it contains. Clear names help the operator find the correct object before changing its properties.
Document independent variations and maintain them
Where independent sources are justified, record what must remain different: playback restart policy, crop, selected file or audio treatment. Review both after replacing a media revision. Independence solves a scope problem but creates a maintenance responsibility; the second copy will not automatically express the first copy’s intended revision.
Finish with a short cue rehearsal that visits every affected scene. Keep the ownership inventory with the collection export so another operator can understand later edits. No complex scene collection was built or tested here; the guide supplies a practical design procedure without claiming a performance benefit or universal resource saving.
Questions answered
Should I always duplicate a source for another scene?
No. Decide whether its underlying properties should be shared or independent, then use the appropriate design.
Is moving an item equivalent to changing its source filter?
No. The source’s shared properties and an item’s scene placement have different scopes.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.