Skip to content
Podcast Season Planner

12 eps × 90 min — what plan survives?

18.0h transcript · 49 GB
36 renders
Free 2h ✗ — Creator 4h ✗ — Pro 8h ✗ — need Studio 70h or split season
180-day retention — your April ep still there in September.
Sermon Year Archive

52 Sundays — what does the year cost?

4.1 GB / week · 211 GB / year
Overage $2.42/mo after Pro
Studio 1500GB flat $119 beats overage at week 31.
Chapter Builder

YouTube chapters in one paste

MCP weaverclip_bulk_create_edits — copy into description.

Course Module Planner

Before you record lesson one

8.0h transcript · 22 GB
40 lessons — 180d retention through launch
Fits Pro
Disk-Full Clock

When does your drive fill?

Your 2TB drive, your schedule, your bitrate — one date.

2.70 GB/h · 32.4 GB/week

15.4 weeks
Fills on (108 days)
Need ~139 GB vault for a month of this schedule.
WeaverClip: Creator holds it — no scrubbing.
At 6 Mbps, Creator 75GB ≈ 28h, Pro 150GB ≈ 56h
OBS Paste → GB/hour

Paste your Output settings

We read VBitrate and tell you what a night costs.

6 Mbps → 2.70 GB/h
4-hour stream: 10.8 GB
At 6 Mbps, Studio 1500 GB ≈ 555h
Subathon Planner

24–72h — will you lose the best hour?

200 suggestions (capped at 200)
130 GB at 6 Mbps
Tip: split a 48h run into 3× 16h sessions to get 3×200 suggestions — use schedule_transcribe for active hours only.
Use case — gaming-streams · plain numbers

24h streams without filling your Mac or watching 24h.

One-minute MKVs, upload while you record, byte count + MD5 verified before local delete. 1.5 TB vault holds 535h at 6 Mbps, 70 transcript hours, 2000 renders. Ranked 20/h, max 200, gallery link not 130 GB attachment. Disk-Full Clock shows the date your drive dies without Weaver.

Gaming streams are long, high bitrate, and repetitive — 38% dead air. A 2 TB drive at 12 Mbps fills in 9 weeks at 10h/week. Weaver's helper uploads 1-min segments while you play, verifies, then frees the SSD nightly. The transcript counts once, dual canvas shares one transcript, and weaverclip_schedule_transcribe lets you pick the 6h where you actually talked. Biggest streamers care because they don't have 6 hours to scrub — they have 10 seconds to decide which 45s to post to TikTok.

One-minute MKVs while you play — helper uploads as you go, r

One-minute MKVs while you play — helper uploads as you go, retries with backoff, deletes only on verify

Schedule transcribe last 6h of 24h, not all 24h — save 18h o

Schedule transcribe last 6h of 24h, not all 24h — save 18h of transcript every subathon

Disk-Full Clock: drive size + free space + weekly schedule →

Disk-Full Clock: drive size + free space + weekly schedule → the date OBS dies without Weaver

Metrics strip live: Storage/Transcript/Renders/Layouts so yo

Metrics strip live: Storage/Transcript/Renders/Layouts so you see '1.2h left' before you burn it

Sharp nuances you didn't know you needed — until you're live

Disk-Full Clock — the date your drive dies

Drive size + free space + weekly schedule (days × hours × bitrate) → vault needed + overage vs Studio flat. At 75 GB vault + 10h/week at 12 Mbps (~54 GB/week), your 500 GB SSD fills in 9 weeks. With Weaver, verified uploads free the SSD nightly and the vault holds 75 GB before overage $0.04/GB. The Clock on /features/storage is a Discord flex — screenshot 'My drive fills March 14. Weaver deletes that date.' That's why biggest streamers pay attention: it's not storage, it's 'I can keep operating without scrubbing a drive at 2am.' The nuance: hard limit 2× vault (Creator 150 GB) pauses uploads, files stay on Mac — you choose delete or upgrade, we never auto-delete to make room.

24h subathon — why 200 cap and split 12h + 12h

24h at 6 Mbps = ~64.8 GB, at 12 Mbps = ~129 GB. Even Studio's 70h transcript handles one 24h fully, but the 200-suggestion cap = 8.3/h over 24h vs 16.6/h if you split 12h + 12h as two sessions (20/h × 12h = 240, capped 200 each, so ~100 each if split). For a subathon, split gives double density and two gallery links — one per 12h block — not one 24h link with 8/h sparsity. Use weaverclip_schedule_transcribe for the 6h window with sponsor read, not all 24h, to save 18h.

Dead-air reclaim — 38% you didn't know you paid for

38% of a 6-hour stream is loading, BRB, or silent — that's 2.3h of transcript you don't spend if you pick the window where you talked. Weaver shows dead-air % on the Safety Rail and lets you skip it via weaverclip_schedule_transcribe startMs/endMs. Opus would bill the whole 6h of credits; we let you bill 3.7h. For a 10h/week streamer, that's 3.8h saved weekly — 15h a month, almost a Creator Pro month. The nuance: dead air still counts as storage (~2.3h × 2.7 GB/h = 6.2 GB at 6 Mbps) but not transcript — you store 6h, transcribe 3.7h.

Agents overnight — the 24h that clips itself

An agent watches your 6h VOD, calls weaverclip_search_transcript 'world record' → 6 hits in 300ms without downloading video, bulk-creates 6 edits with Block preset, renders on helper, shares gallery link, and leaves a verified review: '6h → 6 verticals, 98% verified, host stayed at 14% disk because tmp deleted after verify.' You wake to a gallery, not a timeline. The agent workspace is isolated — its Free 10 GB/2h never touches your human vault. That's why host keeps operating without piling ffmpeg outputs.

Questions that decide the purchase — answered before you ask

Will Weaver fill my SSD during a 24h?

No. One-minute MKVs upload while you record, verified before local delete, helper retries with backoff. A 24h at 12 Mbps is ~129 GB, but it's 1440 1-min files, each verified and freed individually. Your SSD sees ~5.4 GB/hour *at most* as a rolling buffer, not 129 GB at once. The Disk-Full Clock shows the date you'd fill without Weaver.

Do I need 12h of transcript for 12h of stream?

No. Schedule the window: last 6h, or the 4h where chat was hype. Use weaverclip_schedule_transcribe startMs=6*3600000, endMs=12*3600000. You spend 6h, save 6h. The metrics strip shows Storage/Transcript/Renders live so you see remaining before you pick.

Can I record both 16:9 and 9:16 at once?

Yes via Aitum vertical + Display 1, same filename stem %CCYY-%MM-%DD_%hh-%mm-%ss. Helper pairs only on exact stem, extensions may differ. Both masters count as storage (2× bytes) but share one transcript (counts once). Each finished export counts as one render — vertical Short + square = 2 renders.

Why 20/h max 200?

20/h is ranked distinct thoughts, not loudest seconds. 24h × 20 = 480 would be noise, so we cap at 200. For a 24h, split into two 12h sessions for 100 each — better density. For a 2h pod, 40 is enough and you see them all.

Try it with the video you already have.

Free holds a full 2–3h webinar at 6 Mbps for 30 days. Upload the whole thing, download the SRT, make clips later — no re-transcribe. Every plan shows the numbers before you pay.