1130366 - [Loop] Video resolution and FrameRate adjustment in desktop's Loop when streaming to a Firefox OS device

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Loop, defect)

Description

[Oscar Patiño González]

Currently, Hello on desktop streams are 640x480@30fps (at least with my laptop, I guess it depends on camera resolution). This stream is perfectly supported by HW decoder on Firefox OS mobile devices, but the CPU usage significantly increases with this resolution. I guess that this happens due to uncompressed frames, at that rate and resolution, moved from HW decoder to Video memory are taking CPU time.

CPU usage increases around 12% when streaming desktop vs Flame compared with Flame vs FireE.

We should establish some kind of device identification between peers in order to adjust on both sides resolution/framerate and not to hog the CPU.

Comment 1

[Oscar Patiño González]

We could use imageattr, RFC6236, in our SDPs. It is already implemented in mozilla central's latest.
The new line could be something like
a=imageattr:97 send [x=320,y=240] recv[x=320,y=240]   (for a flame)
a=imageattr:97 send [x=640,y=480,sar=1.0,q=0.6][x=320,y=240] recv [x=320,y=240]  (for desktop)

Comment 2

[Oscar Patiño González]

(In reply to Oscar Patiño González from comment #1)
> We could use imageattr, RFC6236, in our SDPs. It is already implemented in
> mozilla central's latest.
> The new line could be something like
> a=imageattr:97 send [x=320,y=240] recv[x=320,y=240]   (for a flame)
> a=imageattr:97 send [x=640,y=480,sar=1.0,q=0.6][x=320,y=240] recv
> [x=320,y=240]  (for desktop)

Sorry, I made a mistake writing this. I don't know why I wrote 'it is already implemented' but I wanted to say 'it is not implemented' yet...

Comment 3

[Maria Angeles Oteo (:oteo)]

[Tracking Requested - why for this release]:

Comment 4

[BMO Automation]

Firefox OS is not being worked on