Remotion Vlog

Turn raw outing footage into a short story that remains easy to inspect and revise as a Remotion project. Preserve the original media and treat the user's editorial exclusions as hard requirements.

Interpret the request

• Resolve the requested camera or mounted volume, date scope, output folder, title, people, place, and render gate from the user's messages. Treat “today” using the user's local timezone.
• Inspect files and metadata before choosing clips. Do not mix in footage outside the requested event merely because it is adjacent on disk.
• If the destination or event can be inferred confidently from the footage and request, proceed. Ask only when two materially different events remain plausible.
• Prefer an existing Remotion project in the requested output folder. Create a new one only when none exists.
• When available, load remotion-best-practices before editing Remotion code. Use a speech-cleaning workflow only when spoken content determines the cuts.

Protect the footage

• Never modify, rename, move, or delete camera originals.
• Put selected, trimmed, consistently encoded proxies under the Remotion project's public/ tree. Keep temporary transcripts and contact sheets outside the project unless the user asks to retain them.
• Preserve unrelated user changes in an existing project.
• If the user wants to eject a camera or card, copy only the selected source originals when capacity allows, then verify every destination against its source with a byte comparison or checksum before saying it is safe to eject. If capacity only permits proxies, say explicitly that full originals were not preserved locally.