Bug 201137 - [iOS] MediaRecorder video capturing results incorrect video orientation
Summary: [iOS] MediaRecorder video capturing results incorrect video orientation
Status: RESOLVED DUPLICATE of bug 198912
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebRTC (show other bugs)
Version: Safari 12
Hardware: iPhone / iPad iOS 12
: P2 Blocker
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-26 05:38 PDT by borisstodic
Modified: 2019-08-27 01:41 PDT (History)
1 user (show)

See Also:


Attachments
source code + encoded video sample (1.86 MB, application/zip)
2019-08-26 05:38 PDT, borisstodic
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description borisstodic 2019-08-26 05:38:38 PDT
Created attachment 377239 [details]
source code + encoded video sample

I am using MediaRecorder API on safari to capture video('video/webm;codecs=H264'). There is an issue with orientation of captured video, it has been rotated by 90 degrees counterclockwise and squashed which makes video unusable. I attached source code which demonstrates video capturing via MediaRecorder, aswell as sample of video recorded. Steps to reproduce bug:

1. Run attached demo in safari ios

2. Hit "start camera" button to initialize camera (navigator.mediaDevices.getUserMedia(constraints))

3. Hit "start recording" button to init video recording (new MediaRecorder(window.stream, options))

4. Hit "stop recording" button to stop video recording

5. Hit "download" to get captured video. 

Note: Safari is not able to playback webm encoded videos so you will have to run video in other browser or application...

Similar issue has already been reported: https://bugs.webkit.org/show_bug.cgi?id=198912
I don't see that any work has been done on this issue yet. I would really appreciate if you can take a look at the issue.


Thank you very much,

Boris
Comment 1 youenn fablet 2019-08-27 01:41:39 PDT
Thanks for the report and the sample.
I'll mark this issue as a duplicate of bug 198912.

*** This bug has been marked as a duplicate of bug 198912 ***