Forums - Low visual video frame rate on adreno200

3 posts / 0 new
Last post
Low visual video frame rate on adreno200
Zhao_Xiaolu
Join Date: 6 Mar 11
Posts: 1
Posted: Wed, 2011-12-07 02:18

Hello, Guys

I want to do the video playback rendering on the adreno 200 platform (Qualcomm 8x55 chipset). My basic way to do this, is to update partial texture with glTexSubImage2D, and glDrawTexiOES to draw the frame out per frame period (like 33 ms). However, it turn out to be looks like updating only 1 frame per second. I used adreno profiler to check, the frame rate is always about 24 fps, which is correct. But the visual effect is much bad.

I suspect the texture bandwidth is bottleneck here, however, using compressed texture during the runtime is not practical way. Can some one help me to point out possible problem here?

Thank you very much.

  • Up0
  • Down0
Zhenhua_Qu
Join Date: 11 Dec 11
Posts: 3
Posted: Sun, 2012-01-22 18:12

Similar problem is observed in Opengl es 2.0. The bottleneck seems to be the time GPU fetching texture data with texture2D(). eglSwapBuffer also takes some time. I can only achive 10 fps for simply display a 800x480 texture on the screen.

  • Up0
  • Down0
Mark_Feldman Moderator
Join Date: 4 Jan 12
Posts: 58
Posted: Thu, 2012-02-02 08:30

Normal 0 false false false EN-US X-NONE X-NONE

Would like to better understand the need for using OpenGLES to display full screen video..

 

Also would like to know the format of the video source.

 

When using glTexSubImage2D or glTexImage2D make sure all changes are applied to the texture, before doing any rendering.  glTexImage2D is likely more optimized than using glTexSubImage2D.

 

Possibly try to double buffer, making changes to one texture while using another texture, and swap those next frame.

 

Lastly introduced in Ice Cream Sandwich, there's an Androi SurfaceTexture API which will be your best option for doing video output in OpenGL ES..  http://developer.android.com/reference/android/graphics/SurfaceTexture.html

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.