fix(studio): stabilize previews and normalize clip audio - #3280
fix(studio): stabilize previews and normalize clip audio#3280miguel-heygen wants to merge 1 commit into
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
7368231 to
bf41590
Compare
bf41590 to
e3fd173
Compare
e3fd173 to
6cb48c0
Compare
6cb48c0 to
33efa91
Compare
Persist agent preview processes safely and support above-unity gain in preview and render. Add a measured LUFS normalizer for matching local authored clips.
33efa91 to
2869bab
Compare
|
Closing this — every piece of it has landed or moved somewhere better, and nothing is dropped. I rebased it onto current Where each piece went:
That last row is the only thing that was genuinely unlanded, and it turned out to matter: raising the ceiling to 12 dB made Merging this as-is would have conflicted with #3306 and #3310 and re-landed an older |
|
Superseded — see the breakdown above. |
What
Fixes the two real issue families reproduced from the reported screenshots and exact saved project:
It also adds
hyperframes normalize-audioso agents can measure two local authored clips with integrated LUFS and safely write the target clip's matcheddata-volume.Reproduction findings
-13.8 LUFSand the second-33.7 LUFS.-15.5 LUFSand the second at-11.8 LUFS; both were authored atdata-volume="1", so equal fader values still did not mean equal perceived loudness.How
+12 dBceiling across Studio, Web Audio, runtime media, the engine mixer, and FFmpeg render.-infinity / -60 dB ... 0 dB ... +12 dBfader with unity at the center.HTMLMediaElement.volumeclamped while applying above-unity gain through Web Audio.normalize-audio --reference <id> --target <id> [--write], which:data-volume;Exact-project correction
The private saved project was updated in place with the first clip as the reference. The second clip's
data-volumechanged from1to0.645654(-3.8 dB). A fresh full render measured both authored segments at-15.5 LUFS. Re-downloading the authoritative saved project and rerunningnormalize-audioreports it matched within the default0.5 LUtolerance.Verification
-15.5 LUFS.Compatibility is preserved: existing
data-volume="1"clips remain at unity, interactive human preview remains foreground by default, and normalization never guesses which clip should define the mix.