AI media harness for planning, generating, and editing locally
TypeScript
Report 23 MB a minute, not 11.5
Bittie9d0a67e8299
diff --git a/src/components/workspace/ExportView.test.tsx b/src/components/workspace/ExportView.test.tsxindex c0ee105..b50cf3c 100644--- a/src/components/workspace/ExportView.test.tsx+++ b/src/components/workspace/ExportView.test.tsx@@ -88,7 +88,7 @@ describe("the export view on media the project does not contain", () => {});/* The mix is built whole in memory before the file is opened and held until the- last frame — 11.5 MB a minute, 1.4 GB for an hour — and the panel that states+ last frame — 23 MB a minute, 1.4 GB for an hour — and the panel that statesbitrate, size estimate, compositor and codec said nothing at all about it. */describe("what the page says the soundtrack will cost", () => {const withAudioSupport = (body: () => void) => {diff --git a/src/lib/export.ts b/src/lib/export.tsindex 17f5901..0d2dc7a 100644--- a/src/lib/export.ts+++ b/src/lib/export.ts@@ -181,7 +181,7 @@ export const AUDIO_CHANNELS = 2;* The mix is one Float32 per channel per sample and it is built BEFORE the* muxer opens — an .mp4's track list is fixed the moment the file is created,* so whether there is sound has to be settled first — and then held until the- * last video frame has been encoded. That is 11.5 MB a minute, so a five+ * last video frame has been encoded. That is 23 MB a minute, so a five* minute cut holds 115 MB across the whole render and an hour holds 1.4 GB,* roughly three times that at the peak of mixing while the decoded sources are* still alive. Nobody should meet that number by running out of memory. */