Thanks for filing https://github.com/web-platform-tests/wpt/issues/39642, I've asked there for more details on what it would take to test this.
The spec change added two dictionary members to https://w3c.github.io/mediacapture-record/#mediarecorderoptions-section which means that it would at least be possible to add a test for videoKeyFrameIntervalDuration and videoKeyFrameIntervalCount being present. Can you write such a test? Also, I think vendor signals here aren't needed given the reviews on https://github.com/w3c/mediacapture-record/pull/216, but can you file bugs for Gecko and WebKit? On Mon, Apr 24, 2023 at 5:58 PM Henrik Boström <h...@webrtc.org> wrote: > > I was present when the WG discussed this pull request and can confirm that > representatives of Apple, Microsoft, Firefox and Google were present when the > PR was merged. > This API solves problems relating to variable frame rate tracks and being > able to ensure key frames in the streams. Allowing implementing this seems > like a good thing as it plugs an existing hole, so to speak. > > On Friday, April 21, 2023 at 6:48:17 PM UTC+2 Markus Handell wrote: >> >> Contact emails: >> >> hand...@google.com >> >> >> Explainer: >> >> https://github.com/w3c/mediacapture-record/pull/216 >> >> crbug.com/1371449 >> >> >> TAG review: >> >> N/A, small incremental change >> >> >> Summary: >> >> The `MediaRecorder` spec was recently updated to allow users to configure >> video keyframe generation parameters of the encoder. Previously there was no >> such support, and no spec requirements related to keyframe generation >> existed, leading to recorded streams that sometimes contain a single >> keyframe at the beginning of the stream. When played back those streams are >> inefficient to seek in, and it’s impossible to excise segments from them >> without resorting to transcoding. These problems present significant hurdles >> to use the MR API for some applications. >> >> >> Link to “Intent to Prototype” >> >> N/A, small incremental change and going directly for shipping. >> >> >> Risks >> >> Interoperability and Compatibility >> >> This is now in the editors draft >> https://w3c.github.io/mediacapture-record/#mediarecorder-api >> >> Gecko: No signal >> >> WebKit: No signal >> >> Web developers: No signals >> >> >> The pull request adding this feature was reviewed and approved by the WebRTC >> WG containing representatives from Apple, Microsoft, and Mozilla. Feedback >> was addressed in the spec PR. But we have not reached out for comments on >> signals. >> >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, Chrome OS, Android, and Android WebView)? >> >> Yes. >> >> >> Is this feature fully tested by web-platform-tests? >> >> Testability requires muxer parsers which MediaRecorder WPTs are currently >> lacking. https://github.com/web-platform-tests/wpt/issues/39642 has been >> filed to ensure WPTs are added when this is fixed. >> >> >> Tracking bug >> >> crbug.com/1371449 >> >> >> Link to entry on the Chrome Platform Status >> >> https://chromestatus.com/feature/5117302963437568 >> >> > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e104767c-a31e-4553-ad18-1a101e33d0een%40chromium.org. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYdnsTGnKGxATrsMvV02dgKy5v7RREgZ%2Bb-0k0zm5Zq3rQ%40mail.gmail.com.
