Android: setPreviewCallbackWithBuffer, buffer in the queue and no callbacks

最新推荐文章于 2024-11-08 21:02:25 发布

随风而去飘飘飘

最新推荐文章于 2024-11-08 21:02:25 发布

阅读量2k

点赞数

分类专栏： android

android 专栏收录该内容

89 篇文章

订阅专栏

本文探讨了在Android应用中优化相机预览帧处理速度的方法，通过使用setPreviewCallbackWithBuffer替代setPreviewCallback，并在回调方法中合理管理缓冲区，实现更高效的帧处理流程。同时，文章指出了在回调时机上的工作规避策略，以及可能存在的预览表面未准备好的问题，提供了解决方案。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

If you want to process Camera preview frames on Android, you need to acquire them with setPreviewCallback or setPreviewOneShotCallback or setPreviewCallbackWithBuffer on the Camera.

setPreviewCallback works as advertised, but slows the camera to just few frames per second. For better camera FPS, use setPreviewCallbackWithBuffer (it can re-use the same buffer without allocating it every frame). Just add the same buffer to the queue after it is processed in Camera.PreviewCallback. If the queue is empty, the preview frames are skipped (and it may improve FPS too, so it is a good thing).

My problem was that even if I had the buffer in the queue, the callback didn't run. However, if I called setPreviewCallbackWithBuffer some seconds later (not in onResume of the activity), the entire thing worked as intended.

I suppose, it has something to do with the surface for the preview not being ready when I call the setPreviewCallbackWithBuffer. This bug may be related: http://code.google.com/p/android/issues/detail?id=13966

My workaround is:

onResume of the activity, do setPreviewOneShotCallback; and the callback will happen when the camera is ready;
in the callback method, when it is called the first time, allocate the buffer and setPreviewCallbackWithBuffer;
after every callback addCallbackBuffer to the Camera.