0

I want to display 3D objects with jPCT, so I use a custum GLSurfaceView.Renderer to display what I want. And below, I need to display a camera preview.

It's work fine but my problem is when I display the 2 SurfaceView (1 for the object and 1 for the camera preview), I had lag on my software. I test it and it's because I use 2 SurfaceView at the same time.

How can I resolve it ? I try to display my 3D object on my camera preview that extends GLSurfaceView :

public class CameraView extends GLSurfaceView implements SurfaceHolder.Callback

But the objects are never display and some functions don't work (Like search an 3D object in a 2D view ...)

Anyone have an idea ?

fadden
  • 51,356
  • 5
  • 116
  • 166
Mekiis
  • 5
  • 3

1 Answers1

0

There's a couple of possibilities. One is that there is some interaction between your renderer threads that is causing lag. Another is that adding an additional layer has caused the system to perform additional GLES composition, and that's slowing you down. (See this doc for background.)

The "objects are never display" statement makes me a bit unsure as to what the actual issue is.

Either way, one approach to correct this is to eliminate the camera SurfaceView. You can send the camera preview to a SurfaceTexture (API 11+) and then render the contents on the main GLSurfaceView as a textured quad. An example of this can be found in the "Texture from Camera" activity in Grafika.

fadden
  • 51,356
  • 5
  • 116
  • 166
  • It's seam to be a good idea to use SurfaceTexture. But I don't understand how it's works ... Have you a simple exemple to explain how to use a SurfaceView and to link with the main GLSurfaceView ? – Mekiis May 12 '14 at 12:26
  • The "Texture from camera" activity in Grafika (linked from the answer) is relatively straightforward -- there's a lot of pieces involved, so it won't be trivial. I'm using a plain SurfaceView rather than a GLSurfaceView there. The "Show + capture camera" activity uses a GLSurfaceView, and also records the camera output, but it's a bit more convoluted (in part because GLSurfaceView is managing the render thread and the activity wants to use a shared EGL context). FWIW, explanation is here: http://source.android.com/devices/graphics/architecture.html – fadden May 12 '14 at 16:13