Skip to content
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

MediaRecorder : frame loss on mobile devices #201

Closed
sr1dh4r opened this issue Jul 12, 2020 · 5 comments
Closed

MediaRecorder : frame loss on mobile devices #201

sr1dh4r opened this issue Jul 12, 2020 · 5 comments

Comments

@sr1dh4r
Copy link

sr1dh4r commented Jul 12, 2020

Browser name including version (e.g. Chrome 64.0.3282.119)

Chrome 83.0.4103.106

Description
Frames are lost in the recording.

Steps to reproduce
Testing:

Open https://webrtc.github.io/samples/src/content/getusermedia/record/ link in mobile chrome browser on android.

Expected results
Recording should be available without any frame drop.

Actual results
Recording has a lot of frame loss.

Related issues
#177
webrtc/samples#1331 (Opening it here since it seems more relevant)

@guest271314
Copy link

How is frame loss determined?

Have you tried using start(0) with requetData() and comparing result with start() without timeSlice?

Have you tested with h264/avc1 codec?

@sr1dh4r
Copy link
Author

sr1dh4r commented Jul 20, 2020

How is frame loss determined?
Visually, please try the linked shared on a mobile device.

Have you tried using start(0) with requetData() and comparing result with start() without timeSlice?
Yes, I see no difference.

Have you tested with h264/avc1 codec?
I have tested against vp8, vp9 webm codecs as described in #177 and I don't expect it to be any different.

@guest271314
Copy link

What are the steps to reproduce?

"a mobile device" is a broad category. What specific device?

How did you verify frame loss other than visually?

What is the expected result?

@sr1dh4r
Copy link
Author

sr1dh4r commented Jul 21, 2020

What are the steps to reproduce?

"a mobile device" is a broad category. What specific device?

How did you verify frame loss other than visually?

What is the expected result?

#201 (comment)

@dontcallmedom
Copy link
Member

unless there are clear reasons why the design of the spec makes it not usable on mobile devices (which this issue doesn't cover), this sounds like an implementation issue. Closing until further motivation is given

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants