[PD] Gem, make small snapshots while display original size?

[Martin .]

thanks for clarifying Johannes, [pix_buffer_write] works fine!

On Thu, Jun 19, 2008 at 3:24 PM, IOhannes m zmoelnig <zmoelnig at iem.at> wrote:
> Martin . wrote:
>>
>> Thanks for the help.
>>
>> [gemhead]
>> |
>> [pix_film]
>> |\
>> |  \
>> |   [pix_separator]
>> |   |
>> |   [pix_texture]
>> |   |
>> |   [pix_invert] (to differentiate the streams)
>> |   |
>> |   [pix_write]
>> |
>> [pix_separator]
>> |
>> [pix_texture]
>> |
>> [rectangle 2 1.5]
>>
>> here, still i get the image from [rectangle] / gemwin in the
>> recordings from [pix_write]. Is that right?
>
> ah yes sorry, i forgot:
> [pix_write] is currently "broken" by design, as it grabs the framebuffer and
> writes that to disk, instead of just writing an incoming pix-stream (e.g.
> coming from [pix_snap])
>
> future versions of Gem (i think in the next release:-); i just don't have
> time to do this in the next few days) will have an object e.g.
> [pix_image_write] that will write pix-data into images.
> [pix_write] will then be implemented as abstraction with [pix_snap] and
> [pix_image_write]
>
>
> so what can you do know?
> - write the pixes into a movie with [pix_record]
> - store the pix into a [pix_buffer] and use the [save( message to write it
> to disk. e.g.
>
>
> [gemhead]
> |
> +-------------------+
> |                   ...
> [pix_separator]
> |
> [pix_invert]
> |
> [t a b]
> |     +-----------------+
> |                       [0(
> [pix_buffer_write $0-buf]
> |
> [b]
> |
> [save filename(
> |
> [pix_buffer $0-buf 1]
>
>
> or similar (this is from memory)
>
>
> fgmasdr
> IOhannes
>
> PS: btw, you don't need the [pix_texture] in the branch that does not render
> the image; it will use ressources without any benefit.
>