Thanksgiving recipe video music: a 60-second acoustic bed

For a Thanksgiving recipe video, ask for a 60-second warm acoustic bed with banjo, guitar and light percussion, and place a small lift at 0:40 where the plated dish appears. On Sume that is one generation at $0.125 and a one-minute render at $0.10, so $0.225.

Cooking videos have a rhythm of prep, cook, plate. The brief mirrors it: a light start for the prep, a steady groove for the cooking and a gentle lift when the dish is plated. Seasonal warmth comes from the instruments, not from a song name.

The brief to send

The marker structure below links the music to the three phases of the recipe.

curl -X POST https://api.sume.com/v1/music-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: thanksgiving-recipe-video-music-a-60-sec-001" \
  -d '{
      "model": "sume/music-auto",
      "prompt": "Warm autumn kitchen music, 104 BPM, G major. Acoustic guitar, soft banjo, upright bass, light shaker and brushed snare. [0:00-0:20] Light prep groove. [0:20-0:40] Steady cooking groove. [0:40-1:00] Gentle lift for the plated dish. Homey, natural, close production. Instrumental, no vocals. A 60-second track."
    }'

Why each axis is set that way

Getting the length right

The 60 seconds go in the prompt, because duration fields are rejected. If the cook speaks, use the voice as the spine and add duck_db. If the video is text-overlay only, use a silent spine and set gain_db so the bed is comfortable.

A recipe is one minute, which is one started minute. A 61-second edit would bill as two, $0.20, so check the timeline before you render.

Before paying for a render, call POST /v1/timeline-1.0/plan with the same body. It is unbilled and reports the billable minutes, which for this 60-second video is 1. Then send the real POST /v1/timeline-1.0/render with an Idempotency-Key, wait up to 30 seconds in sync mode, and poll GET /v1/jobs/:id/status if it is still queued or processing. Statuses are queued, processing, completed, failed and canceled, and a 429 queue_full means try again shortly.

What it costs

A holiday series of five recipes, each with its own bed, is five generations and five renders, $1.125. Reusing one bed across the series is one generation and five renders, $0.625. The choice is brand consistency versus variety. Scaling is simple arithmetic. One finished video here is $0.225 of audio and assembly, so ten of them are $2.25 and fifty are $11.25, before any retries. Failed jobs are not billed as accepted generations, but a regeneration you ask for is a new job, so budget one or two extra takes for a hero clip.

Check before you publish

Prepare a few weeks early; holiday content is crowded in November.

Keep each season's prompt so next year's batch starts from a working brief.

The hand-off between the two calls is the step people miss. When the music job completes, GET /v1/jobs/:id/result returns result.artifacts[] with an audio/mpeg file on media.sume.com. Timeline only accepts workspace media URLs, so import any outside file through POST /v1/media-imports first, and send the resulting URL as soundtrack.url. The Music docs also note that job.request.routed_model names the engine that actually ran, which is worth saving with the file.

• Do not name a specific song or artist in the prompt.
• Check allergen and safety text on screen; the music does not cover that.
• Keep the bed under the voice so the steps are clear.
• Confirm usage terms for generated music with Sume before posting sponsored recipes.