Real estate price change: update the video text without a new render
When a listing price drops, re-burn the price on a clean master clip with one $0.20 caption job instead of re-rendering the whole tour. How to set it up.

To update the price in a real estate listing video after a price change, keep a clean master render with no text on it and burn the price with a Video captions job using cues. One caption job is $0.20 for a video up to 60 seconds, against a Timeline 1.0 render of $0.10 per output minute plus whatever generation made the footage. The old burned-in price is the problem this avoids: text burned into pixels cannot be edited, only re-made from a version without it.
Keep two files per listing
The first is the clean master: the photo or clip tour with no price, address or status text. The second is the published version, which is the master plus a caption job. Store the master's media.sume.com URL with the listing record; never caption the already-captioned file, since the new text would sit on top of the old.
| File | Contains | On a price change |
|---|---|---|
| Clean master | Photos or clips, music, transitions | Untouched |
| Published version | Master plus cues for status and price | Re-made from the master with new cues |
| Cue list | Text, start and end per cue | Edit the price cue only |
The caption call
Send the master as video_url with cues such as a status cue "Price improved" and a price cue, each with text, start and end in seconds, plus an Idempotency-Key so a retry does not double-bill. script_text, words, cues and segments are mutually exclusive, and design can move the line with placement.anchor_ratio. The job is async by default; poll GET /v1/jobs/:id/status and read GET /v1/jobs/:id/result for the new video_url.
Before you publish
A price on screen is a claim; make sure it matches the listing. Platforms that already carry your old video need the new file uploaded, since Sume does not edit a post on a social network. For a "just sold" plate rather than text, see the compose overlay version.
Sources
Related posts
More in Use cases
- Real footage plus one AI shot: do you tick YouTube's AI use label?
Mixing real footage with one AI-generated shot: YouTube asks for disclosure when the result is realistic and meets one of four tests. How to sort each shot.
- Recast one video ad with several faces: consent checklist, cost
Reuse one 15 second ad with different people via H3 Max Recast on Sume: cost per variant, the release to get from each person, and how to label them.
- Recast a video with a shot over 15 seconds: split it first on Sume
H3 Max Recast takes 5-30 s with no shot over 15 s. How to trim a long take, keep the same people on each piece, and join the results in a Timeline.
- Recover YouTube Shorts reach after reposting other creators' clips
YouTube says a channel that shifts from re-uploading to original content gets its reach re-evaluated. What is known, what isn't, and a plan using Sume.
Written by Sume