Databases
StackOverflow2013
Postsdbo
POSurfaceTexture updateTexImage to shared 2 EGLContexts - Problems on Android 4.4
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSurfaceTexture updateTexImage to shared 2 EGLContexts - Problems on Android 4.4
    primarykey
    data
    text
    <p>I am referring to this excellent example of how to encode the preview frames of the camera directly into an mp4 file: <a href="http://bigflake.com/mediacodec/CameraToMpegTest.java.txt" rel="nofollow">http://bigflake.com/mediacodec/CameraToMpegTest.java.txt</a></p> <p>I have adopted the code in the way that I also would like to render the preview image on the screen. Therefore I got something like a GLTextureView with its own EGLContext. This Context is then used as shared EGLContext when I create the EGLContext for the encoder rendering:</p> <pre><code>mEGLContext = EGL14.eglCreateContext(mEGLDisplay, configs[0], sharedContext == null ? EGL14.EGL_NO_CONTEXT : sharedContext, attrib_list, 0); </code></pre> <p>In my render-loop I followed the tip of fadden... for every frame I do the following:</p> <ol> <li>first I wait for the new image to arrive on the SurfaceTexture with awaitNewImage()</li> <li>then I set the GLTextureView's context current and render the frame on it</li> <li>after that I set the encoders context current and render the frame on it</li> </ol> <p>This looks something like that:</p> <pre><code>mFrameWatcher.awaitNewImage(); mSurfaceTexture.updateTexImage(); _textureView.getEGLManager().makeCurrent(); _textureView.requestRender(); mInputSurface.makeCurrent(); mInputSurface.requestRender(); </code></pre> <p>This worked well while I tested it only on my Nexus 4 with Android 4.3.</p> <p>However, since I got the new Nexus 5 with Android 4.4 the encoder only gets 2 different frames per second from the SurfaceTexture... but these 2 frames are repeatedly drawn... so he encodes 15 times the same frame. ALTHOUGH the frames are rendered correct to my GLTextureView with 30 different frames per second. I first thought this might be a Nexus 5 problem - so I updated another Nexus 4 to Android 4.4... but it is the same on the Nexus 4 now.</p> <p>I played around a bit - and finally I was able to solve the problem, by detaching and re-attaching the SurfaceTexture to the different context's when I switch them. This looks something like this:</p> <pre><code>mFrameWatcher.awaitNewImage(); mSurfaceTexture.updateTexImage(); _textureView.getEGLManager().makeCurrent(); _textureView.requestRender(); mSurfaceTexture.detachFromGLContext(); mInputSurface.makeCurrent(); mSurfaceTexture.attachToGLContext(_textureViewRenderer.getTextureId()); mInputSurface.requestRender(); mSurfaceTexture.detachFromGLContext(); _textureView.getEGLManager().makeCurrent(); mSurfaceTexture.attachToGLContext(_textureViewRenderer.getTextureId()); </code></pre> <p>My question now is: Is this the correct way to do this? Honestly I thought the re-attaching of the SurfaceTexture should not be necessary when I use shared contexts. Also the re-attaching takes quite a long time... 3-6 ms for every frame with peeks on 12 ms, which could be better used for rendering. Am I doing/understanding somethind wrong here? Why did it work like a charm on the Nexus 4 with 4.3 without the need to re-attach the SurfaceTexture?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJasonMArcher
    1. USmAx
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSurfaceTexture updateTexImage to shared 2 EGLContexts - Problems on Android 4.4
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSurfaceTexture updateTexImage to shared 2 EGLContexts - Problems on Android 4.4
      1. USdbro
      1. VTFavorite
    1. COSounds similar to http://stackoverflow.com/questions/20386515/glsurfaceview-framerate-issues-on-nexus-5
      singulars
      1. POSurfaceTexture updateTexImage to shared 2 EGLContexts - Problems on Android 4.4
      1. USfadden
    2. COCan you look at the former case with systrace()? I'm curious if you're getting stuck in `eglSwapBuffers()` on 4.4. (There was a behavior change to `TextureView` in 4.4 that causes it to wait for previously-submitted buffers to be acquired by the consumer; in 4.3 if you submitted buffers too quickly it would just drop the old ones.)
      singulars
      1. POSurfaceTexture updateTexImage to shared 2 EGLContexts - Problems on Android 4.4
      1. USfadden
    3. COI will go deeper into this soon... But I'm not sure its the fault of the TextureView, since the preview rendered to the TextureView is displayed correctly with 30fps... however if I change the sequence and render to the encoder first and after that on the TextureView, I got a 30fps mp4 and a 2fps preview on the SurfaceTexture. My guess is it has to do something with the context siwtching... Our Nexus 7 2012 with Android 4.4 e.g. gets an ANR when we switch the contexts in the render loop... but that only occurs on the Nexus 7, the other devices with 4.4 get the fps drops...
      singulars
      1. POSurfaceTexture updateTexImage to shared 2 EGLContexts - Problems on Android 4.4
      1. USmAx
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload