Re: [opensource-dev] Replacement for QuickTime media plugin - a straw man proposal

2016-05-18 Thread Darien Caldwell
Using CEF for media is what I've been saying since CEF support was announced for the viewer. I think it would be a clean solution. The viewer already runs 3 instances of CEF at startup, using one of those for media wouldn't really add any additional load. The viewer is already using something else

Re: [opensource-dev] Replacement for QuickTime media plugin - a straw man proposal

2016-05-18 Thread Callum Prentice (Callum)
Yep, that's a concern - I believe we used QuickTime to play MP3s too so that would be even more wasteful. The answer might be to do this anyway so we enable videos embedded in web content, play video URLs with the LibVLC plugin and come up with a lightweight solution (FMODEx??) for MP3s. On Wed,

Re: [opensource-dev] Replacement for QuickTime media plugin - a straw man proposal

2016-05-18 Thread Cinder Roxley
On May 18, 2016 at 5:40:18 PM, Callum Prentice (Callum) (cal...@lindenlab.com ) wrote: Digesting all the suggestions here - thank you. Intrigued by Nicky's suggestion, I am currently trying to build CEF directly via Chromium - first attempt is without the extra fl

Re: [opensource-dev] Replacement for QuickTime media plugin - a straw man proposal

2016-05-18 Thread Callum Prentice (Callum)
Digesting all the suggestions here - thank you. Intrigued by Nicky's suggestion, I am currently trying to build CEF directly via Chromium - first attempt is without the extra flags (proprietary_codecs=1 ffmpeg_branding=Chrome). Building the branch in use in the viewer failed with a bunch of error

Re: [opensource-dev] Replacement for QuickTime media plugin - a straw man proposal

2016-05-18 Thread Henri Beauchamp
On Wed, 18 May 2016 12:16:27 +0200, Nicky D. wrote: > Point 1, bundling a lot of additional libraries probably also holds true > for libvlc. > One way or the other all those needed plugins need to end on the users PC, > no matter if it is gstreamer or vlc. True... I admit I didn't have a look at

Re: [opensource-dev] Replacement for QuickTime media plugin - a straw man proposal

2016-05-18 Thread Nicky D.
> > > Technical, maybe. As pointed out by Nicky, the main annoyances with > gstreamer are: 1. the amount of additional libraries that would have > to be bundled together with the viewer, and: 2. the runtime symbol > resolution and DSO loading which complicates the plugin code, but > since that plug

Re: [opensource-dev] Replacement for QuickTime media plugin - a straw man proposal

2016-05-18 Thread Henri Beauchamp
On Tue, 17 May 2016 16:32:01 -0700, Callum Prentice (Callum) wrote: > Understood Nicky - thanks for the insight. > > Messages here as well as some digging I've done today suggest that > trying to make GStreamer work on Windows is going to be fraught with > technical and legal issues. Technical,