Software decoding media capabilities won't be displayed correctly on Windows if users haven't started playing any media
Categories
(Core :: Audio/Video: Playback, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox121 | --- | affected |
People
(Reporter: alice0775, Unassigned)
References
(Blocks 2 open bugs)
Details
Attachments
(3 files)
STR:
- Open about:support
Actual results:
Most Software Decoding media capabilities show as unsupported.
Expected results:
Software Decoding media capabilities should show as supported other than HVEC.
Reporter | ||
Comment 1•1 year ago
|
||
Reporter | ||
Comment 2•1 year ago
|
||
Reporter | ||
Comment 3•1 year ago
|
||
Reporter | ||
Comment 4•1 year ago
|
||
Interestingly,
Once the video (https://lachy.id.au/dev/markup/examples/video/bus.ogg) is played back, the issue is resolved and the media capabilities are displayed correctly. However, when the browser is restarted, the problem occurs again.
Comment 5•1 year ago
|
||
That is because there would only be support information from GPU process, if Firefox just starts without playing any media yet. But once users starts playing media and go back to about:support
again, the support information would be displayed correctly.
Ideally, in this case, either we should show this error message to users, or find out a way to start RDD/Utility audio process immediately to get the correct information.
(NI :az for letting this appear on her radar as well)
The Codec support information unavailable. Try again after playing back a media file
message should show when a user hasn't played any media files yet. I tested several times on my machine to check and the message comes up on my end each time, but if it's not consistent then that's an issue. That said, it'd be better if we fired up the processes required to have full information out-of-the-box. There was some discussion on this a while back, with the main concerns being related to potential performance impacts and the right method of testing / mocking playback to ensure that playback works in practice. I'm not sure what the best solution here is, but I'd be happy to discuss further and come up with improvements.
Description
•