-
-
Notifications
You must be signed in to change notification settings - Fork 992
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs: Update
photoHdr
and lowLightBoost
docs
- Loading branch information
Showing
1 changed file
with
5 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -196,6 +196,9 @@ export interface CameraProps extends ViewProps { | |
/** | ||
* Enables or disables HDR Photo Capture via a double capture routine that combines low- and high exposure photos. | ||
* | ||
* On Android, {@linkcode photoHdr} uses a vendor-specific "HDR" extension which is not compatible with {@linkcode videoHdr}, | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
mrousavy
Author
Owner
|
||
* so only one of video- or photo-HDR can be enabled at a time. | ||
* | ||
* Make sure the given {@linkcode format} supports HDR (see {@linkcode CameraDeviceFormat.supportsPhotoHdr format.supportsPhotoHdr}). | ||
*/ | ||
photoHdr?: boolean | ||
|
@@ -235,6 +238,8 @@ export interface CameraProps extends ViewProps { | |
* Enabling low light boost allows the FPS rate to be throttled to up to half of what it is set to to allow for more | ||
* exposure in low light conditions. | ||
* | ||
* On Android, {@linkcode lowLightBoost} might even use a vendor-specific "night-mode" extension to allow for even more visibility in low-light conditions. | ||
* | ||
* Make sure the given {@linkcode device} supports low-light-boost (see {@linkcode CameraDevice.supportsLowLightBoost device.supportsLowLightBoost}). | ||
*/ | ||
lowLightBoost?: boolean | ||
|
woaaaa, this is interesting, i faced this before, do we have any validations to prevent using both or just docs?