WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
293310
Incorrect media time for Opus audio in an Ogg container.
https://bugs.webkit.org/show_bug.cgi?id=293310
Summary
Incorrect media time for Opus audio in an Ogg container.
Chris Adams
Reported
2025-05-20 12:31:05 PDT
We recently ran into a problem with some Opus files which play correctly in every browser other than Safari. These are Ogg containers with 48kHz Opus streams - here's ffprobe's output: [ogg @ 0x154e05bd0] 658 bytes of comment header remain Input #0, ogg, from 'DB100298.opus': Duration: 07:32:36.61, start: 0.000000, bitrate: 24 kb/s Stream #0:0: Audio: opus, 48000 Hz, mono, fltp If I use that file as the source for an <audio> tag, in Safari the total time will display as 7:58:26 in Safari and 7:32:36 in Chrome, Edge, Firefox, and tools like FFmpeg or VLC. If I copy the Opus stream from the original Ogg container to a WebM container, Safari will load it with the correct time: ffmpeg -i DB100298.opus -codec copy DB100298.webm If I convert the Opus stream to a Vorbis stream in an Ogg container, it also has the correct time: ffmpeg -i DB100298.opus -f ogg DB100298-vorbis.opus This was reported on multiple systems running the latest Sequoia and Safari 18.5 (20621.2.5.11.8)
Attachments
Add attachment
proposed patch, testcase, etc.
Chris Adams
Comment 1
2025-05-22 13:34:27 PDT
I reported this at
https://feedbackassistant.apple.com/feedback/17678667
because it affects QuickTime Player as well as Safari, presumably being located in a system framework like Core Audio.
Ahmad Saleem
Comment 2
2025-05-22 14:25:06 PDT
rdar://151875752
Chris Adams
Comment 3
2025-12-12 11:12:05 PST
I updated the version tag to reflect that the behaviour is unchanged in Safari 26.1.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug