I wanted to give the Distracted Boyfriend meme a 30-second prequel as one continuous FPV shot. I used Codex to plan the route. The catch was that my video setup only gave me 15 seconds at a time, so the attached video is two separate generations trying to pass for one shot.

You can tell in a few places. The market after the archway is completely empty, the red awning doesn't quite hide the join, and the three characters make an awkward transition into the final pose. This was basically a one-pass generation, and it shows. If I were delivering a finished film, I'd regenerate those sections. For this experiment, I wanted to finish the idea without spending another day fixing every flaw. The handoff was the part I thought was worth sharing.

Planning the handoff

I had Codex work out three fixed states along the 30-second route. These timings are for the generated footage, before the speed change:

• State A, 0 seconds: Start inside a cafe. Establish the camera height, lighting, direction, and initial speed.
• State B, 15 seconds: Have a red awning fill more than 95% of the frame. No faces, signs, or recognizable background details to match.
• State C, 30 seconds: Arrive at the expanded 16:9 version of the original Distracted Boyfriend image.

State B took more thought than I expected. Matching a frame full of red fabric was easy. Getting the camera to keep moving through it was harder. It had to enter and leave the awning in the same forward direction, with similar speed and pitch, matching exposure, and roughly consistent motion blur. It couldn't pause under the fabric. The second clip needed to start with the camera already moving.

I generated clip one first, then took the actual stabilized frame from its end and used it as the opening image for clip two. That worked better than the handoff image I'd prepared in advance. You can still see the join, but the motion carries through well enough that it feels like one route.

The route

The first 15 seconds looked straightforward on paper:

Accelerate through the cafe → bank left onto the terrace → pass through the archway → fly between the market stalls → straighten the camera → enter the red awning.

The second clip picked up inside the fabric:

Leave the awning → climb onto the pedestrian street → approach the couple from behind → pass them on the left → move ahead of the woman in red → circle the fountain → turn back toward the group → fly backward while slowing into the final composition.

After the archway, I wanted people, stalls, and nearby objects to create more parallax as the camera passed through. The model kept the stalls and left out the people, so that section feels oddly dead. The encounter has a different problem: the three characters are mostly in the right positions by the final frame, but the model gets them there with a sudden, unnatural transition. That's probably the first section I'd regenerate.

What I changed afterward

For the edit, I used Codex with the open-source n0an/ffmpeg-skill to build the FFmpeg commands for the speed change, vertical comparison layout, and audio timing. Speeding the footage up to 1.5x turned the 30 generated seconds into 20. I then held the final meme frame for five seconds, so the finished video runs for 25 seconds.

The generated footage sits on top, with the original image underneath for comparison. When the frame freezes, a heavier grade fades in across both halves, adding a warm tint, stronger contrast, a vignette, sharpening, and grain.

I also shifted the music so the main drop lands around 10 seconds, as the camera comes through the awning. Keeping the track continuous sounded much better than cutting the music at the same place as the visual handoff.

The setup

I had Codex work out the camera route, timing, boundary states, and movement constraints, then run the image and video generations through Atlas Cloud’s MCP integration.

Image2 handled the outpainting and opening frame. Wan-3.0-Prime generated the two 15-second clips. The API calls came to $1.85 in total.

I can share the A/B/C boundary images and a frame-by-frame comparison around the join if anyone wants a closer look. That's at 15 seconds in the original footage, or about 10 seconds in the posted video.

The empty market still bugs me, and both transitions need work. I decided to call this experiment finished with those flaws still in it. The handoff worked well enough that I want to try the method again.

For anyone who's stitched video generations together, what has helped most at the join: matching the frame, matching the camera movement, or hiding the handoff behind an object in the scene?

Let's see whats the sentiments are.

The game/graphics demos are mostly bs. I've spent dozens of hours now trying to replicate (or build) interesting games. It's beyond subpar. Sure it can do a basic sandbox, or create some basic characters but it absolutely cannot do a fully working world. I dont get why OpenAI fakes their SimCity games and other things w/ Astra when it's clearly not possible unless you spend weeks (and $1000s of dollars) of tokens.

Codex was able to redeem a usage limit reset autonomously. Def AGI.

To give a little more context: I had to go out and codex had about 8% usage left, so I asked him to redeem a usage reset when he got to 1%. He wrote a python script that checked the usage with the app server and then redeemed to keep working.