-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Safari 17.4 is here #6997
Comments
Doesn't work. Tested on iOS 17.4, test files are from https://hpr.dogphilosophy.net/test/. Both Vorbis in Ogg and Vorbis in WebM don't play. |
@nihil-admirari I cannot open that URL because of security protections. Can you provide the test files in a place that's not insecure? Ogg is not supported, so it's expected that Vorbis in Ogg will not work. Vorbis should work in other containers, like WebM. |
We just retested with multiple files, including some from Wikipedia, and confirmed Safari 17.4 on iOS does support the Vorbis codec, for example in a WebM container. The site you linked to above requests the user install the WebM QuickTime Component, something that stopped working over a decade ago when support was dropped for QuickTime.framework. And it's serving a |
Here is a vp8/vorbis file .weba is not a valid extension file |
Ok, Vorbis in webm does work. The site in question uses weba and ogg, which are unfortunately still not supported. Release notes don't specify the container:
which is confusing, especially when compared with the release notes for Safari 17, where container for Opus files was indeed specified:
|
weba is not a thing. That’s an extension the site made up. Had the extension of the file been .webm it would have played. |
Didn't know that it's non-standard. Such files are over the Internet. Chromium supports them: chromium/chromium@c3ce84e. |
Chromium sniff the content and ignore the file extension. As long as ffmpeg can play them, so will chromium. Safari is a tad more strict. |
https://webkit.org/blog/15063/webkit-features-in-safari-17-4/
The text was updated successfully, but these errors were encountered: