Hello Oliver, As workaround you can put a [pix_separator] between the [t a a b] and [pix_texture]. But yes, the bahavior is weird. ++
Jack Le 02/03/2018 à 01:33, oliver a écrit : > 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 > > > > _______________________________________________ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list > _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list