[GEM-dev] missing [pix_write], that does only take pixes

chris clepper cgclepper at gmail.com
Tue Jun 5 17:05:44 CEST 2007


My guess is that pix_write came before pix_snap which is why they have
duplicate functionality.

I suppose pix_write could have two modes: one for capturing the GL
backbuffer and one for working with pix_ frames.  That is about as
good/bad as pix_image_write for a solution.

On 6/4/07, Roman Haefeli <reduzierer at yahoo.de> wrote:
> hello everyone
>
> i just realized, that [pix_write], unlike [pix_record], takes its images
> from the framebuffer. when working exclusively in the pix-domain, using
> [pix_write] creates a huge cpu-overhead, that wouldn't be necessary,
> afaik. otoh, [pix_record] does crash to often to be used in everyday
> life.
> is there a way to capture single images from a pix-stream? if not, are
> there plans for a [pix_image_write] (or however this should be called)?
>
> roman
>
>
>
> ___________________________________________________________
> Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
>
> _______________________________________________
> GEM-dev mailing list
> GEM-dev at iem.at
> http://lists.puredata.info/listinfo/gem-dev
>




More information about the GEM-dev mailing list