Creatify Boreal-H3 runs 5 to 15 s; Sume H3 Max lip sync stops at 14.8
Creatify's changelog lists Boreal-H3 at 5 to 15 seconds. Sume's H3 Max lip sync accepts 5 to 14.8 and rejects 15. How to trim a 15.0 s line, and the cost.

Creatify's API changelog lists a Boreal-H3 model for clips of 5 to 15 seconds, while Sume's H3 Max lip-sync route accepts 5 to 14.8 seconds and rejects anything outside, including exactly 15. If you are porting a 15-second job, trim 0.2 seconds from the audio before you submit, or the request fails. The route never rounds a number down to fit.
Side by side
The Creatify rows are what its changelog says; I did not test its API. The Sume rows are from the repo's lip-sync doc.
| Item | Creatify (changelog) | Sume H3 Max lip sync |
|---|---|---|
| Clip window | Boreal-H3: 5 to 15 s | 5 to 14.8 s, rejected outside |
| Boreal price | boreal model_version: 10 credits per 30-second video | Not applicable |
| Aurora price | 1 credit per second; 0.5 fast (per-second billing since May) | Not applicable |
| Sume price | Not applicable | $0.0625, $0.10 or $0.20 per billed second |
| Billing unit | Credits | Dollars; ceil of duration_seconds |
Trim a 15 second line
Sume also bills on whole seconds, so a 14.8 second line bills as 15 seconds. The trim costs you nothing in price, only 0.2 seconds of audio. At 768p the line costs 15 x $0.10 = $1.50.
- Measure the audio length first.
- If it is above 14.8, shorten the text by a few words and render the voice again; do not cut the finished file.
- Set
duration_secondsto the new length, rounded to one decimal. - Submit to
POST /v1/minimax/h3-max/lip-syncwith the same still. - If you cannot shorten it, split the line into two segments of at least 5 seconds.
A caution on the comparison
I do not know from the changelog whether Boreal-H3 is a lip-sync model, a general clip model or something else, so I do not compare quality. What the two share is a short window with a hard upper limit, which is the thing that breaks a migration. Check the model's page for what it does before you plan around it.
Cost at the edge of the window
Here is what the limit means in dollars on Sume. A 14.8 second line and a 14.0 second line both bill 15 and 14 seconds, so the difference is one billed second: 10 cents at 768p and 20 cents at 1080p. Tightening a script to fit therefore saves little money; the real value of trimming is that the request is accepted at all. A batch of fifty 15.0 second lines, all rejected, costs nothing but returns no video, so test the first line before you queue the rest. The same preflight is also a good place to check the still: its width over its height has to sit between 0.4 and 2.5.
What Sume does not do
Sume does not extend the window, and it does not clip the audio for you. For lines longer than 14.8 seconds the packet guidance is to use Fabric, which accepts up to 300 seconds, or to split at a sentence end.
Sources
Related posts
More in Comparisons
- Custom avatars per plan: HeyGen, Colossyan, Tavus, Teams, Sume
Custom avatars each plan lists: HeyGen 1 to 10+, Colossyan 15 or 20, Tavus 0 to 7, Teams 3. Sume prices each new avatar at $0.95; no plan cap is listed.
- Deepgram Flux TTS: text_spoken and barge-in vs Sume voiceover jobs
Deepgram's Flux TTS reports text_spoken and text_remaining when a caller interrupts. Sume has no barge-in, but word timestamps can mark a cut point.
- Descript Creator 3-person teams vs Sume workspace API keys
Descript lists Creator at $24 for 3-person teams and Business at $50 for 5. Sume API keys are workspace-scoped and spend from one USD balance, no seats.
- Does dictation audio leave your device? Fireflies, Phonon-2, Sume
Fireflies Talk keeps finished dictations local but sends audio to its STT provider. Phonon-2 runs on device. Sume STT is hosted. A sourced privacy comparison.
Written by Sume