Clarifications of encoder behavior #362

aboba opened this Issue Jan 20, 2016 · 2 comments


None yet

2 participants

aboba commented Jan 20, 2016

In WebRTC 1.0, there are have been some questions about encoder behavior:

@aboba aboba added PR exists and removed to-do-next-draft labels Jan 21, 2016
@aboba aboba removed the PR exists label Mar 21, 2016
@robin-raymond robin-raymond added 1.2 and removed 1.1 labels Jul 13, 2016
aboba commented Jul 21, 2016

Peter: Encoder has freedom to adjust to conditions. No need to add error support in the sender.

@aboba aboba added 1.1 and removed 1.2 labels Jul 21, 2016
@aboba aboba self-assigned this Jul 21, 2016
@aboba aboba was unassigned by dontcallmedom Aug 23, 2016
@aboba aboba added the PR exists label Sep 9, 2016
@aboba aboba added a commit that referenced this issue Sep 9, 2016
@aboba aboba Encoder clarifications
Fix for Issue #362


@aboba aboba closed this Sep 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment