[PD] [gemframebuffer] and [pix-film] ... weirdness

oliver oliver at klingt.org
Fri Mar 2 01:33:38 CET 2018


hi, list !

PD 0.48-0
GEM 0.93.3
WINDOWS 7 / 64bit

i encountered a weird thing in GEM recently:

when i use [gemframebuffer] with a still image (using [pix_image]) i can 
work with glsl shaders like shown in the GEM tutorials.

however, i recently tried to do the same with a movie (using [pix_film], 
but only the first frame of the loaded film showed up ! subsequent 
"frame" messages did not work.

by chance i found out that when i connected an empty [pix_image] object 
to [pix_film]'s left outlet, it suddenly DOES work as expected !

is this the way it's supposed to be ?

am i missing something ?

or is this a windows thing again ?



i attached a patch that demonstrates the problem
(btw: using [pix_movie] instead of [pix_film] didn't change anything)



thanks for any help
(or deeper insight into [gemframebuffer]'s mysteries)


best

oliver

-- 
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
/////////////// http://pendler.klingt.org //////////////
\\\\\\\\\\\\\\\ http://oliver.klingt.org  \\\\\\\\\\\\\\
////////////////////////////////////////////////////////
-------------- next part --------------
#N canvas 0 50 977 403 10;
#X declare -stdlib Gem;
#X obj 318 167 cnv 15 100 80 empty empty empty 20 12 0 14 -204786 -66577
0;
#X msg 222 91 rectangle 1;
#X obj 312 54 gemhead 50;
#X obj 328 255 pix_texture;
#X obj 312 302 pix_texture, f 16;
#X obj 312 75 t a a b, f 10;
#X floatatom 518 163 5 0 0 0 - - -, f 5;
#X obj 328 177 pix_film, f 13;
#X obj 340 108 gemframebuffer;
#X obj 340 130 translateXYZ 0 0 -4;
#X obj 328 277 square 4;
#X obj 14 11 cnv 14 128 15 empty empty empty 2 2 0 9 -253181 -66577
0;
#X obj 13 10 declare -stdlib Gem, f 21;
#X msg 25 287 0 \, destroy;
#X text 20 196 GEM WINDOW;
#X obj 13 140 del 300;
#X obj 13 337 print ggggg;
#X obj 13 312 gemwin 25;
#X msg 13 217 dimen 480 270 \, offset 10 550 \, color 0.5 0.5 0.5 \,
create \, 1, f 14;
#X obj 13 116 loadbang;
#X msg 426 212 dimen \$2 \$3;
#X obj 222 70 del 300;
#X obj 222 46 loadbang;
#X obj 344 212 pix_image;
#X msg 199 134 open extra/Gem/examples/data/homer.avi, f 18;
#X obj 476 92 f;
#X obj 503 92 + 1;
#X obj 485 116 sel 85;
#X msg 474 139 0;
#X obj 312 350 square 2.5;
#X obj 312 327 translateXYZ -3 0 0;
#X obj 688 167 cnv 15 100 80 empty empty empty 20 12 0 14 -204786 -66577
0;
#X msg 592 91 rectangle 1;
#X obj 698 255 pix_texture;
#X obj 682 302 pix_texture, f 16;
#X obj 682 75 t a a b, f 10;
#X floatatom 888 163 5 0 0 0 - - -, f 5;
#X obj 698 177 pix_film, f 13;
#X obj 710 108 gemframebuffer;
#X obj 710 130 translateXYZ 0 0 -4;
#X obj 698 277 square 4;
#X msg 796 212 dimen \$2 \$3;
#X obj 592 70 del 300;
#X obj 592 46 loadbang;
#X msg 569 134 open extra/Gem/examples/data/homer.avi, f 18;
#X obj 846 92 f;
#X obj 873 92 + 1;
#X obj 855 116 sel 85;
#X msg 844 139 0;
#X obj 682 350 square 2.5;
#X obj 682 327 translateXYZ 3 0 0;
#X obj 682 54 gemhead 52;
#X text 312 31 WORKING:;
#X text 681 31 NOT WORKING:;
#X text 141 193 this extra [pix_image] (that seems to do nothing at
all) apparently makes all the difference. how so ?, f 28;
#X connect 1 0 3 0;
#X connect 1 0 4 0;
#X connect 1 0 8 0;
#X connect 2 0 5 0;
#X connect 3 0 10 0;
#X connect 4 0 30 0;
#X connect 5 0 4 0;
#X connect 5 1 8 0;
#X connect 5 2 25 0;
#X connect 6 0 7 1;
#X connect 7 0 3 0;
#X connect 7 0 23 0;
#X connect 7 1 20 0;
#X connect 8 0 9 0;
#X connect 8 1 4 1;
#X connect 9 0 7 0;
#X connect 13 0 17 0;
#X connect 15 0 18 0;
#X connect 17 0 16 0;
#X connect 18 0 17 0;
#X connect 19 0 15 0;
#X connect 20 0 8 0;
#X connect 21 0 1 0;
#X connect 21 0 24 0;
#X connect 22 0 21 0;
#X connect 24 0 7 0;
#X connect 25 0 26 0;
#X connect 25 0 27 0;
#X connect 26 0 25 1;
#X connect 27 0 28 0;
#X connect 27 1 6 0;
#X connect 28 0 25 0;
#X connect 30 0 29 0;
#X connect 32 0 33 0;
#X connect 32 0 34 0;
#X connect 32 0 38 0;
#X connect 33 0 40 0;
#X connect 34 0 50 0;
#X connect 35 0 34 0;
#X connect 35 1 38 0;
#X connect 35 2 45 0;
#X connect 36 0 37 1;
#X connect 37 0 33 0;
#X connect 37 1 41 0;
#X connect 38 0 39 0;
#X connect 38 1 34 1;
#X connect 39 0 37 0;
#X connect 41 0 38 0;
#X connect 42 0 32 0;
#X connect 42 0 44 0;
#X connect 43 0 42 0;
#X connect 44 0 37 0;
#X connect 45 0 46 0;
#X connect 45 0 47 0;
#X connect 46 0 45 1;
#X connect 47 0 48 0;
#X connect 47 1 36 0;
#X connect 48 0 45 0;
#X connect 50 0 49 0;
#X connect 51 0 35 0;


More information about the Pd-list mailing list