mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-13 07:40:06 +00:00
docs(media): document automatic proxying for hostile codecs (#2596)
* docs(media): document automatic proxying for hostile codecs Describes the shipped behavior: which input codecs render, that live preview auto-proxies what the browser cannot decode, where the cache lives, and how to turn it off. Carries the skills notes and the hardening design documents. * docs(media): align proxy guidance with runtime
This commit is contained in:
@@ -393,10 +393,11 @@ with `resolve --from <output> --type <type>` so it joins the ledger + global
|
||||
cache.
|
||||
|
||||
HEVC/H.265 sources need no conversion for **render** (FFmpeg pre-decodes all
|
||||
input video); only live preview depends on the browser's codec support. If an
|
||||
HEVC asset previews black, make an H.264 authoring proxy (`ffmpeg -i in.mp4
|
||||
-c:v libx264 -crf 18 proxy.mp4`), register it with `resolve --from`, and keep
|
||||
either file for the final render.
|
||||
input video) or for **preview** (auto-proxy transcodes and caches an H.264
|
||||
copy on first use, disable with `--no-proxy` or `media.autoProxy: false` in
|
||||
hyperframes.json). A manual H.264 proxy via `ffmpeg -i in.mp4 -c:v libx264
|
||||
-crf 18 proxy.mp4`, registered with `resolve --from`, remains available for
|
||||
edge cases (e.g. auto-proxy disabled, or ffmpeg unavailable at preview time).
|
||||
|
||||
## CLI tools used (what to run, and how to enable each)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user