RE: Is there a faster way to get a PBuffer on screen in CoreGraphics?

Subject: RE: Is there a faster way to get a PBuffer on screen in CoreGraphics?

From: Joe Jones <email@hidden>

Date: Tue, 25 Nov 2008 14:53:01 -0800

Accept-language: en-US

Acceptlanguage: en-US

Delivered-to: email@hidden

Thread-index: AclPS5a3Szs/0mVdTDyAv/dEeN8biwABPhQg

Thread-topic: Is there a faster way to get a PBuffer on screen in CoreGraphics?

I am. L

From: mac-opengl-bounces+joejo=email@hidden [mailto:mac-opengl-bounces+joejo=email@hidden] On Behalf Of David Wolstencroft
Sent: Tuesday, November 25, 2008 2:16 PM
To: email@hidden
Subject: Re: Is there a faster way to get a PBuffer on screen in CoreGraphics?

Use Pixel Buffer Objects (PBOs) for asynchronous glReadPixels

On Tue, Nov 25, 2008 at 11:07 AM, Joe Jones <email@hidden> wrote:

Currently, due to some sever app limitations that I do not control, I have to use a CGL PixelBuffer in order to do OGL rendering, I then call glReadPixels on it to pull it into a block of memory that I then use to create a CGImageRef in order to draw the GL image into the target CGContext that I have to work with.

glReadPixels is SLOW. This I know. My question is: Is there any way to sidestep this so I can get the image to screen w/o the copy? I can't find one in the docs but I thought I'd send a call out to the list to see if anyone had any ideas.

Thanx,

Joe

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Mac-opengl mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Mac-opengl mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden

References:
	>Is there a faster way to get a PBuffer on screen in CoreGraphics? (From: Joe Jones <email@hidden>)
	>Re: Is there a faster way to get a PBuffer on screen in CoreGraphics? (From: "David Wolstencroft" <email@hidden>)