I think that might be because Safari uses the HEVC version of the video. I'm also seeing 25% usage on an M1 Max MacBook, which is more than I expected.
Firefox and Chrome don't have noticeable CPU usage. They only support the H264 encoded video.
I might have to reencode the video and optimize for hardware decoding. Default ffmpeg options were not enough apparently.
Safari is the only browser that can activate the HDR subsystem on these Display P3 screens, and by doing that it taxes the GPU more when playing back video.
I think that might be because Safari uses the HEVC version of the video. I'm also seeing 25% usage on an M1 Max MacBook, which is more than I expected.
Firefox and Chrome don't have noticeable CPU usage. They only support the H264 encoded video.
I might have to reencode the video and optimize for hardware decoding. Default ffmpeg options were not enough apparently.
EDIT: it's actually because of the HDR section from https://lunar.fyi/#xdrSafari is the only browser that can activate the HDR subsystem on these Display P3 screens, and by doing that it taxes the GPU more when playing back video.