op: Test camera capture using copyExternalImageToTexture #4364
Comments
kainino0x
changed the title
8 tasks
kainino0x
added a commit
that referenced
this issue
Apr 23, 2025
- Don't use fallback paths in camera capture; instead, have the test pick the exact path it's using, and parameterize over it. Test two paths: VideoFrame from MediaStreamTrackProcessor, and the old-fashioned HTMLVideoElement. - Work around an issue where Chrome (at least on Mac) shows blank frames for a while after initializing the camera. - I happened to notice that requesting different width/height from the camera is broken in Chrome in several ways, so added cases for that. - Added a TODO for copyExternalImageToTexture from camera These tests only worked in Chrome, and even then they were buggy (usually running the test on a blank first frame). Now, the HTMLVideoElement tests work in Safari. Test failures are as follows, on an M1 Mac: - Chrome: https://crbug.com/411656657 - HTMLVideoElement passes some cases, but fails when a requested size is passed to getUserMedia(). - VideoFrame fails due to incorrect color management (regardless of dstColorSpace). - Safari: - HTMLVideoElement fails due to incorrect color management (regardless of dstColorSpace). - VideoFrame is skipped. - Firefox: doesn't yet implement importExternalTexture. Issue: fixes #4363, cc #4364
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we have camera capture tests for
importExternalTexturebut notcopyExternalImageToTexture.The text was updated successfully, but these errors were encountered: