[miguel-heygen]

What changed

BROWSER_HOSTILE_CODECS gains mpeg2video (MPEG-2, as in an mp4 from an older camera or encoder) and dnxhd (Avid DNxHD in a mov), both with no representative mime and pre-warm on, as prores and mpeg4 are. A project video in either codec now gets a browser-playable copy instead of "no copy" (browser_safe_codec).

Why

Chrome in Electron refuses both: a card for an ffmpeg -c:v mpeg2video mp4 and a -c:v dnxhd mov ended with <video> error code 4 and no picture, while the same studio server table lists neither, so the copy request was answered 404. In the same run H.264 (4:2:0, 4:4:4 and 4:2:2 10-bit), HEVC, VP9 and AV1 played, and MPEG-4 and ProRes played through their copy.

What I measured

• fails without the fix: packages/studio-server/src/helpers/mediaCodecMap.test.ts, 4 failures with the two table lines removed (the mpeg2video and dnxhd mime and pre-warm cases), 45 pass with them (bun, vitest, format check on a Linux box).
• Browser check: one Chrome inside Electron on macOS, one generated clip per codec.

What I did NOT exercise

• No end-to-end proxy transcode of an mpeg2video or dnxhd file through the server route; the table is what decides eligibility.
• Other codecs (h263, msmpeg4, vc1, wmv, dv) are not added: they could not be put in an mp4 here, or were not tried.

Size

About 4 changed lines in 2 files: a lone table change with its test; nothing open on this table to carry it.

[heygengenesis]

Approve at 66d82ed5.

The change adds two lines to the table, matching the existing mpeg4/mjpeg/prores pattern: no representative mime, and pre-warm on. That's right for codecs that no browser decodes.

Verified at this head:

• npx vitest run src/helpers/mediaCodecMap.test.ts: 45 passed.
• fails without the fix: holds. With main's mediaCodecMap.ts, the 4 new cases fail (mime and pre-warm, for mpeg2video and dnxhd).
• The keys match ffprobe's names. Clips generated with -c:v mpeg2video (mp4) and -c:v dnxhd (mov) probe as mpeg2video and dnxhd.
• This table is the only codec list. Its consumers (checkBrowser, publishProxyBake, the preview route, staticProjectServer) all go through hostileCodecEntry/decideMediaProxyEligibility, so check copies and publish bakes pick both codecs up consistently.

Non-blocking: MPEG-2 from broadcast or older cameras is often interlaced. The proxy transcode doesn't deinterlace, so such a copy may show combing on motion. Worth a follow-up if anyone reports it.

[github-actions]

Edit accuracy: accurate 267 (base branch 267), smooth 90 of those

The gate passes.
Smoothness is reported in the artifact, not gated. A case fails only if it fails 2 of 3 runs.

Quarantined, measured but not gated (8)

• seqplainkeys-none-center-r0-nested-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): pass, passes
• seqplainkeys-none-center-r0-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): fail / pass / pass, passes
• seqplainkeys-none-center-r30-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run
• seqplainkeys-none-pct-r0-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): fail / pass / pass, passes
• seqplainkeys-none-pct-r30-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run
• seqplainkeys-none-px-r0-nested-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): pass, passes
• seqplainkeys-none-px-r30-nested-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run
• seqplainkeys-none-px-r30-root-z100 (fixed by studio: undo/redo on a keyframed plain element sometimes leaves the box 230-400px off (edit-accuracy seqplainkeys-none-*) #6989): not run

Unstable (1)

• seqrepeat-none-center-r0-nested-z100: tracking 0.05, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true / tracking 0.05, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true / tracking 0.05, pressJump 0, drop 0, reload 0, render 0.02, renderKey -, undo true, teleport true