- Posts: 4
- Joined: Thu Apr 10, 2025 10:37 pm
- Real Name: Jhaimes Sousa
Wed Apr 23, 2025 1:56 am
Hi team,
I've noticed a frustrating behavior with the Quick Export feature in DaVinci Resolve.
When using a custom preset that includes tags in the "Filename" field (like %Timeline Name%, %Date%, %Render Preset%, etc.), the regular Deliver page honors these tags perfectly and names the exported file accordingly.
However, when using Quick Export with the same preset, these tags are ignored, and the output file ends up with a generic or incorrect name – stripped of all metadata-based tags.
This completely defeats the purpose of using Quick Export with well-configured presets, especially in workflows where automated naming is essential for versioning, file tracking, or collaborative environments.
Please align Quick Export’s behavior with the Deliver page when reading and applying filename tags from presets. This would make Quick Export actually quick and usable in professional workflows.
I've noticed a frustrating behavior with the Quick Export feature in DaVinci Resolve.
When using a custom preset that includes tags in the "Filename" field (like %Timeline Name%, %Date%, %Render Preset%, etc.), the regular Deliver page honors these tags perfectly and names the exported file accordingly.
However, when using Quick Export with the same preset, these tags are ignored, and the output file ends up with a generic or incorrect name – stripped of all metadata-based tags.
This completely defeats the purpose of using Quick Export with well-configured presets, especially in workflows where automated naming is essential for versioning, file tracking, or collaborative environments.
Please align Quick Export’s behavior with the Deliver page when reading and applying filename tags from presets. This would make Quick Export actually quick and usable in professional workflows.