here is the patch
++
s.
stefan wrote:that is quite interesting, as i think that Gem is agnostic whether [pix_film] opens an image or a film: it just passes the request to QuickTime (which might then return a 1-frame "film")
I don't succeed to use the hottest gem...
anyway I will explain some others things I observe about that bug...
(using os X 10.5 + pd-0.41.4-extended-20090429)
with pix_film and .mov files there is no problem
(but there is a problem with still images when pix_film is used as
pix_image)
that's something else and more interesting (in terms of fixability) for me.
with pix_buffer, when the buffer is looped there is no problem
when I resize the buffer using [resize $1(the used memory increase
if I resize to a buffer with less frames the used-memory decrease...but...each times I resize pix_buffer there is a little bit less ram disponible..
could you please post an example patch that exposes this behaviour?
f
dasrm
IOhannes