ClipOne answer, several attributes, your editorial decision. This example does not write to the app.
Start with the shots your editor asks for
Your logging palette is the set of fields you use to describe a shoot. For a game, that could be athlete, action, shot size and rating. For a restaurant, it could be menu item, plating, pouring and shot size. An interview might need speaker, topic and a note about the useful moment.
Choose fields that help someone else find the shot. You can fill them yourself, use keyboard shortcuts and roster codes, or ask a vision model to suggest the values before you review them.
Learn from the filenames you already use
If you have a folder of clips named with people, actions or other useful details, open it in Browse and show at least three files. Open the palette picker and choose Learn from these files…, then name the new palette.
ClipLogger infers fields and options from the visible filenames and gives you an editable starting point. Check the guessed meanings, remove anything you do not need, and import your roster codes separately. This is filename learning; it does not automatically turn every embedded metadata field into a palette.
Supported XMP values can also be read from existing media, so you do not have to ignore the ratings, keywords or descriptions already in the archive.
Pick the field that matches the decision
| Field | Use it for | Example |
|---|---|---|
| Single-select | One answer | Shot size: Wide |
| Multi-select | Several things in one clip | Crowd, celebration, reaction |
| Subjects | Known people, items or places | Maya Torres / Shrimp scampi |
| Flag or toggle | A quick decision | Pick / usable audio |
| Rating | Your editorial judgment | Four stars |
| Text or description | Context that needs a sentence | Clean reaction after the whistle |
| Number or date | A value you want to keep typed | Take 3 / shoot date |
Give the model a short explanation of each field and the options you want it to use. Disable new AI values when the vocabulary needs to stay fixed. Leave a description field for details that do not fit a short label.
Use codes for the things you know
A roster code can fill a person’s name without retyping it on every clip. The same lookup approach works for locations, shot codes or client terms, including single-select and multi-select fields. Map the code to the intended field and check any duplicate codes before applying them. Roster and lookup guide.
Bind frequent decisions to comfortable keys in the palette editor. Test the bindings with a real clip selected so text entry and app-wide shortcuts behave as expected.
Let a model take the first pass
Choose a few clips and run suggestions with Local, Your API or Rush. The model receives selected frames and your enabled context, including the fields you defined. Review whether the proposed answers would help your editor, then adjust the field descriptions before running a bigger batch.
The goal is less repeated typing and a more consistent log. Your team still makes the editorial calls.
Make the palette useful outside this session
Search and filter the fields you created inside ClipLogger. Preview a filename built from them, and check a supported NLE export. Enable sidecar output to keep the fuller log beside the media, and save the project/palette configuration so you can reuse it on the next shoot.