[PD] pix_write ???

[Ulrich Kehrer]

hy bernard, list

pix_write has to be the last object of the gem-list (for example you have
to connect the OUTLET of a cube object to the inlet of pix_write)
pix_write's 2nd inlet understands a list of 2 integers which corresponds 
to the lower left corner of your snapshot (xy position). the 3rd inlet
also accepts a list of 2 integers which is the snapshot's size (xy size).
for example if your gemwin has 640x480 px and you want to grab the whole
win you have send "0 0" to the 2nd and "640 480" to the 3rd inlet. if you
just want to grab a 100x100px area from the center of the gemwin send "270
190" to the 3nd and "100 100" to the 3rd inlet ...
(the messages "vert_pos x y" and "vert_size x y" both to the 1st inlet do
the same as "x y" (position) to the second and "x y" (size) to the 3rd
inlet). was this clear?!?

the snapshots will be saved in the pd/bin directory with successive
numbers as tif files (gemmgem100000.tif).
i didn't find out yet how to tell pix_write a costum place to save the
tiffs and how to change the default name and the starting
number. ...johannes?

with a "metro 40" banging pix_write i grabbed a few seconds with
720x576px at 25fps. it was a patch with 9 cubes spinning around and i
noticed that pd/gem waited with the action until a snapshot was written to
disk. the 5 seconds i "recorded" took about 30 seconds to be saved. i then
got a 125 frame tiff-sequence with a smooth movement just like in the
gemwin. that's cool! can anyone explain this behavior?

cheers,
ulrich


On Tue, 27 Nov 2001, Bernhard [iso-8859-1] Zösmayr wrote:

> hello everyone,
> 
> can anybody tell me how to use the "pix_write" - object proper
> or where I can find documentation about it ?
> 
> thanks a lot
> 
> bernard