android / android/camera-samples
DEPTH 16 format produces 0 values
- Langage dominant
- Kotlin
- Étoiles
- 5.5k
- Forks
- 2.4k
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Is DEPTH16 in Camera2 API ready to use? or we are supposed to use ARCore for depth detection? My use case is not to render depth data/image continuously on screen, but to capture a JPEG image and it's depth when user tap on capture button in a shot.
I created a capture request of TEMPLATE_PREVIEW / TEMPLATE_STILL_PICTURES for target image reader of Image Format DEPTH16 as following.
```
imageReader = ImageReader.newInstance(
240, 180, ImageFormat.DEPTH16, IMAGE_BUFFER_SIZE)
```
```
val captureRequest = camera.createCaptureRequest(
CameraDevice.TEMPLATE_PREVIEW).apply {
addTarget(depthImageReader.surface)
}
```
captureRequest.set(CaptureRequest.JPEG_ORIENTATION, 0)
val fpsRange: Range = Range(15, 30)
captureRequest.set(CaptureRequest.CONTROL_AE_TARGET_FPS_RANGE, fpsRange)
session.capture(captureRequest.build(), null, null)
```
imageReader.setOnImageAvailableListener({ reader ->
val image = reader.acquireNextImage()
```
on this image , with session.capture, the depth samples are all 0. if I replace it with session.setRepeatingRequest(captureRequest.build(), null, null), the first frames are still all 0 values, after some movement, the later frames has a a lot of 0, 8192, and very large values such as 17524 (17m which is not correct?), along with some random range.
I've tested https://medium.com/swlh/working-with-the-3d-camera-on-the-samsung-s10-5g-4782336783c , however the first frames are 0 as well
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par examiner la documentation de la Camera2 API pour ImageFormat.DEPTH16, ImageReader et les requêtes de capture. Reproduisez le problème avec la configuration DEPTH16 240×180 présentée, à la fois avec session.capture et setRepeatingRequest, puis déterminez si les échantillons nuls et hors limites indiquent un comportement non pris en charge par l’appareil ou une erreur de l’application.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- kotlin
- Domaine
- mobile-dev
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100