# Long-recording editing brief

Prepared by Valmera. Updated September 8, 2026.
Guide: https://valmera.io/long-video-ai-editing

This is a blank planning and review template, not a measured editing result or a guarantee of processing time, cost or quality. Replace brackets with your own facts. Do not paste unknown values as facts into an editing request.

## 1. Source and deliverable

- Project name / ID: [ ]
- Source filename: [ ]
- Actual duration and file size: [ ]
- Video format: [ ]
- Upload method: [direct local file / video link]
- Transfer complete and source ready: [check actual project state]
- Part number and original timestamp offset, if split: [ ]
- Audience and purpose: [ ]
- Deliverable: [full episode / shorter highlights program / separate clips]
- Target duration and allowable variation: [ ]
- Aspect ratio and destination: [ ]
- Required captions, titles, audio and other assets: [ ]
- Delivery requirements outside Studio, such as SRT/VTT or chapter metadata: [ ]
- Deadline and usage budget: [ ]

Valmera's main direct-upload video must satisfy BOTH the displayed 14 GB file-size ceiling and the three-hour duration ceiling. The live response checked September 8, 2026 expressed these as 15,032,385,536 bytes (14 GiB) and 10,800 seconds. Supported video extensions: MP4, MOV, M4V, MKV and WebM. A valid extension alone does not guarantee processing success.

Video-link imports have separate limits; the checked configuration caps them at 500 MiB and one hour. Confirm current limits and readiness before working: https://valmera.io/docs/file-uploads and https://valmera.io/api-backend/video/limits.

Account creation and uploads are free. A subscription is required before indexing and agent editing begin. Editing usage is metered; useful analysis-only agent replies can also consume credits. Check current account usage and plans: https://valmera.io/subscribe.

## 2. Source map and protected material

Use ORIGINAL-SOURCE timestamps here. Say explicitly when a timestamp refers to one part of a split recording. Verify important transcript statements against the recording.

| Source start–end | Topic / evidence | Keep, consider cutting, or uncertain | Reason / material to protect |
| --- | --- | --- | --- |
| [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] |

- Exact wording or passages that must stay: [ ]
- Qualifications, questions or demonstrations needed for context: [ ]
- Names, numbers and technical terms to verify: [ ]
- Ending / sign-off to preserve: [ ]
- Material requiring human judgment before removal: [ ]

## 3. Adaptable first request

Map the topics in [source] using original-source timestamps. Identify candidate omissions and explain what would be lost. Flag unclear speech and uncertain repetition. Aim for [deliverable and duration], preserving [protected material]. Do not change the timeline in this request. If the target requires removing a major topic, identify that choice for review.

Map reviewed against the source by: [ ]
Approved structure / permitted omissions: [ ]

## 4. Sample cleanup and wider edit

- Current version before changes: [ ]
- Representative SOURCE range for the first cleanup: [ ]
- Permitted changes: [ ]
- Pauses, breathing, complete words and context to preserve: [ ]
- Preview range returned after the edit: [ ]
- What was heard or seen at the joins: [ ]
- Approved scope for further cleanup: [ ]

Do not assume every silence is unnecessary or that the last repeated take is the best. Recheck the intended meaning and actual preview before applying an approach more widely. A large runtime reduction may require editorial cuts beyond pauses.

## 5. Revision log

Name the clock on EVERY correction. Edits, rearrangements and speed changes can alter the source-to-preview mapping.

| Version viewed | Clock: source or preview | Range | Observed problem | Requested correction | Reviewed result |
| --- | --- | --- | --- | --- | --- |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] |

Separate child clip projects, if requested:

| Source range / topic | Child project | Context to retain | Format | Review and final-export status |
| --- | --- | --- | --- | --- |
| [ ] | [ ] | [ ] | [ ] | [ ] |

Finding clip candidates does not finish or export those clips. Each child needs its own editing, review and final MP4 creation in Studio.

## 6. Final review and delivery

- [ ] Correct project and intended version selected.
- [ ] Complete program reviewed, including late sections and ending.
- [ ] Questions, answers and qualifications preserve their meaning.
- [ ] Protected material and approved structure are present.
- [ ] Cut boundaries keep complete words, useful breathing and natural pacing.
- [ ] Names, numbers, captions and on-screen text checked.
- [ ] Framing, demonstrations and important screen detail remain readable.
- [ ] Speech, music and other audio reviewed through the full program.
- [ ] Final MP4 created in Studio, downloaded and played.
- [ ] Complete runtime, branding and any appended ending checked.
- [ ] Destination requirements confirmed; separate subtitle files or chapter metadata handled outside this Studio workflow if required.
- [ ] Original source and approved brief retained.

Final project / version: [ ]
Downloaded filename and runtime: [ ]
Remaining limitations or corrections: [ ]
Reviewer and date: [ ]

Final output uses original media but is re-encoded; it is not a lossless copy. Studio does not import or export SRT/VTT files. The checked external MCP workflow does not initiate final export.