The Righteous Stress Test: Neural Frames — Dry Run, No Edits
Share
DRY RUN — NO EDITS.
Watch both original dry runs below. Each video opens in Google Drive and is available to anyone with the link. Both are unchanged first outputs created with the app's built-in templates, backgrounds and AI characters.
Disclosure: This test is part of a paid collaboration with Neural Frames. This article includes an affiliate link that may earn us a commission. Our observations and conclusions are our own.
Before you start fixing an unfamiliar creative tool's output, learn what it produces on its own. That's the purpose of the Righteous Stress Test: complete a project using built-in templates, preserve the original, examine the result, and only then decide what deserves editing.
The test setup
We used the Jack Righteous recording Made to Spark and Neural Frames' built-in background templates and AI characters. We generated one full-song landscape video and one Lyric Pro short-form vertical video. No post-generation editing or visual corrections were performed. These are baseline experiments, not polished final productions.
Test 01 — Full-length music video (3:33)
DRY RUN — NO EDITS
Landscape; approximately 3 minutes 33 seconds; 1344 × 768; 24 fps. The sampled visuals show warm amber lighting, recording-studio imagery, a recurring AI performer, and changing compositions. The open questions are how well the full sequence follows the song, whether camera changes are meaningful, and whether the character remains convincing in motion.

Watch the original full-length video (3:33)
Original unedited MP4 · Opens in Google Drive in a new tab
Test 02 — Lyric Pro short-form (0:30)
DRY RUN — NO EDITS
Vertical; 30 seconds; 720 × 1280; 25 fps. Sampled frames show a recurring performer in an industrial hall with brass instruments, changing camera distances and a consistent setting. The full moving sequence still needs checks for vocal timing, lyric accuracy if displayed, lip synchronization and opening impact.

Watch the original Lyric Pro short (30 seconds)
Original unedited MP4 · Opens in Google Drive in a new tab
Our seven-step method: how to repeat the test
The goal is to understand the tool before deciding what to edit. You can try this with one song and one short sample if credits are limited.
- Define: Choose a completed song and write one objective, such as “generate a vertical clip using an app-provided performer.”
- Explore: Record the workflow name, available templates, selected background and AI-character options.
- Generate: Complete the first output without post-generation changes. Check the credit estimate before starting.
- Preserve: Download and label the file DRY RUN — NO EDITS; do not overwrite it with revised versions.
- Observe: Watch the complete result once for overall feel and again for precise issues. Note timestamps.
- Identify: Separate defects (e.g., incorrect timing or changing facial features) from preferences (e.g., wanting a darker environment).
- Refine later: Prioritize a few specific changes and compare the next output with the untouched original.
Our test log: Made to Spark
| Field | Full-length video | Lyric Pro short |
|---|---|---|
| Song | Made to Spark | Made to Spark |
| Objective | Explore full-song visual generation | Explore 30-second vertical lyric-focused workflow |
| Duration | 3:32.8 | 0:30 |
| Output | 1344 × 768, landscape, 24 fps | 720 × 1280, vertical, 25 fps |
| Assets | Built-in backgrounds and AI characters | Built-in backgrounds and AI characters |
| Post-generation edits | None | None |
| Specific template/model settings | Not recorded | Not recorded |
| Credits consumed | Not recorded | Not recorded |
| Generation time | Not recorded | Not recorded |
Not recorded means the detail was not captured during the first run. It is not an estimate.
Try it yourself: a ten-minute review
After generating one clip, identify one strength, one technical concern and one creative preference. Record the timestamp of each. Then decide which single correction you would test first. A useful result is a prioritized edit plan, not a perfectly generated first take.
What the first results show—and what remains open
Neither a good-looking still nor a poor stylistic match alone proves that the application succeeded or failed. The original videos are provided so readers can judge the results directly.
What we would improve next
After complete playback review, identify scene-by-scene needs: replace inconsistent shots, correct lyric timing, change repetitive camera angles, adjust performers or pacing, and evaluate how much extra time and credit usage those changes require. Preserve the originals to measure what genuinely improved.
Why no edits?
An untouched initial generation is valuable evidence. It exposes the default workflow and lets other creators understand how far automation takes them before deliberate direction begins. The first run is about understanding the tool; the next run is about directing it.
Takeaway
Use what the app already offers. Make something complete. Watch carefully. Understand the limitations. Then refine with intention. DRY RUN — NO EDITS.
Read our Neural Frames app overview.
Create What You Love | Love What You Create.