WebRTC stream recordings of inverted cameras are not rotated correctly anymore
Reported by
eggert.c...@googlemail.com,
Feb 8 2018
|
|||||||||
Issue description
Chrome Version : 59.0.3071.90
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari:
Firefox: OK
IE/Edge:
What steps will reproduce the problem?
1. Rotate the mobile device so that the camera is natively inverted
2. Establish a WebRTC connection with said mobile device and a Chrome browser
3. Record the footage using MediaRecorder following example https://developers.google.com/web/updates/2016/01/mediarecorder
What is the expected result?
The recorded video should have the corrected rotation as seen in the stream and on the device.
What happens instead of that?
The recorded video is upside-down and seems to just use the native camera footage.
Please provide any additional information below. Attach a screenshot if
possible.
I'm relatively positive this was not an issue in earlier versions and has been introduced lately.
UserAgentString: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.90 Safari/537.36 Vivaldi/1.91.867.38
,
Feb 8 2018
Forgot to mention: Issue experienced with the latest Chrome (64.0.3282.140) - just reported with another browser. Sorry!
,
Feb 9 2018
,
Feb 9 2018
Sounds like an issue with CVO. Can you give some details about what platform/versions the sending mobile device is on?
,
Feb 9 2018
I tested with: - Sony XPeria Z3 Compact, Android 6.0.1 - Vuzix M300, Android 6.0.1
,
Feb 10 2018
,
Feb 12 2018
,
Feb 14 2018
@eggert.christop: Could you please update Chrome to the latest version #64.0.3282.137 and check if you still face the issue? Thanks!!
,
Feb 15 2018
Tested with 64.0.3282.167 - still the same behavior (Firefox works using the same setup).
,
Feb 15 2018
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 16 2018
sprang, what are the next steps here?
,
Feb 16 2018
Speculatively assigning to magjed@, who has at least touched the cvo code. Could you help triage?
,
Feb 16 2018
If I can help with logs or anything, let me know.
,
Feb 16 2018
,
Mar 5 2018
I tested Verision 66 via Dev Channel and 67 via Canary Channel. For both versions the issue is fixed, my question is, if the fix will be part of Version 65. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by dtapu...@chromium.org
, Feb 8 2018