commit | 3cab5f95132953d28f1151bf1dcf98eefb51f904 | [log] [tgz] |
---|---|---|
author | Piotr Bialecki <bialpio@chromium.org> | Thu Apr 04 18:22:15 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 04 18:22:15 2024 |
tree | 89b29672d48d3e1204abd47445b2c20804022c99 | |
parent | 68e6e90671f2ea804313e52e895ebf4d10118520 [diff] |
Establish connections between Browser, Video Capture, and Video Effects End-to-end connection between Video Effects Manager (Browser process), Video Effects Processor (Video Effects Service process), and Video Capture Device Client (Video Capture Service process) should now be established. Major changes / approach: - Introduce the `media::VideoEffectsContext` struct, declared in video_capture_device_client.h. This allows us to iterate on the specific types that are needed by `VideoCaptureDeviceClient` but without incurring churn. Similar approach could be taken in `VideoCaptureDeviceLauncher::LaunchDeviceAsync()` - VideoEffectsManager is replaced with VideoEffectsProcessor in the codepath from VideoCaptureManager to ContentBrowserClient. Change-Id: I12d5fd855df5ea69670bc33c0165f719ca474f23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5384525 Reviewed-by: Ilya Nikolaevskiy <ilnik@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Reviewed-by: Ahmed Fakhry <afakhry@chromium.org> Reviewed-by: Mark Foltz <mfoltz@chromium.org> Reviewed-by: Markus Handell <handellm@google.com> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Piotr Bialecki <bialpio@chromium.org> Cr-Commit-Position: refs/heads/main@{#1282631}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.