From: Marcin Romaszewicz (marcin++at++asmodean.engr.sgi.com)
Date: 11/12/2001 14:52:36
Don't call setImage each frame. If you do this, Performer and OpenGL think
you're re-defining the texture, where you're only changing the
contents. Take a look at the pfTexture::subload function in the
manpage. Subloading is a faster way to change the contents of the texture,
though it is still limited by bandwidth. To maximize speed, make sure that
your texture's external and internal formats are the same so that the
OpenGL library does not have to convert.
-- Marcin
On Mon, 12 Nov 2001 lai++at++daimi.au.dk wrote:
> I have integrated SMPEG into a custom performer library. SMPEG is a library for
> decompressing mpeg1 movies. This requires me to call pfTexture::setImage each
> frame to upload the new decompressed image to texture memory. This however,
> seems to be a bottleneck. With the bandwidth that O2 and Octanes provide, I
> cannot see how this could be a problem. The textures have a max size of 512x512.
> Is there any special attributes I can set on the pfTexture to speed up the
> operation. Do you have any other suggestions that might be helpful.
>
> Thanks
>
> /Gorm
> -----------------------------------------------------------------------
> List Archives, Info, FAQ: http://www.sgi.com/software/performer/
> Open Development Project: http://oss.sgi.com/projects/performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
> -----------------------------------------------------------------------
>
This archive was generated by hypermail 2b29 : Mon Nov 12 2001 - 14:52:40 PST