Re: [mediacapture-record] Should stop(), pause(), resume() change state synchronously?

I believe we can run into the issue alluded to above:

> Note that for media elements, the true async nature can still be observed, e.g. calling pause() makes the element look paused, but currentTime will change at least once more since the playback doesn't happen on the main thread. Are there situations like that here?

Data is delivered to our encoders on a different thread than the one we control the recorder on. As it stands I think we could end up with a race between delivery and control functions.

-- 
GitHub Notification of comment by SingingTree
Please view or discuss this issue at https://github.com/w3c/mediacapture-record/issues/123#issuecomment-325529434 using your GitHub account

Received on Tuesday, 29 August 2017 01:39:12 UTC