Fast-cut single frames "burn"/flash on playback and export — Apple Silicon only (M-series), not on Intel Mac, Windows, or Linux
Issue:
I have a video trailer with a section containing very fast cuts (single-frame duration cuts). This portion appears "burnt"/flashed/over-bright only during playback and only on Apple Silicon (M-series) Macs. The same single frame, when paused/held, displays correctly with no burn.
Where it happens:
- M-series MacBook Pro (built-in display)
- Mac Studio (M-series) with external display
- Confirmed in DaVinci Resolve playback, in the exported file played via QuickTime, and even via OneDrive's web/desktop viewer
Where it does NOT happen:
- Same exported file on an Intel iMac — looks correct
- Same file on Windows — looks correct
- Same file on Linux — looks correct
- Same file viewed on mobile (via OneDrive) — looks correct
What I've ruled out:
- Not an export/encoding issue — file plays back correctly on every non-Apple-Silicon platform
- Not incorrect HDR metadata — confirmed via ffprobe that color_primaries/color_transfer/color_space are all standard Rec.709 (SDR), not HDR/PQ/2020
- Not a single-app bug — happens consistently across DaVinci Resolve, QuickTime, and OneDrive on the same M-series hardware
- Not a mini-LED backlight/local-dimming artifact — happens on Mac Studio + external display too, which has no built-in backlight zones, so it's not panel-specific
What this points to:
Since the artifact is consistent across different playback apps but only on Apple Silicon (both built-in and external displays), it looks like something in macOS's Apple Silicon display/EDR compositing pipeline is momentarily misreading or over-boosting a single fast-cut frame — possibly related to per-frame tone-mapping/EDR handling that Intel Macs don't perform the same way.
Question:
Has anyone else run into single-frame brightness "burn"/flash artifacts specifically on M-series Macs during fast-cut video playback? Is there a known display/EDR setting (Reference Mode, True Tone, automatic brightness, etc.) that affects this, or is this a known Apple Silicon media pipeline bug?
MacBook Pro 14″, macOS 26.6