A generated clip can look finished in a browser and still arrive unusable at the edit. The failure usually appears later: a soft transparency edge, missing sound, an unexplained color shift, or a frame count that no longer matches the cut. On August 10, 2026, Runway added ProRes 4444 with PCM audio and PNG-sequence export for eligible Gen-4.5 and Aleph 2 work on Pro and higher plans. That is an important delivery option, but it is not an automatic handoff contract.
This free checklist turns Apple ProRes, PNG frames, review media, and source records into one repeatable package. It starts after creative generation: make the character or source shot in APOB, continue the selected clip through a compatible Runway workflow, and test what the recipient actually receives. APOB is not being described here as a direct ProRes exporter. The point is to protect quality and accountability across the full pipeline.
CinePack Move 1 — Stop treating the generated clip as the master
CinePack 01 — Preview output is not an edit master
A preview answers one question: does the idea look close enough to continue? An edit master must answer many more. It needs an agreed frame rate, predictable color handling, sufficient image information for the next operation, intact audio when audio belongs in the deliverable, and a traceable relationship to the approved source.
The distinction matters in an AI video export because the most convenient playback file is often optimized for sharing rather than finishing. Keep the first APOB render, the selected intermediate, the Runway export, and the final editorial master as different assets. If the pipeline begins on the APOB Runway AI video page, record which model and settings created each generation rather than treating every downloaded file as interchangeable.
CinePack 02 — Three recipients, three tolerances
An editor wants playback, handles, sound, and a reliable time base. A colorist wants stable levels, a declared color interpretation, and enough image information to grade. A motion designer may need transparency or frame-level access for cleanup. Ask each recipient what they will do to the file before choosing the delivery format.
Write the answers in three lines: recipient, next operation, and unacceptable failure. “Editor / cut into 23.976 timeline / no audio drift” is useful. “High quality” is not. The line prevents a technically valid export from being approved for the wrong job.
CinePack 03 — The acceptance line
Define a binary acceptance test before export. A useful line is: the package opens in the named NLE, preserves its expected duration and frame count, carries usable transparency when required, plays synchronized audio when required, shows no unexplained color change, and includes rights and generation notes.
Date-stamp availability too. Runway’s changelog describes the new export surfaces as of August 10, 2026; plans, models, and interfaces can change. Recheck the official changelog before production and mark the check date in the manifest.
CinePack Move 2 — Fork A: one alpha movie; Fork B: recoverable frames
CinePack 04 — When a 4444 movie wins
Choose a ProRes 4444 movie when the receiver needs one manageable file, synchronized PCM audio, and an alpha-capable post-production path. Apple describes ProRes as a codec family designed for post-production; the specific format and alpha interpretation still need to match the receiving application. A single movie is convenient for editorial transfer, relinking, and review against audio.
Do not infer that every ProRes file contains useful transparency. Confirm the export actually carries alpha, inspect the edge over contrasting backgrounds, and tell the recipient whether the image should be interpreted as straight or premultiplied if that distinction applies in the toolchain.
CinePack 05 — When separate frames win
Choose a PNG sequence when recovery and frame access matter more than single-file convenience. A damaged or missing frame can be regenerated or replaced without retransmitting the entire movie. Cleanup artists can inspect individual boundaries, and a partial render can sometimes resume from a known frame.
The costs are equally real: thousands of files are easier to misname, drop, or reorder, and a frame sequence carries no embedded soundtrack. Deliver audio separately with an explicit start point. Protect the sequence with zero-padded names, a frame range, a frame count, and a checksum or inventory.
CinePack 06 — The fork card
Use one decision card for every shot:
Need | Prefer one 4444 movie | Prefer PNG frames |
|---|---|---|
One-file editorial handoff | Yes | No |
PCM audio in the same deliverable | Yes | No |
Replace a single failed frame | Limited | Yes |
Frame-by-frame paint or inspection | Possible | Direct |
Simple transfer and relink | Yes | Requires discipline |
This is not a quality ranking. It is a recovery decision. Export both for one representative shot, open both in the receiving application, and keep the path that survives the acceptance line with the least ambiguity.
CinePack Move 3 — The envelope every recipient opens before the file
CinePack 07 — Frame rate and color note
Put a human-readable manifest at the top of the folder. Record duration, dimensions, aspect ratio, declared frame rate, start time or frame, end frame, and total expected frames. Add the project color setup and how the receiving application should interpret the file. Avoid writing “normal” or “same as source.” Name the source and the intended interpretation.
The related APOB HDR-to-Runway workflow is a useful reminder that pipeline labels are not proof of a successful round trip. Compare a reference frame before and after import on the same calibrated review path.
CinePack 08 — Handles, audio, and ownership
State whether the shot includes editorial handles and how many frames exist before and after the approved action. For sound, name the channel layout, sample rate, start reference, and whether the mix is production audio, a guide, or approved final sound. Runway’s update specifies PCM audio for the ProRes option; a PNG sequence still needs a separate audio asset.
Ownership belongs in the same envelope. Identify who approved the character, source image, prompt, source footage, music, and final cut. Preserve consent and licensing records. A technically perfect file is not release-ready if the team cannot show where its material came from.
CinePack 09 — Names that survive versioning
Use names that sort in the same order on every machine. One workable pattern is:
project_shot_model_generationdate_format_version_framerange
For example, atlas_sh030_gen45_20260831_pr4444_v003_1001-1120.mov tells the recipient more than final-03.mov. Never overwrite an approved version. If a frame sequence changes, increment the package version and provide a short change note.
CinePack Move 4 — A four-fault return trip through the NLE
CinePack 10 — Transparency edge
Import the candidate into the named NLE or compositing application and place it over white, black, saturated green, and a midtone image. Inspect hair, motion blur, glass, smoke, and fast edges at 100% and during playback. Adobe’s current compositing and transparency overview provides the underlying alpha-channel context; the practical pass here is visual and application-specific.
Log halos, dark fringes, clipped semitransparent pixels, and unexpected matte interpretation. A file that looks correct only over its original background has not passed.
CinePack 11 — Sound lock
Place a visible event and an audible event at the start, middle, and end. Confirm synchronization after import and after one export from the NLE. Listen to the entire clip, not only the opening. Check channel assignment and confirm that a guide track has not been mistaken for the approved mix.
If the sequence format is used, import the separate audio from the manifest’s declared start. Do not fix an offset silently; record the correction so the package can be rebuilt.
CinePack 12 — Gamma round trip
Export a short round-trip file from the receiving application and compare reference frames with the delivered master. Check faces, neutral areas, highlights, and deep shadows. If there is a difference, record the applications, versions, project settings, display path, and interpretation before changing the picture.
Avoid claiming that a codec alone caused the shift. Color differences can enter through generation, export, metadata interpretation, project settings, conversion, or monitoring. The test localizes the problem instead of guessing.
CinePack 13 — Frame-count checksum
Verify first frame, last frame, expected total, and actual total. For sequences, scan for gaps, duplicates, mixed dimensions, and nonconforming names. For movies, compare duration and time base after import. Store a file hash or package inventory after approval so the receiver can confirm that transfer did not alter the delivery.
The result should be a small failure log: test, expected, observed, owner, fix, and retest status. Official capability statements belong in the source column; observed results belong in the test column.
CinePack Move 5 — Ship two speeds and one paper trail
CinePack 14 — Archive master
The archive package contains the accepted master or frame sequence, separate approved audio where necessary, manifest, generation notes, rights records, reference still, and checksums. Keep source and derivative files distinct. Store enough information to rebuild the approved output without depending on a browser history or a person’s memory.
Use the loss-resistant format that passed the receiving workflow, not automatically the largest file. The archive is valuable because it is understood and recoverable.
CinePack 15 — Review proxy
Make a lightweight proxy for comments and approvals. Burn in project, shot, version, frame count or timecode, and an unmistakable “review” label. The proxy should be easy to play but impossible to confuse with the master. Link every note to a frame or timecode and keep the approved proxy beside the master manifest.
CinePack 16 — Provenance ledger
Close the folder with a source ledger: source asset, creator or licensor, consent status, permitted use, model and generation date, editing tools, approvals, and final destination. Add the free checklist itself: recipient named; acceptance line agreed; format fork tested; manifest complete; alpha, audio, gamma, and frame count passed; master and proxy separated; rights packet present.
Recheck Runway’s changelog on September 30, 2026, or sooner if its plans, model coverage, export surfaces, or documentation change. Then rerun one representative ProRes video and one PNG sequence through the same NLE. The deliverable is not the codec label. It is the package that arrives, opens, and can be defended.
Sources
Be the first to like this.
No credit card needed
