Runway Aleph users no longer have the option to keep an old production recipe untouched. Runway’s July 30 changelog says Gen-4 Aleph is unavailable, requests using its former identifier fail, and API users should move to Aleph 2.0. That makes this a migration problem, not a model-demo contest.
Build Your Aleph Migration Control Clip in APOB
The safest response is to replay a small, documented edit queue. Run the same source clips, preserve the same protected details, and judge the whole output rather than one attractive frame. This guide turns the official Runway API changelog and Aleph 2.0 prompting guide into a four-case Runway Aleph 2.0 test. It was checked on September 5, 2026; prices, limits, and interfaces can change.
Rebuild the edit brief before models move
Do not begin by pasting an old prompt into a new model. Begin with a one-page edit brief that separates the required change from everything the job must protect. A useful brief makes disagreements visible before credits, time, or client confidence are spent.
Source lock
Choose one untouched source file for each test and calculate a file hash if the job is sensitive. Record filename, duration, frame rate, dimensions, audio presence, and the exact in and out points. Keep that master outside the generation folder.
For a visual control, create a neutral reference clip with the APOB Runway AI video workflow or another approved source, but do not imply that APOB currently exposes Aleph 2.0 unless the live interface confirms it. The control exists to make the migration repeatable.
Requested delta
Write the change as one visible action: replace the bag, move the scene to a winter street, relight the face from camera left, or restyle the shot as silent-era film. Runway’s guide recommends a direct action verb plus the intended transformation. Keep the first prompt short enough that a reviewer can explain exactly what it asked for.
If the job needs additional motion, list it separately. Runway describes Extra motion as optional and useful when the desired movement is not already in the source or edited keyframe. Mixing transformation and motion into one vague paragraph makes failures harder to diagnose.
Protected elements
Name what may not move: identity, body proportions, product geometry, logo spelling, camera path, timing, background objects, shadows, and audio. “Keep everything else the same” is not a review checklist. A protected-elements list is.
Give each item a verification method. Identity may require a start/middle/end contact sheet; timing may require an overlay; product geometry may need silhouette comparison. The model can promise preservation, but the team still owns acceptance.
Acceptance rule
Define pass, repair, and reject before generating. For example: pass when the requested delta is visible and every protected element survives; repair when one local defect can be corrected without restarting; reject when identity, timing, or product truth changes.
Store the rule beside the source clip. A video edit migration should not quietly lower standards just because the replacement tool is new.
Divide the clip into preserve, replace, and recover zones
Mark the frame as three operating zones. The zones turn a creative instruction into a review map and prevent one successful change from hiding damage elsewhere.
Preserve zone
The preserve zone contains the elements that make the clip recognizable and usable. Outline the subject, face, hands, product, brand marks, floor contact, and any background anchors the cut depends on. Add time ranges when the protected detail only appears briefly.
Use the same overlays in your AI video editing workflow so model output and later editorial fixes are judged against one coordinate system. Do not redraw the zone after seeing a flawed result.
Replace zone
The replace zone is the smallest area that can satisfy the request. A bag swap should not authorize a wardrobe rewrite; a sky replacement should not authorize new architecture. When the edit crosses behind hair, glass, smoke, or moving limbs, flag those boundaries as high-risk edges.
Write the desired material, scale, direction, and lighting relationship, not just the object name. A bounded zone plus a precise delta gives reviewers something measurable to compare.
Recover zone
The recover zone identifies what can be restored downstream without invalidating the generation. Minor color balancing, an isolated mask edge, or a clean audio reattach may qualify. A different person, a misspelled logo, or a changed product mechanism usually does not.
List the approved recovery tool, owner, and time ceiling. If recovery exceeds that ceiling, rerun from the source instead of building an undocumented chain of patches.
Run the legacy-to-Aleph 2 migration matrix
Use four jobs that stress different edit behaviors. Keep source, duration, range, acceptance rules, and export settings constant. Change only the edit request. The Runway Edit Studio guide says an edit can cover the full video or a selected range, so record that choice for every row.
Case | Requested change | Protected evidence | Primary failure label |
|---|---|---|---|
Restyle | New visual treatment | Identity, blocking, timing | STYLE-SPILL |
Object | Replace one prop | Hands, logo, geometry | OBJECT-DRIFT |
Background | Move the setting | Subject edge, shadows | EDGE-BREAK |
Lighting | Change source and mood | Skin tone, product color | LIGHT-DRIFT |
Restyle case
Choose a clip with a clear subject and stable camera. Apply one named treatment across the requested range. Compare pose, gaze, garment boundaries, and the rhythm of motion to the source; a convincing look still fails if it rewrites the performance.
Save the exact prompt and whether a keyframe was used. The Runway prompting examples are useful syntax references, not evidence that your footage will behave identically.
Object case
Replace an object that interacts with a hand or overlaps clothing. Review its size, grip, contact shadow, reflection, and label across time. Pause at the moment of maximum occlusion; that is often more revealing than the first frame.
For a product-centered alternative workflow, assemble the source and comparison shot through the APOB AI Product Video Generator. Keep the same product reference and acceptance ledger across both routes.
Background case
Swap the setting while preserving the foreground. Inspect hair, translucent fabric, fast limbs, motion blur, and reflected color. Note whether the replacement background obeys the original perspective and camera movement.
Test one full-clip run and, if the brief permits, one bounded-range run. The point is not to declare a universal winner; it is to learn which boundary gives this production fewer repairs.
Lighting case
Specify direction, softness, color, and contrast. Compare skin and product color against the source, then inspect shadow motion frame by frame. A dramatic still can conceal flicker or lighting that detaches from the moving subject.
If the delivery also needs HDR, keep that as a separate downstream decision. The APOB HDR video workflow covers a different handoff and should not be folded into this migration test.
Grade invisible damage, not just the hero frame
Review the complete export at normal speed, half speed, and on a contact sheet. A pass needs temporal integrity as well as a strong thumbnail.
Identity drift
Compare face shape, eye spacing, hairline, skin marks, clothing seams, and accessories at the beginning, middle, and end. Give the case a binary identity verdict plus a short note. Do not average a severe identity break into an otherwise attractive clip.
Temporal drift
Overlay source and output timecode. Check entrances, gestures, camera moves, cuts, and the requested edit range. If a hand arrives late or an object changes before the approved boundary, record the first bad frame and the duration of the drift.
Edge damage
Inspect high-contrast boundaries, occlusions, reflections, fine hair, glass, text, and motion blur. Log halos, tearing, texture boil, and shape changes by frame range. Edge damage that is invisible at phone size may still fail a paid placement or future crop.
Audio check
Listen once without looking, then compare duration and sync with the source. Confirm whether audio survived, changed, disappeared, or was reattached later. Runway’s current Edit Studio documentation describes video editing settings and costs; it does not remove the need for an audio receipt.
Publish a rollback packet for the next sunset
The output of this test is not merely four videos. It is a packet that lets another editor rerun or reverse the decision without reconstructing the experiment from memory.
Prompt record
Save source hashes, prompts, keyframes, range handles, Extra motion text, model identifier, generation date, export settings, and accepted output. Add a small README that points to the approved row of the matrix.
Failure label
Use stable labels such as IDENTITY-DRIFT, RANGE-LEAK, EDGE-BREAK, AUDIO-LOSS, and PRODUCT-CHANGE. Attach the first bad frame and a short reproduction note. A shared vocabulary makes future Runway Aleph comparisons faster.
Owner
Name the person who can approve prompts, visual repairs, product truth, rights, and final delivery. One person may hold several roles, but the packet should never leave an unresolved approval with “the team.”
Retest trigger
Set the next check for October 4, 2026, or earlier if Runway changes Aleph 2.0, Edit Studio, model identifiers, limits, prices, or output behavior. The current API changelog is the first place to verify a platform change.
Run one real queue through the matrix, sign the acceptance rows, and keep the original files. That turns the Gen-4 Aleph sunset into a controlled video edit migration—and leaves a working path for the next one.
When the locked edit also needs a new soundtrack, carry the same receipt discipline into the Adobe Firefly audio three-tool test.
Sources
Be the first to like this.
No credit card needed
