You can/should specify details about all codecs used, including video codec and if audio is involved, the audio codecs as well.įor your example, the shortest version would be this: Īlso see: Demo on CodePen and article Update Browsers would have to download parts of the files in order to figure out which of the files are compatible, usually in order of the source tags. So far you're only telling the browser that a MP4 container is used for both the HEVC and the H.264 source. Once you are sure the HEVC video is compatible with Safari, give the browser a hint about the codecs by using the type property in the source tags. If Safari plays it, continue to the next step, otherwise fix the video file. Test this by removing all sources from the video tag except the one pointing to your HEVC video.

It would be useful if people could test the codepen demo and note in comments what codec play and Mac hardware info.įirst make sure your HEVC video is encoded correctly so it can be played back by Safari. How it manages to do this without codec hint or apparent mime-type sniffing is unclear. The discussion below suggests that Safari could, despite Apple's own release notes, be deciding to use an AVC source based on hardware considerations. Is there any way to solve this without using feature detection to manipulate the src element?įiled with Apple as a Safari bug #37821806 Setting HEVC as the default source for the video element works for Safari but causes problems for every other browser. I've tried annotating the source with codec information but this doesn't help. However, Safari doesn't play nicely and will ignore the HEVC film if the H264 is present. Ideally a browser should read the sources and takt the first file that it thinks it can read and this should allow Firefox and Chromium to show the VP9 film, Safari the HEVC and Internet Explorer the H264. I'm currently investigating the feasibility of adding HEVC support to videos but am hitting a problem with Safari.

Hvc1 player for mac