search

WICG / video-rvfc

video.requestVideoFrameCallback() incubation
https://wicg.github.io/video-rvfc/
Other
54 stars 19 forks source link

captureTime: present for webrtc use-cases #74

Closed fippo closed 3 years ago

fippo commented 3 years ago

https://wicg.github.io/video-rvfc/#dom-videoframemetadata-capturetime says it should be present for webrtc use cases. Locally, can that work even? The video element doesn't know a track is going to be sent over a peerconnection.

fippo commented 3 years ago

It can work for getUserMedia applications which might be what is intended? Happy to do a PR!

tguilbert-google commented 3 years ago

I will defer to @drkron to answer this question.

Should the spec be relaxed, or is there an implementation issue (and the capture time should always be present?)

fippo commented 3 years ago

i think it is just a wordsmithing issue on the local end. On the remote end it might be an implementation issue but lets discuss that in the samples pr and maybe a chrome bug

drkron commented 3 years ago

I think that the requirement statement is correct for remote sources, but it could be improved for local sources. Phrasing in terms of getUserMedia may be a way to capture that.

Adding @handellm to this thread since he made a change to captureTime recently.