-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The myth of HTMLVideoElement.readyState
and HTMLVideoElement.requestVideoFrameCallback
#6577
Labels
Comments
@hujiajie Please file a chromium issue to see whether it's a chrome bug about the |
hujiajie
added a commit
to hujiajie/tfjs
that referenced
this issue
Jul 15, 2022
`HTMLVideoElement.requestVideoFrameCallback()` provides a realiable way to guarantee the readiness of a video frame, whereas the browser may not update the ready state until a few frames later. In such cases, false alarms will be raised by the validation in `fromPixels()`. For where rVFC is unavailable, fallback to the old path based on the `loadeddata` event. This at least seems better than waiting on nothing. Fixes tensorflow#6577
hujiajie
added a commit
to hujiajie/tfjs
that referenced
this issue
Aug 1, 2022
`HTMLVideoElement.requestVideoFrameCallback()` provides a realiable way to guarantee the readiness of a video frame, whereas the browser may not update the ready state until a few frames later. In such cases, false alarms will be raised by the validation in `fromPixels()`. Fixes tensorflow#6577
gyagp
pushed a commit
that referenced
this issue
Aug 5, 2022
`HTMLVideoElement.requestVideoFrameCallback()` provides a realiable way to guarantee the readiness of a video frame, whereas the browser may not update the ready state until a few frames later. In such cases, false alarms will be raised by the validation in `fromPixels()`. Fixes #6577 Co-authored-by: Yang Gu <yang.gu@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm seeing this error when running latest TFJS unit tests with the WebGPU backend:
OS: Windows 10 (19044.1766)
GPU: Intel UHD 620 (driver version: 30.0.101.1994)
Browser: Chrome Canary (version: 105.0.5148.0)
What I don't understand is the readiness of the frame data has already been gated by
HTMLVideoElement.requestVideoFrameCallback
:tfjs/tfjs-backend-webgpu/src/backend_webgpu_test.ts
Line 243 in ca9799d
How can the ready state be 1 (
HAVE_METADATA
) instead of 2 (HAVE_CURRENT_DATA
) or higher here:tfjs/tfjs-core/src/ops/browser.ts
Lines 112 to 118 in ca9799d
Am I misunderstanding anything? Thanks
cc @gyagp @qjia7 @shaoboyan
The text was updated successfully, but these errors were encountered: