1766637 - [meta] Improve OpenH264 first run experience

Status: NEW

(Core :: Audio/Video: GMP, task)

Comment 1

[Jeff Muizelaar [:jrmuizel]]

Do you recall a reason that we don't try to install openh264 as part of the install process?

Comment 2

[Jim Mathies [:jimm]]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #1)

Do you recall a reason that we don't try to install openh264 as part of the install process?

It's H264 patent related I believe.

Comment 3

[Jeff Muizelaar [:jrmuizel]]

I don't mean distributing as part of the installer, just downloading from cisco during install. That shouldn't be any different patent wise vs. downloading it during first run.

Comment 4

[Jim Mathies [:jimm]]

My guess would be that not installing on demand is a bug, and not forcing the install right on first run is related to avoiding startup perf. issues.

Comment 5

[Andrew]

Just to add some detail:
I think it would be best if there were a UI somewhere that allows for manual triggering of the download+install of openh264 that gives feedback about what's happening -- i.e., whether it's in progress, and whether it succeeded/failed with specific error messages if applicable.

Currently, if OpenH264 fails to download/install, the FF installation is left in a state where it cannot negotiate H264 calls, and there isn't a formal process for the user to know what's wrong or to remedy the situation, and those of us with WebRTC applications don't have a good place to point Firefox users to when they run into this.

A UI like this would go a long way toward helping the situation.