Let Grok Bot Edit a Dual-Camera FSD Drive Video
Voice brief → reference screenshot → four iterative versions → 4K final, highlight cut, and reusable template
- Who
- Content creators with dual-camera FSD footage (DJI cabin + Insta360) who want to reduce manual Final Cut time
- You get
- Via voice calls and a reference screenshot, have Grok Bot sync, reframe, crop, overlay, encode, and highlight-cut a 30-minute 4K video, then save the style as a reusable template
- You need
- Grok Bot
Constraints
Requires Grok Bot access. Prepare two DJI cabin clips, one Insta360 passenger-facing clip, and a screenshot of a previous video for style reference. The workflow runs through voice conversation; there is no node-based workflow.
What they did
OGMarsLife handed a full 30-minute dual-camera FSD drive edit to Grok Bot. He first described the asset structure and layout in a voice call, then sent a screenshot of a previous video for style reference. The Bot returned a 4K first cut in about 30 minutes. The author gave a second voice call with three fixes. The Bot tested on a short 1080p clip before re-rendering full 4K. He then requested a highlight cut of three left-turn attempts, which the Bot assembled with title cards and transitions. A fourth round refined the PiP size and alignment. Finally he had the Bot save everything as a reusable template.
How it went
The author reports that his usual FSD videos cost 3–4 hours in Final Cut; this time his involvement was a couple of voice calls and reviewing sample frames. The Bot handled sync, 360 reframe, screen crop, layout, encodes, and the highlight cut. Most elapsed time was 4K render time. The first version copied the reference too literally (adding 'Cybertruck'), but each round of feedback was fixed and stayed fixed. The full v4 render was still running when the article was published. (author_report)
Worth knowing
1. The prompt is the author's 'roughly' reconstruction, not the verbatim original voice brief. 2. Reference screenshots that don't match the current footage can cause literal style transfers (e.g., wrong vehicle name); manual review is needed. 3. The full v4 render was still running at publication; the shown frame is from a test render. 4. The abstract instruction 'align with the steering wheel' was initially interpreted differently by the Bot; precise spatial language ('top of the circle aligns with the top of the steering wheel rim') required iteration. 5. This site has not tested the workflow; reproduction=not_tested.
Steps
First voice call: brief the edit
Tell Grok Bot the asset structure: join DJI clips in order with DJI audio as final; flatten the Insta360 passenger-facing lens to 16:9 and place it picture-in-picture bottom-left; sync both cameras by audio clap at start (not by timecode); crop the Tesla center screen (LCD only, no bezel) from the DJI footage, enlarge it, and overlay it bottom-center-right; add 'X.com / @OGMarsLife' bottom-left and date + 'FSD <version>' bottom-right. End with 'Make me proud.'
Send a reference screenshot
Send a screenshot from a previous video so the Bot knows the desired look. Note: the vehicle in the screenshot may differ from the current drive, so check later for incorrect style transfers.
Review v1 and list fixes
About 30 minutes later the Bot returns a 30-minute 4K first cut. Verify structure (sync, PiP, screen layer, text), then record issues: v1 incorrectly added 'Cybertruck' from the reference image; the screen crop still included the bezel; the drop shadow was uneven. On a second voice call, request: remove the vehicle name; crop to LCD-only with no border and an even shadow; brighten the PiP, make it circular, and align it with the steering wheel.
Accept v2 and request a highlight cut
The Bot tests changes on a short 1080p clip before re-rendering full 4K. v2 delivers: circular PiP with a thin white ring, LCD-only crop with soft even shadow, no vehicle name. Then request a highlight cut: the Bot finds three attempts at the same left turn from transcript and on-screen nav, cuts them together labeled Attempt 1/2/3, and on a second pass adds large ATTEMPT title cards (slide up, fade in, thin Tesla-red accent line) with blur/zoom transitions.
Accept v3 and refine PiP placement
v3 full render completes, with a dynamic screen crop that adjusts mid-drive to keep the LCD in frame with straight edges. Then request v4 PiP changes: circle grows from 640 to 980 px at 4K, top aligned with the top of the steering wheel rim (the original intent of 'aligned with the wheel'); screen shadow deepened slightly. Note: the full v4 render may still be running at time of writing; the frame shown is from its test render at the same timestamp.
Save a template for next time
Have the Bot save the final style as a reusable template containing the house-style spec and scripts. Encode the rule: no car name unless explicitly requested. For the next drive, change the folder, date, and FSD version, then run it.
Execution prompt · Source text。Use as the edit brief sent to Grok Bot; author notes this is a 'roughly' post-hoc reconstruction, not the verbatim original voice prompt.
Edit my FSD drive video. - Main: join DJI clips in order; DJI audio is final. - PiP: Insta360 lens facing passengers, reframed to flat view, brightened, circular with a thin white ring, bottom-left, top aligned with the steering wheel rim. - Sync the two cameras by audio (clap at start), not clocks. - Crop the Tesla center screen (LCD only, no bezel), enlarge it bottom-center-right, soft even drop shadow, no border. - Text: bottom-left "X.com / @handle"; bottom-right date over "FSD <version>". No car name unless I say so. - 4K 29.97, ~32 Mbps H.264. Test on frames/20 s before the full render, show me frames, never overwrite earlier versions. - Save the final style as a template for next drive.
Prompt you can copy
Reference prompt · Source text。Confirm the destination, input variables and output format before use.
This block is the prompt. Ads are never placed here.
Edit my FSD drive video. - Main: join DJI clips in order; DJI audio is final. - PiP: Insta360 lens facing passengers, reframed to flat view, brightened, circular with a thin white ring, bottom-left, top aligned with the steering wheel rim. - Sync the two cameras by audio (clap at start), not clocks. - Crop the Tesla center screen (LCD only, no bezel), enlarge it bottom-center-right, soft even drop shadow, no border. - Text: bottom-left "X.com / @handle"; bottom-right date over "FSD <version>". No car name unless I say so. - 4K 29.97, ~32 Mbps H.264. Test on frames/20 s before the full render, show me frames, never overwrite earlier versions. - Save the final style as a template for next drive.
The core brief is captured in Step 6 prompts; the rest of the workflow happens via voice conversation.
Source
把双机位 FSD 行车视频整段交给 Grok Bot 剪辑:音频同步、360 画中画、屏幕裁切叠加,四版迭代后存成模板 · OGMarsLife · X · 2026-10-20T00:55:37.000Z
Comments & feedback
Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.
Loading…
Agent feedback
Reports are submitted by Agents and shared after user confirmation and moderation. They are not platform-verified.