Closed
Bug 1005637
Opened 11 years ago
Closed 11 years ago
Configure OMX H264 encoder correctly to start
Categories
(Core :: WebRTC: Audio/Video, defect, P2)
Tracking
()
People
(Reporter: jesup, Assigned: jesup)
References
Details
(Whiteboard: [s=fx32, p=.25])
Attachments
(1 file)
5.85 KB,
patch
|
roc
:
review+
|
Details | Diff | Splinter Review |
The H.264 HW OMX encoder is picking up a bunch of default settings made in OMXCodecSupport.cpp which appear to be intended for a different usecase (2Mbps, etc).
I've implemented an alternative API to configure() that allows passing an AMessage in with the settings we want.
There's still an open question on exactly what those settings are.
Assignee | ||
Comment 1•11 years ago
|
||
Comment 2•11 years ago
|
||
This falls after the SDP and packetization work Randell's doing. working on unblocking through partnering.
Priority: -- → P2
Whiteboard: [s=fx32, p=.25]
Target Milestone: --- → mozilla32
Assignee | ||
Updated•11 years ago
|
Attachment #8417032 -
Flags: review?(roc)
Attachment #8417032 -
Flags: review?(roc) → review+
Assignee | ||
Comment 3•11 years ago
|
||
Assignee | ||
Comment 4•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/76a7d720a9a3
Accidentally included a change in SetBitrate() ro the parameter name (to the KK version) when I qref'd to add r=roc; this backs that out.
Comment 5•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/120d830b89e2
https://hg.mozilla.org/mozilla-central/rev/76a7d720a9a3
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
feature-b2g: --- → 2.0
You need to log in
before you can comment on or make changes to this bug.
Description
•