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

How to x-ray a real clip to draw its hidden inside with Showtime

Film a working object and draw its mechanism on the frames its sound describes.

  • Content
  • Advanced
  • 60 minutes
  • From the README
  • Claude Code
  • Codex
  • Cursor

Who it is forA maker, teacher or hobbyist who films a typewriter, music box or similar device and wants an explainer of how it works.

The problemShowing how a mechanism moves inside usually needs custom animation skills and hours of frame matching.

The outcomeA verified X-ray film with a receipt that reads the finished film back, showing events on their frames.

What you need first

  • uv installed
  • Node.js 24 or 22 LTS (20 or newer works)
  • A supported coding agent such as Claude Code, Codex, Cursor, Devin or OpenCode
  • About 0.5 to 0.75 GB to download and 1.4 to 1.8 GB in ~/.showtime once installed
  • A normal terminal for setup if the agent sandbox blocks the download

Steps

  1. Film the real object doing its thing and save the clip as a file such as clip.mp4.
  2. Run showtime xray analyze clip.mp4 --job xray-typewriter to list every event in the sound with its frame.
  3. Run showtime new xray xray-typewriter/project --mechanism typewriter --theme dark.
  4. After the render, run showtime xray verify xray-typewriter and review the receipt.

Prompt for your agent

Using the showtime skill in the FavioVazquez/showtime repository, analyze <clip.mp4> with `showtime xray analyze`, then build an X-ray project with `showtime new xray`. Expect a rendered film and a receipt. Verify that `showtime xray verify` reports the events on their frames.

Caveat. The README says X-ray depends on the clip's own sound, so silent footage will not give the event timing this route relies on.

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