commit | 90c7da64fbde20037684762ea832ace910ff1d4f | [log] [tgz] |
---|---|---|
author | Xi Zhang <xizh@google.com> | Thu Nov 16 13:02:19 2023 -0800 |
committer | Xi Zhang <xizh@google.com> | Sun Dec 03 20:57:15 2023 -0800 |
tree | c1554380c97f33b62d1f7fd74e356042227067a7 | |
parent | 504d15fae694cf035000bcb71094f6546e16e6d4 [diff] |
Allow CameraEffect to configure prefered transformation. Previously, the effects pipeline is built based on the assumption that CameraX will make all the decisions and send transformation to the image processing library via the SurfaceProcessor API. During the integration with other image processing libraries, we realized that it's hard for the image processing lib to handle arbitrary transformation. For example, MediaPipe has built in mechanism to handle the texture transformation and the Surface transformation. It's hard to disable those and apply the value provided by the effects pipeline. To fix this, we will allow the implementer of the CameraEffect to configure the desired transformation in this CL. - Update CameraEffect and add a new option called transformation. TRANSFORMATION_ARBITRARY is the current behavior, and TRANSFORMATION_CAMERA_AND_TARGET_ROTATION is the behavior that handles texture and surface rotation (but not cropping). - Update StreamSharing to apply the rotation in the effect node if the option is selected. Update VirtualCamera to handle this accordingly. - Update the test app to use TRANSFORMATION_CAMERA_AND_TARGET_ROTATION as the default option for testing. The API is hidden for now. After it stabilizes, we will consider making it an official API. Bug: 310260193 Test: manual test and ./gradlew bOS Change-Id: I8f3264a68706fda82d96aef13febe76de2179af3
Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.
Jetpack comprises the androidx.*
package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.
Our official AARs and JARs binaries are distributed through Google Maven.
You can learn more about using it from Android Jetpack landing page.
For contributions via GitHub, see the GitHub Contribution Guide.
Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:
When contributing to Jetpack, follow the code review etiquette.
We are not currently accepting new modules.
Head over to the onboarding docs to learn more about getting set up and the development workflow!
Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.
Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:
Generate a HTTPS password: https://android-review.googlesource.com/new-password
Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement
AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal
and prebuilts/androidx/external
directories in your checkout. All the dependencies in these directories are also available from google()
, or mavenCentral()
. We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.