- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 May 2020 16:14:37 +0000
- To: public-webrtc-logs@w3.org
I see, so it might make sense for audio if codecs use some prediction. Maybe the promise should not reject then? An alternative solution is for the e2e JS transform module to state that it needs a key frame as part of the additional frame metadata given to the packetizer for each processed frame. That might be also useful for a non JS e2e module for which the key changes might not be visible to the script. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/37#issuecomment-628738017 using your GitHub account
Received on Thursday, 14 May 2020 16:14:39 UTC