pix_film+separator=pd_crash!? - Pd-list

2 Mar 2003


      Hello
Last september, dmotd had a crashing issue with the pix_film or pix_movie
when used in combination with the separator object. I'm new to PD, and also
consistently crash pd when I turn on a rendering chain that has both
objects. I can't find a message on the PD list archive that ever finds the
problem with his patch. Did anyone figure out the problem, has it been
fixed, was it just a patching issue?
I get the exact same message he got:
The instruction at "0X015cf58b" referenced memory
at "0x0be06e8b". The memory could not be "read".
Any help would be much appreciated.
Alexander
PS: Is there any other way to split a video image to different objects and
retain each object's autonomous coordinates and values?
PPS: here is the simple patch again...
#N canvas 115 239 587 506 12;
#X obj 37 220 gemwin;
#X msg 33 95 0;
#X msg 65 113 1;
#X msg 98 136 create;
#X msg 129 161 destroy;
#X obj 299 33 gemhead;
#X obj 295 234 rotateXYZ;
#X obj 220 277 separator;
#X obj 365 272 separator;
#X obj 211 419 cube;
#X obj 371 420 cube;
#X floatatom 405 303 5 0 0;
#X floatatom 247 305 5 0 0;
#X floatatom 381 221 5 0 0;
#X obj 292 193 pix_texture2;
#X msg 385 51 auto $1;
#X obj 385 32 tgl 15 0 empty empty empty 20 8 0 8 -262144 -1
-1 0 1;
#X floatatom 327 137 5 0 0;
#X obj 293 166 pix_rgba;
#X obj 306 139 tgl 15 0 empty empty empty 20 8 0 8 -262144
-1 -1 01;
#X obj 295 112 pix_film;
#X msg 384 76 open homer.avi;
#X obj 213 339 translateXYZ;
#X obj 365 334 translateXYZ;
#X connect 1 0 0 0;
#X connect 2 0 0 0;
#X connect 3 0 0 0;
#X connect 4 0 0 0;
#X connect 5 0 20 0;
#X connect 6 0 7 0;
#X connect 6 0 8 0;
#X connect 7 0 22 0;
#X connect 8 0 23 0;
#X connect 11 0 23 1;
#X connect 12 0 22 2;
#X connect 13 0 6 3;
#X connect 14 0 6 0;
#X connect 15 0 20 0;
#X connect 16 0 15 0;
#X connect 18 0 14 0;
#X connect 19 0 18 0;
#X connect 20 0 18 0;
#X connect 20 1 17 0;
#X connect 21 0 20 0;
#X connect 22 0 9 0;