James df80182452 fix(engine): add bt709 color space + range conversion to H.264/H.265 encoding ...

Chrome captures frames in full-range sRGB, which maps to BT.709. Without
explicit color metadata, players guess the wrong color space and range,
causing color shifts and crushed dark values across devices.

Changes:
- Embed bt709 color info in H.264/H.265 VUI via x264-params/x265-params
  (colorprim, transfer, colormatrix) and FFmpeg metadata flags
- Add scale filter (in_range=pc:out_range=tv) to convert full-range
  Chrome screenshots to limited/TV range expected by H.264 decoders
- Chain range conversion with VAAPI's existing hwupload filter
- Add -video_track_timescale 90000 for consistent A/V timing
- Skip color metadata and range conversion for VP9/ProRes
- 8 new regression tests for color space, range filter, VAAPI chain,
  GPU skip, VP9 skip, and timescale

Verified via ffprobe: color_space=bt709, color_transfer=bt709,
color_primaries=bt709, color_range=tv, time_base=1/90000.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-07 16:58:28 +00:00

..

cli

fix(cli): fix preview opening wrong project in dev mode (#221)

2026-04-07 17:40:24 +02:00

core

fix(core): load head styles/scripts from non-template sub-compositions (#219)

2026-04-07 17:17:25 +02:00

engine

fix(engine): add bt709 color space + range conversion to H.264/H.265 encoding

2026-04-07 16:58:28 +00:00

player

feat: allow clip animation + ship <hyperframes-player> web component (#209)

2026-04-06 19:59:39 +02:00

producer

fix(producer): extract head assets from non-template sub-comps + fix postcss ESM (#220)

2026-04-07 17:37:26 +02:00

studio

chore: release v0.2.2

2026-04-03 04:36:19 +00:00