Megaphone

Clip Studio — keep scrolling, the strip comes apart

One long video.
A month of shorts.
Every one your call.

1 · .91That's exactly how it went1:12:40 · 38s
2 · .88Twenty bags and he still—0:24:03 · 41s
4 · .71This is the pull that broke us1:41:10 · 42s
6 · .64Everyone said it was unlucky1:47:22 · 35s
7 · .61The part he cut out0:09:55 · 27s
9 · .58So — oh1:38:41 · 29s
11 · .54Wait, say that again1:33:02 · 44s
0:00:00

Drop in the episode. Megaphone transcribes it, proposes the moments worth cutting, and hands them over as clips you crop, caption and schedule.

That run, in figures

A two-hour episode costs two requests and about 400 KB to put on screen. Frame count is fixed, so a six-hour source costs the same as a one-hour one.

1:52:07source duration
42,118words transcribed
240frames · one sheet

Five stages, five separate authorities. Never one spinner.

01UploadMultipart and resumable. Close the tab; it keeps its place.476 parts
02PreprocessA proxy and one 240-frame sheet, so nothing seeks video later.18m 41s
03TranscriptWord-level timings — the source for captions and cut points alike.42,118 words
04DetectionMoments proposed with a hook line and a score, ranked for you.6s ago
05RenderBurn the captions, cut the vertical, post it on the day you chose.2 of 5

A run can hold a finished transcript and a stuck render at the same moment. Merging that into one bar would be a lie, so we don't — only the stage that failed reports a failure, with the code and the fix.

Try it here. Keep two, reject one.

The real gallery behaviour, running on this page. A rejection needs a reason and stays in place at 40% — what you turned down is half the signal about what you want.

2 kept · 1 rejected · 3 still open
1 · .91
That's exactly how1:12:40 · 38s
2 · .88
Twenty bags and he0:24:03 · 41s
rejected
Nobody move, nobodyAudio clipped
4 · .71
This is the pull that1:41:10 · 42s
5 · .68
So — oh1:38:41 · 29s
6 · .64
Everyone said it was1:47:22 · 35s
3 candidates still waiting on you.
Twenty bags and he still—

Your crop. Your captions. Your call.

Move the frame, hold the subject, trim the ends against real frames rather than guessing at seconds. Captions come from the transcript, so fixing a word is a text edit — not a re-render and a prayer.

Framing9:16 · subject centred, nudged 40px left
CaptionsFrom transcript · per-word highlight on
In / out0:24:03 → 0:24:44
DestinationsTikTok · Reels · Shorts

Burned in by the renderer, not the browser

You pick the clips. Not the model.

What's in the run

Six rows · M2 marked honestly
Candidate reviewEvery proposed moment, ranked, with hook, timecode and score — and a required reason on reject.shipping
Transcript captionsWord-level timings, editable as text. A typo is a text fix, not a re-render.shipping
Crop and framing9:16 vertical with the subject held where you put it, trimmed against real frames.shipping
SchedulingDay and time per clip, inside the same run rather than a second app to paste into.shipping
PublishingConnect an account once; it becomes a target you pick per clip.shipping
Caption presetsSaved burn-in styles beyond the single built-in treatment.next

The things people ask first

Most of it is upload and transcription; detection and render are quick by comparison. You don't have to sit and watch — every stage keeps its own state, so you can come back and see exactly where the run got to.

No. A clip has to be kept by you, then rendered, then scheduled. Three of those are your decision, and a rejected candidate stays in the gallery as a record rather than quietly disappearing.

Both are yours. Captions are generated from the transcript and editable as text; the crop, the subject position and the in and out points are all adjustable before anything renders.

It stays in the gallery at its original rank, at 40% opacity, with the reason you picked. A rejection is half the signal about what you actually want, so it stays visible.

The vertical destinations you connect to your workspace. Connect once and the account becomes a target you can choose per clip when you schedule it.

Only the stage that actually failed reports a failure — the ones after it read blocked. You get the sanitized failure code, a sentence about the cause, and a retry for that stage alone rather than the whole run.

01:52:07 — end of run

Bring your last episode. Leave with next week's posts.

One video is enough to see it work. If the moments aren't in there, you've lost an afternoon of uploading and nothing else.

Megaphone
PrivacyTermsSub-processorsSecurityContactMockup · real frames pending