[GEM-dev] pix_buffer* & pix_write

[chris clepper]

While I think some of these are good ideas relating to pix_buffer, none of
them strike me as something which can only be done on the C code level or
would pose some great advantage by doing it there - the possbile exception
might be the clearing code.  Loading and saving images can be done on the
patching level using existing objects.

I have no idea what you would do with a gemlist written to a file.  It
doesn't strike me as something that would be useful for later apart from
possibly debugging.  What is your reasoning behind this request?

cgc

On 2/22/06, B. Bogart <ben at ekran.org> wrote:
>
> Hey all,
>
> So I've been working a lot with the pix_buffer (depot) stuff and had a
> few ideas that would make using it even more useful:
>
> * The ability to colour the buffer black, effectively clearing it
> without deallocating memory.
>
> * The ability to load and save the images in a buffer, basically being
> able to take a snapshot of the system so that the same images that were
> in the buffers can be reloaded, restoring the original state.
>
> * It would be also nice to be able to save a particular frame rather
> than the whole buffer.
>
> "load [filename]"
> to pix_buffer_read could load the [filename] into the slot already set
> by the pix_buffer_read index. "load [wildcard] 10" would load 10 images
> matching the wildcard pattern into 10 slots (reallocate if needed?)
>
> "save [filename]" to pix_buffer_write would save the image in the
> current slot to that filename. "save [filename] 10" could save images
> from the first 10 slots to filename with an id appended: "file0000",
> "file0001" etc..
>
> "clear 10" or "clear" to pix_write would clear the first 10 slots, or
> the current slot respectively. "black" may work instead of the word
> "clear".
>
> Oh and It would be amazing if you could put pix_write in a gemchain and
> have it only capture that gemlist in the buffer... or maybe the current
> pix_write should be called something like window_write since it does not
> actually save what is happening in the pix_ of a chain...
>
> Thanks!
>
> .b.
>
>
> _______________________________________________
> GEM-dev mailing list
> GEM-dev at iem.at
> http://lists.puredata.info/listinfo/gem-dev
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20060222/9181f4a9/attachment.htm>