Closed Bug 1239956 Opened 10 years ago Closed 9 years ago

Reduce resolution of captured video stream to align with the maximum resolution the other peer can potentially render.

Categories

(Hello (Loop) :: Client, defect, P2)

Product:
Hello (Loop)
Component:
Client
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: RT, Unassigned)

Details

(Whiteboard: [akita-beta])

User Story

As a Hello user in limited bandwidth or limited hardware conditions, I want Hello to perform well went in real-time sessions.

Acceptance criteria:
- Set capture video resolution for webcam on owner and guest sides to 320x240
- Set max height and width of captured tab for tab sharing to 1280

In an effort to try to optimize Hello performance and improve Hello's experience in limited bandwidth conditions and/or limited hardware conditions we should investigate the following:
1 What is the maximum resolution a link clicker can see the link generator's camera at
2 Can we lower the resolution of the captured link generator video stream to 1
3 What is the maximum resolution a link generator can see the link clicker's camera at
4 Can we lower the resolution of the captured link clicker video stream to 3
No description provided.
User Story: (updated)
Summary: Reduce resolution of captured video stream to align with the maximum resolution a link clicker can potentially render. → Reduce resolution of captured video stream to align with the maximum resolution the other peer can potentially render.
Rank: 21
Priority: -- → P2
The RTP stack in the browser manages adapting video resolutions and frame rates to network conditions, but there are constraints you can put on resolution and frame rate for P2P if you want. My advice would be to set resolution based on the size that you are going to display the video on the subscriber side. The lowest we support is 320x240 and that's probably enough for Hello. You could also experiment with a lower frame rate, but I think it's usually better to let the webrtc engine handle it because setting it lower than the default is noticeable. https://tokbox.com/developer/sdks/js/reference/OT.html#initPublisher
You can also control the max resolution and framerate of the screen share stream but be careful there since it requires a pretty good resolution to render a screen well. Reducing the frame rate could help if the stuff you are sharing isn't very animated.
Rank: 21 → 26
Whiteboard: [triage]
We need a better confirmation that this will improve the experience before we implement it in the product. (Prototyping or experimenting on the effect outside of Hello would be useful at any time.)
Rank: 26 → 31
Priority: P2 → P3
Whiteboard: [triage]
Ian, we reviewed the quality reports extracted from the NPS forms (manual user feedback) yesterday and it confirmed a drop in perceived quality since FF45 launched. Could we look into this again since Akita's UX renders video streams of cameras in a fairly small window without pop-out option allowing full screen. Is this actionable now (i.e can it become a P1) or do we need further investigations to understand if limiting resolution/framerate at the sending end would improve perceived quality?
Flags: needinfo?(ianb)
Rank: 31 → 5
Priority: P3 → P1
Rank: 5 → 25
Flags: needinfo?(ianb)
Priority: P1 → P2
Whiteboard: [akita]
Updating user story with further details based on Mike's comments.
User Story: (updated)
Whiteboard: [akita] → [akita][triage]
Whiteboard: [akita][triage] → [akita-beta]
Support for Hello/Loop has been discontinued. https://support.mozilla.org/kb/hello-status Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.