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

[B. Bogart]

I think this would be best implimented into the pix_buffer stuff, so
that you would choose some frames from a pix chain (not the framebuffer)
write them to a pix_buffer, and then save them from there. pix_write is
really for writing files from the framebuffer, not from chains...

I wonder if anyone has made a patch that saves the framebuffer with
pix_write and also loads that image somehow, not a very easy task...

I vote for "open" and "save" for pix_buffer. I think pix_buffer may
already support "open?"

..b..

chris clepper wrote:
> On 6/5/07, Roman Haefeli <reduzierer at yahoo.de> wrote:
>> On Tue, 2007-06-05 at 10:05 -0500, chris clepper wrote:
>>> 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.
>> sorry to stick with this, but will there be such a thing in future
>> versions of gem?
> 
> The certainly could be.  I guess we just have to decide on which way
> to do it.  pix_image_write is fine with me.
> 
> This is actually not a bad starter project for someone looking to
> figure out how GEM pix_ processing works.  It doesn't require any per
> pixel loops and you have to dig around in some base classes to get the
> image exporter function.
> 
> _______________________________________________
> GEM-dev mailing list
> GEM-dev at iem.at
> http://lists.puredata.info/listinfo/gem-dev
>