Use a metadata keyword only when the on-screen information should change with the source clip. First confirm the intended field exists for that clip; then preview the overlay on at least two clips with different values. If the field is missing, ambiguous, or displays the wrong value, do not let it pass into the delivery unchanged.
Identify the field and set up the overlay
- Select a source clip and open Properties > Metadata. The panel shows embedded, non-editable metadata. Do not assume that a project-only comment, a renamed clip title, or a field seen on another file is available here. Shotcut’s Properties documentation distinguishes embedded metadata from comments saved with the project.
- If you need to verify the exact property name, inspect the
.mltproject file in a text editor and find the section for that clip. Look for the property name and value together, such asmeta.attr.title.markup. The property name after themeta.prefix is the part to use in the keyword; confirm it in the actual clip section rather than copying a documentation example blindly. - Add the Text: Simple video filter and place
#meta.<field>#in its text. Replace<field>with the exact property path you verified. For example, a clip containingmeta.attr.title.markupcan be referenced as#meta.attr.title.markup#. Surround it with fixed wording if useful, such asTitle: #meta.attr.title.markup#. Shotcut documents this keyword form for metadata properties; Text: Simple documentation also explains that the keyword is replaced with clip information. - Preview the filter on two different source clips whose verified values differ. Check the displayed wording and value on each clip. This is an editorial comparison, not a guarantee that every field behaves identically across media types or project structures.
Static text is literal wording you type into the filter; it stays the same across clips. A metadata keyword requests a value from the clip, so its usefulness depends on the property being present and suitable on each source.
Use a metadata text mapping sheet
The following is a hypothetical acceptance example, not a report of a Shotcut test. Suppose a creator wants to show the source title. The project-file observations below are assumed sample values; inspect your own clips before using this mapping.
| On-screen label | Verified project field | Clip A observed value | Clip B observed value | Decision |
|---|---|---|---|---|
| Source title | meta.attr.title.markup | North Dock | South Gate | Accept only if each preview shows its own value |
| Frame rate | meta.media.0.stream.frame_rate | 25 (independent hypothetical value, not the 60 shown in the cited official example) | Field absent | Do not apply this mapping to B; use a different approved label or omit it |
| Producer | meta.attr.artist.markup | Studio One | Empty | Hold B for review; do not silently label it as Studio One |
For each production label, record the actual field path and observed values from the selected clips. A mismatch between the two clips is useful evidence: it can expose a missing property, an inappropriate field, or a value that does not change as expected. Decide the empty-value policy before approving the overlay: omit that label on the affected clip, use separately reviewed static text where appropriate, or hold the clip until its source information is confirmed. Do not substitute a guessed value.
Limits and what to do when it fails
The documented mechanism reads metadata properties for file-based clips. It does not establish that every media file has the same properties, that every field is meaningful, or that a displayed value is editorially correct. Properties > Metadata is read-only for embedded metadata; Shotcut’s documentation says comments are project-saved and do not modify the source asset. A project comment is therefore not a replacement for a verified embedded field in this workflow.
If the keyword displays no useful value, first recheck the property spelling and the selected clip’s project section. Then compare the same field in Properties > Metadata and inspect the preview for both clips. If one clip lacks the property or its value cannot be confirmed, omit the dynamic label for that clip or use an explicitly reviewed static alternative. Recheck the final preview against the mapping sheet before delivery. Do not treat a plausible-looking value as proof that the field mapping is correct.
Three quick questions
Can I use the example field from the documentation? Only if that exact property exists for your clip. The frame-rate and title paths above illustrate the syntax; they are not a universal field list.
Will a keyword show a project comment? The cited documentation says comments are saved with the Shotcut project and searchable for playlist clips. It does not document comments as metadata keyword values, so do not assume `#meta...#` can read them.
What if I need the same wording on every clip? Use static text when the wording is genuinely constant. Use a metadata keyword only when the displayed value should follow a verified source property.
Sources and next step
- Text: Simple Video Filter - Documentation - English - Shotcut Forum
- Audio/Video Properties - Documentation - English - Shotcut Forum
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.