DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find b-roll clips in a library by plain-text search with Cdaf

Generate sidecars once, then grep .cdaf files to pick cut candidates by description.

Who it is forA video editor or agentic editing tool team choosing clips from a large footage library for a new edit.

The problemFinding the right shots means multimodal sweeps over every video, which is slow and expensive at library scale.

The outcomeA text search over sidecar files returns candidate clips, and their segment timestamps map to cut points.

What you need first

  • Python 3.10 or newer
  • Node.js with npx for the agent skill install
  • A Gemini API key (bring your own) for generating sidecars, or the local provider for no-key generation
  • ffmpeg, only if you run the synthetic benchmark

Steps

  1. Run cdaf generate ./footage to create sidecars for the library.
  2. Run cdaf status ./footage to confirm every clip is FRESH before searching.
  3. Search the sidecars with grep for the shot you need, for example a grep for "coastal highway" across the .cdaf files.
  4. Open the matching .cdaf file and copy the segment lines such as [00:05.2-00:12.8] into your cut list.

Prompt for your agent

Using the CDAF format from the repo UditAkhourii/cdaf, search every .cdaf file in <footage-folder> for the description <shot-description>, and return each matching clip path with its matching segment timestamps. Verify that each returned sidecar reports FRESH before you use it.

Caveat. Search quality depends on what the generator wrote into each sidecar, so check the matching segment text before you cut.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page