Nutcracker ticket promo for a dance school: one poster, one short clip

A dance school can promote its Nutcracker showings by animating one poster or set photo into a 5 to 8 second image-to-video clip and burning the showtimes and ticket link on as caption cues. The ballet itself has a long history: it premiered on December 18, 1892 in Saint Petersburg, and the full score runs about 90 minutes without intermission or applause.

Why does the Nutcracker suit a small-business clip?

Wikipedia notes the ballet is a two-act work by Tchaikovsky and that, since the late 1960s, many US companies have performed it every holiday season; major companies reportedly earn roughly 40 percent of annual ticket sales from it. For a local school the pull is the same: families buy tickets early, and the clip needs to answer when, where and how long.

The running time is a useful fact for parents planning the evening, but state your own show's length, since school productions are usually shorter than the full ballet.

How do you animate the poster?

Upload the poster or a set photo as the first frame of a POST /v1/videos request and prompt for gentle snowfall and a slow push-in. The Sume docs state that frame_images with frame_type: first_frame selects image-to-video, and that GET /v1/videos/models lists what each model supports. Keep the poster text out of the prompt; the poster already carries it.

Do not generate children's faces from a prompt for a promo. Use the real photos you have releases for, or a set and costume shot with no faces.

Where do showtimes go?

Burn them on with cues: "The Nutcracker", "Sat Dec 12, 2 pm and 6 pm" (use your real times), "Tickets at the front desk or online". Authored cues avoid speech-to-text, so a silent clip works. Check the finished MP4 for spelling, particularly the date.

If you also want a logo card on screen, timeline compose combines one hosted still and one hosted video in a single MP4 for a flat $0.02 per job per the docs, and the still never lengthens the clip.

What is the lead time?

Plan the production in three jobs (video, optional compose, captions), each polled to completion. Run them a few weeks before your on-sale date so you can re-roll a clip that looks off.

Which model should you pick, and how do you keep spend bounded?

Do not guess at model limits. The Sume video guide says to read GET /v1/videos/models before submitting, because limits differ per model: for example wan-3.0 accepts 2 to 30 seconds, seedance-2.5 accepts 4 to 30 seconds at 480p, 720p and 1080p, and gemini-omni-flash-1.1 accepts 3 to 10 seconds. The same catalog carries pricing_skus, so you can read the price of the length and resolution you want before you spend anything.

For a social story, a short clip at a modest resolution is enough; a higher tier costs more and a phone screen rarely shows the difference. Draft once at the lowest tier that looks right, check the cues and the dates, and only then decide whether a second render is worth it.

Keep the idempotency habit too. Where an endpoint requires an Idempotency-Key, reuse the same key when you retry the same request so a network error does not create a duplicate job.