Closed
Bug 1022012
Opened 10 years ago
Closed 10 years ago
Finalize initial pref-on API for GMP codecs
Categories
(Core :: Audio/Video, defect)
Core
Audio/Video
Tracking
()
RESOLVED
DUPLICATE
of bug 1020760
People
(Reporter: jesup, Assigned: jesup)
References
(Blocks 2 open bugs)
Details
We need to finalize the API for codecs in the GMP sandbox, which may be shared by EME codecs. For flexibility, in bug 9990704 I used an API similar to OpenMAX's (choice of single unit/NAL, or a set of units in one buffer with 1, 2, 3, or 4 byte size values between them. This is more generic than the 'raw' H.264 encoder format often seen (start codes). And H.264 encoder that generates a bunch of NALUs with start codes between them would replace the start codes with sizes, for example. The other primary option would be a separate array of offsets and sizes into a main buffer, or (maybe) a list of separate buffers (but this might complicate the sandboxing compared to the single-buffer setup, and end up requiring copying more data around.)
Comment 1•10 years ago
|
||
(In reply to Randell Jesup [:jesup] from comment #0) > For flexibility, in bug 9990704 I used an API similar to OpenMAX's (choice > of single unit/NAL, or a set of units in one buffer with 1, 2, 3, or 4 byte > size values between them. This is more generic than the 'raw' H.264 encoder > format often seen (start codes). As I understand it, this is AVCC format. That works for us, provided the NAL size's size is communicated out of band.
Updated•10 years ago
|
Blocks: WebRTC-OpenH264
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → rjesup
Assignee | ||
Comment 2•10 years ago
|
||
All the work for this is happening in bug 1020760
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•