Back to Blog

Two-layer workflow

How to use Eagle and ShotMind together: a two-layer video workflow

Updated July 12, 2026 · 6 min read

Eagle and ShotMind do not need to compete for the same job. One workable setup is to use Eagle for a broad cross-format reference library and timestamp notes you deliberately write, then use ShotMind to search the visible content of selected analyzed video shots when no note exists yet.

What each layer is for

Eagle's current product pages describe a cross-format design asset library with folders, tags, filters, video preview, and AI semantic search presented around images. Its Video Notes attach searchable text to timestamps that a person has already chosen.

ShotMind is narrower. It splits local videos into shots, lets you choose which shot clips to analyze, and saves AI visual descriptions, thumbnails, and a local searchable index. It does not replace Eagle's image and design asset management.

Layer 1: organize assets and known moments in Eagle

Keep images, screenshots, design references, fonts, audio, and video files in Eagle when you want one broad visual library. Use folders, tags, ratings, and filters for ownership, project, client, format, or other known metadata.

When you review a video and already know a moment matters, add a Video Note at that timestamp. The note becomes searchable and can take you back to the marked segment later.

  • Use Eagle for cross-format collection and broad library structure.
  • Write timestamp notes for decisions, lessons, or moments you deliberately review.
  • Do not assume every useful future shot will receive a manual note today.

Layer 2: search unnoted visual moments in ShotMind

Bring the local videos that need deeper visual retrieval into ShotMind. After shot splitting, choose the clips worth cloud AI analysis; full source videos stay local, while only selected shot clips are temporarily sent for analysis.

Later, search by the subject, action, setting, lighting, camera movement, or mood you remember. This can surface candidates even when nobody wrote a timestamp note for that exact visual moment beforehand.

  • Use ShotMind when the memory is visual rather than a filename, tag, or written note.
  • Review the ranked candidates and open the original footage before making an edit decision.
  • Keep broad asset ownership in the existing library instead of pretending ShotMind is a general DAM.

A practical handoff between the two layers

Start with Eagle when collecting references or documenting a known moment. Move to ShotMind when a project asks for an unnoted visual idea such as a handheld product detail, a slow push-in, or a rainy reflection hidden somewhere in the footage.

After ShotMind narrows the library, verify the original clip and bring the chosen shot into the editing, prompting, or pitching tool you already use. Neither product replaces the final human review or the editor timeline.

  • Collect and categorize the broad reference library in Eagle.
  • Record important known timestamps with Eagle Video Notes.
  • Analyze selected video shots in ShotMind when visual retrieval is worth the AI cost.
  • Search, review the source context, and continue in the production tool.

Evidence, sources, and limits

This is a workflow guide, not a customer case study. It combines Eagle's publicly documented capabilities with ShotMind's current product boundary; it does not claim that a real customer has adopted this exact setup.

For ShotMind evidence, the linked public test records a real close-up query across 163 analyzed shots and shows both useful matches and broad results that still required human review.