Open
Bug 1194652
Opened 9 years ago
Updated 2 years ago
Make MediaFormatReader capable of returning only demuxed raw data for EME HW CDM Rendering
Categories
(Core :: Audio/Video: Playback, defect, P3)
Core
Audio/Video: Playback
Tracking
()
NEW
FxOS-S9 (16Oct)
People
(Reporter: kikuo, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [ft:conndevices][partner-blocker][POVB])
Considering media playback HW Rendering such as decrypt/decode/render+av-sync by 3rd HW component, we need to make MediaFormatReader capable of requesting encrypted-and-demuxed MediaRawData and returning these data to MDSM.
Per Bug 1146795 Comment 24, we need to consider several conditions as follows,
Under the premise that using EME and HW CDM rendering,
1. Either Video / Audio is encrypted
2. Both Video / Audio are encrypted
==> Both cases, we could push encrypted / encoded data in EncryptedMediaDataSink / RawMediaDataSink, and wait for the requesting from HW consumers.
3. Encryption method changes on the fly.
==> There should be a way to notify this situation happening, and update information into MDSM's MediaInfo, so that different types of medias sink could be created/destroyed dynamically.
Updated•9 years ago
|
Target Milestone: --- → FxOS-S9 (16Oct)
Updated•9 years ago
|
Priority: -- → P1
Updated•9 years ago
|
Updated•9 years ago
|
Whiteboard: [ft:conndevices][partner-blocker] → [ft:conndevices][partner-blocker][POVB]
Reporter | ||
Updated•9 years ago
|
Assignee: nobody → kikuo
Reporter | ||
Comment 4•9 years ago
|
||
Hmm...kinda,
I think the code actually has been done in Bug 1194606, but there is still an open issue to be discussed about Bug 1194606 is that ... we need to come out a policy(or mechanism) in MDSM to decide when to ask MediaFormatReader returning demuxed-only data for any external decoding+rendering cases.
The discussion is in Bug 1204799, but there's no conclusion yet, and I suppose it's not in priority now.
Flags: needinfo?(kikuo)
Updated•9 years ago
|
Priority: P1 → P2
Mass change P2 -> P3
Priority: P2 → P3
Reporter | ||
Updated•7 years ago
|
Assignee: kilik.kuo → 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
•