ARCore Android Studio 向相机视图添加滤镜
ARCore Android Studio add filter to camera view
我正在尝试向 Android Studio SDK 上的 ARCore 添加过滤器，例如 sobel 边缘检测。
目前我正在使用
GLES20.glReadPixels(x, y, w, h, GLES20.GL_RGBA, GLES20.GL_UNSIGNED_BYTE, intBuffer);
每帧从 glsurfaceview 读取图像并使用 GPU-Image 添加过滤器 Android。
但它会导致性能问题，例如丢帧并最终导致崩溃。
在 ARCore 中访问图像数据的最佳方式是什么？
我看到 ARCore 的 BackgroundRenderer 正在渲染相机视图，但我看不到它从哪里获取相机纹理。
怎么把过滤后的图片放回ARCore相机预览？
目前还没有真正好的方法来做到这一点。 They are aware of the limitation，我个人希望他们尽快添加框架访问功能。
在此期间， 可能会帮助您捕获帧。我已经实现了 PBO 写入，并且我可以以大约 15 fps 的速度捕获帧，而没有太多可见的延迟。
For the time being, your best bet for accessing image data is probably drawing the texture to a renderbuffer and using glReadPixels into a persistent-mapped pixel unpack buffer. Use a fence sync to detect when the glReadPixels is complete.
Another option is to use a compute shader and write directly to a persistent-mapped SSBO. (Disregard persistent-mapped suggestion. I thought EXT_buffer_storage had broader support)
The later is possibly fewer copies (the renderbuffer pixels may still hit DRAM even if you invalidate it after the glReadPixels), but it's also a less-common code path and incurs render/compute changeovers so I don't have intuition about which approach would be more efficient.
我正在尝试向 Android Studio SDK 上的 ARCore 添加过滤器，例如 sobel 边缘检测。
目前我正在使用
GLES20.glReadPixels(x, y, w, h, GLES20.GL_RGBA, GLES20.GL_UNSIGNED_BYTE, intBuffer);
每帧从 glsurfaceview 读取图像并使用 GPU-Image 添加过滤器 Android。
但它会导致性能问题，例如丢帧并最终导致崩溃。 在 ARCore 中访问图像数据的最佳方式是什么？
我看到 ARCore 的 BackgroundRenderer 正在渲染相机视图，但我看不到它从哪里获取相机纹理。 怎么把过滤后的图片放回ARCore相机预览？
目前还没有真正好的方法来做到这一点。 They are aware of the limitation，我个人希望他们尽快添加框架访问功能。
在此期间，
For the time being, your best bet for accessing image data is probably drawing the texture to a renderbuffer and using glReadPixels into a persistent-mapped pixel unpack buffer. Use a fence sync to detect when the glReadPixels is complete.
Another option is to use a compute shader and write directly to a
persistent-mappedSSBO. (Disregard persistent-mapped suggestion. I thoughtEXT_buffer_storagehad broader support)The later is possibly fewer copies (the renderbuffer pixels may still hit DRAM even if you invalidate it after the glReadPixels), but it's also a less-common code path and incurs render/compute changeovers so I don't have intuition about which approach would be more efficient.