866224 - Feed back to application and/or source MediaStream the resolution actually needed/used by the encoder

Status: NEW

(Core :: WebRTC, defect, P5)

Description

[Randell Jesup [:jesup] (needinfo me)]

Per bug 844177 comment 7 through comment 9, this bug is about reworking how the current CodecConfig setup works in AudioSessionConduit and VideoSessionConduit.

Quote:
I do want to avoid anything possibly heavyweight where it's not needed (and the current ConfigureSendMediaCodec() really isn't designed for what we're talking about, as you mention).  What we really need to do is to rearchitect it to interact with the bandwidth controls to dynamically adjust the encoding resolution, to deal with source resolution changes, and to feed back "upstream" to gUM that we're encoding at X by Y, since in many cases the camera will scale for us (or at least scale to something close, we the amount of data copying we do is greatly reduced).

*That's* the redesign we need to do.

Comment 1

[Randell Jesup [:jesup] (needinfo me)]

This is done, except for the "feeding it back upstream to gUM" part.  And arguably that should be intermediated by the App in case it was using the stream for something else as well.

Dynamic resolutions are now being done via the loadadaptation code, and dynamic bandwidth is landed.  Repurposing this bug

Comment 2

[Bulk Bug Changes for mreavy's org]

Mass change P4->P5 to align with new Mozilla triage process.