Edit package
Scenes, shots and expected takes for the cutting room — as an ALE for Resolve and Avid or as JSON. Where each column comes from and where you enter it.
What was decided and written down on set is what the cutting room needs: which scene in which order, which shots were planned and which takes the sound and daily reports record. The edit package brings exactly that together — always built the same way, without AI. It invents nothing: every column comes from a field someone filled in on set. If something stays empty there, it stays empty in the edit package too.
What is in it
- Scenes in screenplay order, with number and heading.
- Shots per scene with size, movement, lens, description and the storyboard frame.
- Expected takes from the sound and daily reports: scene, slate, take, circled take, sound file and timecode. Takes whose scene number no scene of the project carries come along separately — the cutting room needs them all the same.
- Marker suggestions for the timeline: where a scene begins and what sound noted on a take.
Takes and daily reports are only included if you may read them in the project's account. Everything else follows your right to read scenes.
Where the ALE file gets its data
Each line of the ALE file is a recording from a shooting day's sound report: Shooting days → open the shooting day → Sound report tab → Recordings. The columns come about like this:
| Column in the ALE file | What Resolve and Avid do with it | Where you enter it |
|---|---|---|
| Source File | find the clip by it | the recording's File name — exactly as on the recorder, with extension, such as A001_T01.WAV |
| Name | show it as the clip name | comes from the File name without extension |
| Start | also match the clip by its timecode | the recording's TC start |
| Tape and Soundroll | assign the clip to its sound roll | Sound roll at the top of the sound report — applies to all recordings of that sound report |
| Scene | scene on the clip | the recording's Scene — written as in the screenplay, such as 12A |
| Slate | slate on the clip | Slate |
| Take | take on the clip | Take |
| Circled | circled take, Yes or No | the Circled tick on the recording |
| Comments | comment on the clip | the recording's Notes |
1 Circled → Circled. 2 Scene → Scene. 3 Slate → Slate. 4 Take → Take. 5 File name → Source File and Name.
If the row is wider than the screen, swipe it sideways. 1 TC start → Start. 2 Notes → Comments.
The file's header comes from the sound reports too:
- FPS from the Timecode setting at the top of the sound report — the frame rate that appears most often in the project's sound reports; without one, 25.
- The audio format from Sample rate (Hz) — the project's most frequent one; without one, 48 kHz.
- The video format is always set to 1080.
1 Sound roll → Tape and Soundroll of every recording in this sound report. 2 Sample rate (Hz) → audio format. 3 Timecode → FPS.
Where the JSON gets its data
The JSON contains everything from the ALE file and, in addition:
| Part | What | Where you enter it |
|---|---|---|
| Scenes | number, heading, content, order | the Scenes tab or the Screenplay |
| Shots | number, size, movement, lens, description | the Shot list tab |
| Storyboard frames | the frames per shot | the Storyboard tab |
| Daily report per scene | Takes, Circled, Selects, Notes | shooting day → Daily report tab |
| Marker suggestions | every scene start with number and heading, every recording with a note | come from the scenes and the recordings' Notes |
So that everything ends up in it
- Create a sound report for each shooting day. Without a sound report the ALE file has no line for that day. The Sound reports tool must be switched on in the project — see Editing a project.
- Enter the file name exactly as the recorder writes it. Otherwise Resolve does not find the clip.
- Set TC start and the frame rate under Timecode as on the recorder. Resolve also matches clips by their timecode.
- Write the scene as in the screenplay. Upper and lower case and spaces do not count:
12ais12A. A number that does not exist in the project still appears in the ALE file, and in the JSON under the takes without a scene. - Tick circled takes. Only then does Circled say
Yes. - Check the reading rights. Takes are only included with View sound reports, the daily report's lines only with View daily reports — each in the project's account.
Downloading
- Open the project's Overview.
- Tap Edit package at the top.
- Choose the format:
- ALE for Resolve and Avid — the recordings from the sound report with file name, sound roll, timecode, scene, slate, take and circled take as a metadata table both programs import.
- JSON — the whole package with scenes, shots, expected takes and marker suggestions for your own tools.
1 ALE for Resolve and Avid. 2 JSON.
The file carries the project's name. The edit package needs a connection to the server.
In DaVinci Resolve
- Import your recordings into Resolve's Media Pool.
- Choose File → Import Metadata To → Media Pool and the ALE file. Resolve matches each line to a clip by file name and timecode; scene, slate, take and circled take then sit on the recordings as metadata.
- Sort or filter the Media Pool by scene or by circled takes.
With a connected AI assistant it goes further: the recipe Prepare DaVinci Resolve for the edit creates bins per scene and shot from the edit package, writes the metadata onto the recordings and hands the screenplay to IntelliScript as a Final Draft file. For that the assistant also needs Resolve's own MCP access.
Through the interface
Programs and assistants fetch the same package with the operation Get a project's edit package — as JSON, or with format=ale as a file. The address is listed under Operations.