More media mojification to allow running the DefaultRendererFactory in a Utility Process |
||
Issue descriptionDesign doc: https://docs.google.com/document/d/19n22cLElIoBEBepXA4TslHfVWRbzf37eThzppmXgTac 1- Allow to use {FFmpeg/Vpx}VideoDecoder from a UtilityProcess: https://codereview.chromium.org/2643733002/ 2- Allow to use the DefaultRendererFactory from a Utility Process: https://codereview.chromium.org/2643713003/ https://codereview.chromium.org/2640003002/ I have not added any gn args, mojo_media_services = [ "video_decoder" ] or mojo_media_services = [ "renderer" ] and mojo_media_host = "utility" already existed. But it was still using the TestMojoMediaClient and it was mostly empty. So I implemented a dedicated UtilityMojoMediaClient to support the 2 above services. A lot of bits were in place already but in short it was missing to use mojo video frames in the video frame pool and to mojify the AudioRendererSink / VideoRendererSink.
,
Feb 17 2017
,
Sep 13 2017
I moved the CL to gerrit (I also rebased, addressed some remarks and fixed a couple of bugs):
1- Allow to use {FFmpeg/Vpx}VideoDecoder from a UtilityProcess:
https://chromium-review.googlesource.com/c/chromium/src/+/664797
2- Allow to use the DefaultRendererFactory from a Utility Process:
https://chromium-review.googlesource.com/c/chromium/src/+/664878
https://chromium-review.googlesource.com/c/chromium/src/+/664879
The following 3 and 4 are useful for 1 and 2 but for other cases too:
3- MojoDecoderFactory: can now create more than one video decoder
https://chromium-review.googlesource.com/c/chromium/src/+/664676
4- VpxVideoDecoder: can use mojo for MemoryPool::VP9FrameBuffer
https://chromium-review.googlesource.com/c/chromium/src/+/664877
|
||
►
Sign in to add a comment |
||
Comment 1 by julien.isorce@chromium.org
, Jan 18 2017