Remembrance Sunday 2026: a 12-second 11am pause notice video

Remembrance Sunday 2026 falls on Sunday 8 November, and the two minutes' silence begins at 11am. A shop, club, school or council that wants to tell followers when to pause can post a 12-second notice: three of its own photos held for four seconds each, one line of text naming the time, and no sound. On Sume that is one Timeline render with a silent spine ($0.10) and one caption job with authored cues ($0.20), so $0.30 in all.

The date and the timing come from Remembrance Sunday 2026 on Awareness Days, read on 2026-10-12. The Sume side comes from the Timeline and video captions docs, read the same day.

What are the facts to put on screen?

Awareness Days says Remembrance Sunday is always the second Sunday in November, the Sunday nearest to Armistice Day on 11 November, and that the silence begins at 11am and lasts two minutes. Put only those facts on the card, and publish before 11am on the day.

Why use your own photos and no sound?

A notice for a solemn moment should not be a generated scene. Image and video models can get uniforms, medals and memorial inscriptions subtly wrong, so use photographs you took of your own memorial, shopfront or staff, or ask the community group that owns the image. Silence also suits the message: Timeline accepts audio.mode: "silence", which declares an output length with no spine file.

How do you build it?

Import the three photos first (POST /v1/media-imports), because Timeline accepts only this workspace's media.sume.com files. Stills are static holds, so each slot is a four-second hold with a half-second fade into the next. Run the unbilled plan call first; it returns the duration, segment count and estimated cost before you spend anything. Swap /plan for /render (add an Idempotency-Key header) when the numbers look right.

curl -X POST https://api.sume.com/v1/timeline-1.0/plan \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "audio": { "mode": "silence", "duration_seconds": 12 },
    "video": [
      { "source_url": "https://media.sume.com/artifacts/artf_demo/one.jpg",
        "start": 0, "duration": 4 },
      { "source_url": "https://media.sume.com/artifacts/artf_demo/two.jpg",
        "start": 4, "duration": 4,
        "transition": { "type": "fade", "duration": 0.5 } },
      { "source_url": "https://media.sume.com/artifacts/artf_demo/three.jpg",
        "start": 8, "duration": 4,
        "transition": { "type": "fade", "duration": 0.5 } }
    ],
    "output": { "fade_out_seconds": 1 }
  }'

How do you add the words without speech recognition?

The clip is silent, so a normal caption job would fail with caption_no_speech. Send cues instead: each cue is text with a start and end in seconds, and Sume burns exactly that text. The input video_url must be a public HTTPS URL, such as the finished Timeline artifact.

Two cues are enough: "Remembrance Sunday, 8 November" from 0.5 to 5 seconds, and "Please join us in two minutes' silence at 11am" from 5 to 11.5 seconds. For a plain look, pick the slam style or restyle later with source_caption_id; the docs say a restyle is still a render and costs the same.

Rates move, so confirm them in GET /v1/catalog before a batch. If you run this for several branches or schools, give each job its own idempotency key so a retry cannot render twice.