Open
Bug 1340372
Opened 8 years ago
Updated 2 years ago
Support 3gpp:video-orientation in WebRTC
Categories
(Core :: WebRTC: Networking, defect, P3)
Tracking
()
NEW
People
(Reporter: jesup, Unassigned)
References
Details
+++ This bug was initially created as a clone of Bug #1300665 +++ Split off, since we landed support for abs-send-time and toffset in bug 1300665. This would allow avoiding rotating video in some cases before sending or after receiving. Mostly though not solely for Android/mobile (in theory a rotating monitor on desktop might use it, maybe).
Reporter | ||
Updated•8 years ago
|
Rank: 25
Comment 1•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Comment 2•6 years ago
|
||
I left a comment on bug 984215 but seems like this is the bug to support video-orientation feature. May I ask when this feature will be implemented or is this in the Firefox product roadmap? Our team is developing WebRTC mobile apps, but Firefox does not support video-orientation and display video without rotation. Without this feature, our apps must rotate video frames manually before sending them.
Updated•6 years ago
|
Comment 3•4 years ago
|
||
Just wanted to point out that the missing support of this flag may lead to significant performance issues. While the orientation is correctly negotiated in direct calls (could be an issue with SFUs to even orientate correctly) to be viewed normally, some mobile devices get severe framedrops from having to rotate the video material. So a device that is able to do full HD 30fps streaming when being connected with a Chrome browser might be on 13fps when connected with a Firefox browser. Especially in the wearable market this makes it a significant performance issue rather than a programming inconvenience.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•