android / android/camera-samples
DEPTH 16 format produces 0 values
- Lenguaje dominante
- Kotlin
- Estrellas
- 5.5k
- Forks
- 2.4k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
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
Guía de contribución
Línea de trabajo
Comience revisando la documentación de la Camera2 API para ImageFormat.DEPTH16, ImageReader y las solicitudes de captura. Reproduzca el problema usando la configuración DEPTH16 de 240×180 mostrada, tanto con session.capture como con setRepeatingRequest, y determine después si las muestras con valor cero y fuera de rango indican un comportamiento no compatible del dispositivo o un error de la aplicación.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- kotlin
- Área
- mobile-dev
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100