Opened 8 days ago

Closed 8 days ago

#1381 closed request (pending)

Video aspect ratio problem

Reported by: bemasc@… Owned by: alex@…
Priority: tbd Milestone: ietf-108
Component: meetecho-streaming Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

My camera is 16:9, and I am showing up horizontally squished to 4:3.

smime.p7s

Attachments (2)

smime.p7s (3.8 KB) - added by bemasc@… 8 days ago.
Added by email2trac
smime-1.p7s (3.8 KB) - added by bemasc@… 8 days ago.
Added by email2trac

Download all attachments as: .zip

Change history (7)

Changed 8 days ago by bemasc@…

Attachment: smime.p7s added

Added by email2trac

comment:1 Changed 8 days ago by Rick Alfvin

Owner: changed from < default > to alex@…
Status: newassigned

comment:2 Changed 8 days ago by Rick Alfvin

Component: incomingmeetecho-streaming

comment:3 Changed 8 days ago by alex@…

Resolution: worksforme
Status: assignedclosed

We force 4:3 aspect ration as not all browsers support 16:9 capturing. For instance FireFox? does not support it. 4:3 should be supported by all WebRTC-enabled browsers.

comment:4 in reply to:  5 Changed 8 days ago by bemasc@…

Resolution: worksforme
Status: closedreopened
According to chrome:webrtc-internals, Meetecho is setting the video
constraints to {aspectRatio: {ideal: 1.33333}, ...}.  "ideal" means that
the browser is free to override this value during mode selection.  As a
result my hardware returns a 16x9 video feed.  This is within-spec.

Meetecho is squishing this feed into a 4x3 display area.  This is
unfortunate, and could be fixed by cropping the edges of the frame, e.g.
during transcoding or by adjusting the CSS.

smime-1.p7s

Changed 8 days ago by bemasc@…

Attachment: smime-1.p7s added

Added by email2trac

comment:5 Changed 8 days ago by alex@…

Resolution: pending
Status: reopenedclosed

We're aware of other constraints to request a more specific resolution, but in our experience this has been more likely to result in a getUserMedia request failing, e.g., because that exact resolution is not supported by the webcam, and/or the browser is unwilling or uncapable of scaling/cropping to the desired outcome. As such, we went for ideal that gives the highest rate of success. We agree that some cropping on the UI side might be the easiest way to address this (we don't do any transcoding instead), rather than stretching as we do now: at the same time, though, not sure if we'll be able to do this within the week, as this may require a few too many changes in the way the UI currently works.

Note: See TracTickets for help on using tickets.