Open
Bug 1239098
Opened 9 years ago
Updated 2 years ago
Ensure that we specify the video frame rate correctly when creating DXVA video decoders
Categories
(Core :: Audio/Video: Playback, defect, P3)
Core
Audio/Video: Playback
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox46 | --- | affected |
People
(Reporter: mattwoodrow, Unassigned)
Details
AMD is planning on making sure the InputSampleFreq field of DXVA2_VideoDesc is read and included into the decision whether to allow the decoder to be created.
We need to ensure that we're specifying this correctly so that we don't get decoders created that would require throughput that isn't available.
We'll also need to detect the driver version in which this functionality is available, and skip our hardcoded list of blacklisted device ids.
Updated•9 years ago
|
Priority: -- → P2
Updated•9 years ago
|
Component: Audio/Video → Audio/Video: Playback
Mass change P2 -> P3
Priority: P2 → P3
Comment 2•8 years ago
|
||
There's a problem with that approach. This assumes that the framerate is constant. And from a few files I'm working on right now, this isn't true.
In particular videos coming from live streams.
I guess the framerate will be low enough that it doesn't really matter anyway.
Comment 3•3 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: matt.woodrow → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•