Have you try with [pix_share_read] and [pix_share_write] ? Then connect the [pix_share_write] to a [pix_mask] or [pix_multiply]. In all cases, you will need to use [gemframebuffer] to 'mask' certain processes/parts (the background and transform the particles in texture). But, i really recommand tu use GLSL in your patch to accelerate things. In my previous patch, you can add a GLSL 'part' on the gemchain where there is [gemhead 51] or simply use a [color 1 1 1 0.9] (although it is not really a biquad ;) on it. ++
Jack
Le lundi 07 juin 2010 à 21:59 +0200, patko a écrit :
but I still can't see the background image,
once I could see it but I couldn't get how I did it. +++++
Patrice Colet - 06 32 66 03 57
----- "Jack" jack@rybn.org a écrit :
OK, good ! ;) ++
Jack
Le lundi 07 juin 2010 à 21:10 +0200, patko a écrit :
the rendering order wasn't good in my patch, now you can see the
fading
Patrice Colet - 06 32 66 03 57
----- "patko" colet.patrice@free.fr a écrit :
yes, that's what I'm trying to achieve, it just misses the pretty fading we can obtain with biquad processing, but that is exactly that,
thanks ++++ Patrice Colet - 06 32 66 03 57
----- "Jack" jack@rybn.org a écrit :
Here a patch using GLSL and the frame buffer for feedback. Hope it helps. ++
Jack
Le lundi 07 juin 2010 à 17:00 +0200, patko a écrit :
oupse I've mixed [pix_threshold] and [pix_alpha]
it's about pix_alpha rather but I think you've understood,
indeed I'd like the particle reveals background image
the idea is about snaping the particle system over a black
rectangle
(the mask)
and then turning the white pixels to alpha for revelating the
(purple) rectangle
that should be rendered first
i've attached again the same patch but with [gemhead 5]
instead of
[gemhead 0]
+++
----- "Jack" jack@rybn.org a écrit :
> order rendering' because [gemwin 0] <=> [gemwin 50]. > If I understand, you want to see a background image when
the
> particles > are drawn ? > ++ > > Jack
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 2010-06-08 01:39, Jack wrote:
Have you try with [pix_share_read] and [pix_share_write] ? Then connect
[pix_share_*] only exist on osx and linux, so it's probably not such a good idea. these objects are intended for interprocess communication.
if you just need a storage for pixes, you can use [pix_buffer] and [pix_buffer_read]/[pix_buffer_write].
if you just want to share textures, you could use [pix_texture].
gmfadr IOhannes
-
IOhannes m zmoelnig -
Jack