County fairs: midway stills plus hours, not a Veo crowd of fake faces

Lock the Ferris wheel you actually booked. Recurring daily hours. Do not fill the midway with generated children.

A county-fair clip that can run is a still of this wheel, this ticket booth, this barn — then a little motion, then the hours as type you typed. It is not a Veo crowd. Photoreal children the model invented are a likeness problem and a line you should not cross. Photograph the empty-enough midway you control. Animate that. Print today's hours. Leave the faces out of the generate.

The wheel in the still has to be the wheel on the grounds

Booked rides have permits, paint, and a silhouette a local will recognise. A paragraph that says "Ferris wheel at dusk, happy families" will mint a cousin wheel and a crowd you do not have releases for. Frame the real machine: same spokes, same lighting towers, same barn roof behind it. Dawn, empty, or staff-only is a legal still. A packed midway of generated kids is not.

Ordinary image-to-video moves that photograph. It does not get to populate the foreground with people. Prompt the travel — slow clouds, a wheel that is already in the still, light on the steel. Stop. "Children running with cotton candy" is a second job, and it is talent you did not hire. Keep lips and minors out of the generate.

/for/event-venues is a ballroom and a floor plan. It is not the fair's booked wheel. Do not rewrite that page as a midway, and do not import a venue crowd onto the grounds still.

Wan 2.5 I2V is the cheap silent hold on the locked plate

Wan Video 2.5 Image to Video is high-quality image-to-video. It requires an image. Audio is false. Durations: 5s and 10s. Ceiling 1080p. Display price 15 credits. The still is the brief. The model moves it.

Fifteen credits is cheap enough to retry, not cheap enough to retry the wrong label. No still, no generate. A Veo-shaped paragraph where the Ferris wheel should be is a wrong label. Every second of the 5s or 10s is waste — and a crowd the sampler will gladly invent if you ask.

The AI image-to-video tool is the door. Medium motion on an approved wheel is often the whole job. High motion on a busy unapproved plate is ten seconds of confident drift and extra limbs. 1080p will faithfully resolve whatever you uploaded, including a generated toddler you should not have prompted in.

Silent is the spec. Prompting a carnival calliope here does not buy a bed. It may paint notes on the sky. Score later. Hours are not speech. Hours are overlay.

Do not "fill the midway" in the prompt to make the still look open. Open is a photograph of opening night, with people who were actually there, releases in the folder. Generation is not a crowd-size slider.

Hours are a line you burn. The series is a new hours card, not a new crowd.

Add a text overlay to a video stamps one authored line on the whole file — top, center, or bottom. "Gates 10–10. Tonight: demolition derby 7pm." That string changes. The wheel does not. Burn hours after picture lock and after the crop. A 16:9 overlay that then gets mashed into Stories sits in the chrome.

Run a recurring video series is schedule_workflow on a saved scene workflow: each tick, a fresh plot around the same characters, style, and assets, then a full generate, optionally auto-posted. For a fair, the asset map is the booked-wheel still (and only that still). The premise is today's hours and tonight's named event — type, not a new population. Each run is priced like a full video-workflow generation, charged when that run actually generates, not when you set the clock.

That is the dangerous edge. A series that "writes a new episode" will invent a new midway if you let the plot roam. Pin the still. Tell the workflow the crowd is out of scope. If you needed the identical MP4 every weekday, you wanted a scheduled post of a finished file, not a scheduled generate. If you needed new hours on the same steel, keep the steel. Change the overlay line. Do not let the tick become a Veo crowd of fake faces.

Cron is UTC. "9am" without a timezone is accepted as UTC. Wrong hour for a week is still a week of generations if the workflow ran.

Veo is the wrong population engine

A cinematic talking row with native audio will happily build a packed fairgrounds from a sentence. That packed fairgrounds will include children the model invented. Do not do that. A silent wheel on Wan is the fair job. A real photographer on opening night is the people job. There is no third job called "generate the crowd so the grounds look busy."

If a 4-H clip needs faces, those faces are members you have permission to show, on footage you shot. Generation stays on the ride, the empty aisle, the hours.

The test is a pause. If a local can name the wheel, you locked the right still. If a parent might ask who that child is, you shipped a replica. Recurring hours do not require that replica. Print the time. Leave the midway as you photographed it.

FAQ

Can we add a generated crowd so the grounds look open?

No. Photoreal children and constructed faces are a likeness problem. Photograph opening night with real people and releases, or keep the still empty-enough and overlay hours.

Does Wan 2.5 I2V include a carnival soundtrack?

No. Audio is false. You get a silent 5s or 10s file at up to 1080p for 15 credits. Score after lock. Hours are overlay, not Wan glyphs.

Is a recurring series the same as posting yesterday's clip every morning?

No. schedule_workflow generates a new video each tick. Re-posting a finished file is the social scheduler. Pin the wheel still so the new tick is hours, not a new crowd.

Why not Veo for a more "cinematic" fair?

Veo will invent a packed midway. That packed midway will include fake faces. The fair job is the booked wheel plus hours you typed.