AFX Camera Tagger addresses a very specific but recurring problem in multicamera editing inside DaVinci Resolve. The application’s multicam creation dialogue allows editors to synchronise clips by timecode, waveform, or other methods, and to automatically detect camera angles. That angle detection depends on correctly assigned camrea tags in the clip metadata.
If those tags are missing, Resolve treats each clip as a separate angle. The result is not a clean multicam stack but a staircase of individual tracks, each containing a single clip. For editors handling concerts, interviews or live events with double-digit camera counts, that is not a minor inconvenience.
AFX Camera Tagger automates the assignment of Camera metadata, removing the need to tag clips manually in the Media Pool – for free.
Why tags matter
In Resolve, multicam creation is straightforward. Editors select their clips, choose the option to create a new multicam clip, define a sync method and enable camera angle detection. The angle detection relies on the Camera field in clip metadata. If clips share identical camera tags per angle, Resolve groups them correctly. Without tags, or if angle detection is disabled, each clip is placed on a separate track. The resulting timeline is technically functional but operationally inefficient.
Tags themselves are flexible. They can be any string, provided each camera angle is assigned a distinct value. The system does not enforce a specific naming convention. However, manual tagging becomes tedious in productions with frequent multicam setups or high clip counts.
Two tagging modes
AFX Camera Tagger provides two workflow modes. The first is based on bins, the second on file names.
In the From Bins mode, users select a main folder containing sub-bins with camera clips. After invoking a bin scan, the script lists available bins. A command labelled Set camera from bin names assigns Camera metadata based on the specified bin names. This approach suits ingest structures where each camera angle is organised into its own folder.
The script supports recursive processing, which automatically handles nested folders. According to the developer, deeply nested folder structures are processed without manual intervention. This is relevant for larger productions where DITs deliver structured Media Pools with multiple levels.
The second mode, From Clip Names, addresses the common scenario where all clips reside in a single bin but follow distinct naming patterns per camera. Users select clips in the Media Pool, specify which portion of the file name to parse, and preview detected camera angles before applying them.
The preview step reveals how many unique angles the selected name range produces. If the range is too narrow, the script may detect fewer angles than expected. Adjusting the selected character range corrects this. Once confirmed, the Set camera from clip names function writes the tags to the metadata.
This parsing approach depends entirely on consistent file naming. The tool does not claim to analyse image content, timecode or embedded metadata beyond the Camera field. It strictly operates on folder names or file name substrings.
Metadata handling and safety
AFX Camera Tagger writes to the Camera metadata field. If clips already contain camera tags, users can avoid overwriting them by enabling the relevant protection option. A Clear camera checkbox allows the removal of existing Camera tags from selected clips. Once assigned, tags persist with the clips throughout the project and work with every subsequent multicam synchronisation. The script does not advertise any background services or external dependencies. It operates within Resolve’s scripting environment.
Batch tagging is described as capable of handling hundreds of clips in seconds. The developer does not publish benchmark data. Performance, therefore, depends on project size and system configuration.
Studio requirement
AFX Camera Tagger requires DaVinci Resolve Studio from version 19.1 onwards. It is not compatible with the free edition from that version. Resolve scripting capabilities are typically tied to Studio features. The script is completely free and available for download from Art FX. An installation manual is included in English and Polish.
Practical implications for editors
For editors who regularly build multicam timelines, the tool addresses a narrow but real friction point. Manually entering camera tags via the Metadata panel is straightforward but repetitive. In larger projects, this can become a preventable source of error. The script’s value lies in its ability to map existing organisational logic, folder structure or file naming conventions onto Resolve’s Camera metadata field. It does not introduce new sync methods or alter multicam functionality. It simply ensures that the existing system works as intended.
The functionality is particularly relevant in workflows where assistants prepare Media Pools before the editor begins cutting. Automated tagging reduces prep time and minimises human error in repetitive data entry.
What it does not claim
AFX Camera Tagger does not claim to perform automatic camera detection based on image analysis. It does not claim to modify timecode, reel names or scene metadata. It does not advertise integration with external asset management systems. Its scope is limited to setting or clearing the Camera metadata field based on folder or file name patterns. Within that scope, the workflow appears clear and intentionally minimal.
That simplicity is likely its main strength. It solves one problem while leaving the rest unchanged.
As with any new tool in a professional environment, editors and post supervisors should test functionality, performance and metadata behaviour before deploying it in production pipelines. New tools and innovations should always be tested before production use.
