Existing DAMs are photo-first, cloud-dependent, or give you tags like "beach." DAAAM is built for video. A custom vision model runs on your Mac and captions every frame: shot type, mood, composition, scene, lighting. Audio is transcribed with word-level timestamps fused to the timeline. Search by what you see or what was said. Connect to Claude via MCP for AI-driven storyboarding. Export to Final Cut, Premiere, or Resolve. Perpetual license. Your footage never leaves your machine.
No reviews yetBe the first to leave a review for DAAAM
Maker
📌
Hey everyone! 👋
I'm the solo dev behind DAAAM. Here's the backstory:
I've been shooting video for years — phone, drone, camera — and I have hundreds of GBs of raw footage I've barely touched. Not because the footage is bad, but because I could never find anything. Every time I sat down to edit, I'd spend more time scrubbing through folders than actually creating.
I looked at what was out there. Every digital asset manager was either designed for photographers, required uploading everything to someone else's cloud, or just gave you generic tags like "dog" and "sunset." Nothing understood how a frame was shot — the composition, the mood, the lighting, the energy.
So I fine-tuned my own vision model and built the app I wanted.
What makes it different:
🎥 Frame-level captioning — every extracted frame gets a structured 7-field description (scene, subjects, shot type, composition, mood, lighting, setting). Not "beach" — more like "wide aerial, golden hour, calm, river winding through valley."
🗣️ Transcript search — audio is transcribed with word-level timestamps and fused to the visual timeline. Search for something someone said and land on the exact timecode.
🔒 Fully local — the vision model runs on your Mac. Your footage never leaves your machine. Cloud processing is there if you need it for larger batches.
🧠 Claude MCP integration — describe the narrative you want to tell and Claude searches your visual captions and transcripts, then suggests which clips and timecodes to use. It's like having an AI assistant that's watched all your footage.
🎬 NLE export — export Boards directly to Final Cut Pro, Premiere Pro, or DaVinci Resolve. Relinks to your original raw files, no transcoding.
I built this because I genuinely needed it. If you're sitting on a drive full of footage you've never cut into anything — this is for you.
Happy to answer any questions about the model, the tech, or the roadmap. Would love your feedback! 🙏
Report
How does the custom vision model hold up with lower resolution or heavily compressed footage where fine details like mood or shot type might be ambiguous to detect?
For macro-level details like mood, shot type, lighting, and composition, the local vision model holds up incredibly well even on highly compressed or low-resolution footage. Because modern multimodal models are trained on a wide variety of real-world data, they analyze global color palettes, contrast patterns, and spatial layouts rather than micro-textures to determine the 'feel' and structure of a scene.
To help the model handle degraded or flat-colored footage, we do a few key things under the hood:
Dynamic Range & LUTs: For flat Log profiles (like Apple Log, S-Log, etc.) or HDR, our ingest pipeline automatically tone-maps the frames to Rec.709. This ensures the model sees accurate contrast and lighting cues rather than a washed-out, low-contrast grey image.
Smart Filtering for Fine Details: For micro-details like face indexing, we run strict quality gates. If a face is too small (under 60px) or excessively blurry, it is automatically filtered out so noisy data doesn't clutter your catalog.
Built-in System Honesty: The model is instructed to never 'guess' or hallucinate details. If compression, motion smear, or low light makes a detail ambiguous, it flags these sources of noise in a confidence_note so downstream indexing knows it’s uncertain.
In short: search queries like 'warm backlit wide establishing shot' work beautifully even on degraded footage, while the system gracefully flags or filters out fine details (like faces or small text) if the quality drops too low!
Report
The frame-level captioning on a local Mac is genuinely impressive. Searched a messy Premiere project for "low angle, golden hour" and it just worked.
How does the custom vision model hold up with lower resolution or heavily compressed footage where fine details like mood or shot type might be ambiguous to detect?
@ravzanv5o
Great question!
For macro-level details like mood, shot type, lighting, and composition, the local vision model holds up incredibly well even on highly compressed or low-resolution footage. Because modern multimodal models are trained on a wide variety of real-world data, they analyze global color palettes, contrast patterns, and spatial layouts rather than micro-textures to determine the 'feel' and structure of a scene.
To help the model handle degraded or flat-colored footage, we do a few key things under the hood:
Dynamic Range & LUTs: For flat Log profiles (like Apple Log, S-Log, etc.) or HDR, our ingest pipeline automatically tone-maps the frames to Rec.709. This ensures the model sees accurate contrast and lighting cues rather than a washed-out, low-contrast grey image.
Smart Filtering for Fine Details: For micro-details like face indexing, we run strict quality gates. If a face is too small (under 60px) or excessively blurry, it is automatically filtered out so noisy data doesn't clutter your catalog.
Built-in System Honesty: The model is instructed to never 'guess' or hallucinate details. If compression, motion smear, or low light makes a detail ambiguous, it flags these sources of noise in a confidence_note so downstream indexing knows it’s uncertain.
In short: search queries like 'warm backlit wide establishing shot' work beautifully even on degraded footage, while the system gracefully flags or filters out fine details (like faces or small text) if the quality drops too low!
The frame-level captioning on a local Mac is genuinely impressive. Searched a messy Premiere project for "low angle, golden hour" and it just worked.