[PD] GEM pix_image+ram
stefanpiat at gmail.com
Mon Apr 27 12:48:41 CEST 2009
I will try to compile the "hottest" gem...
2009/4/27 IOhannes m zmoelnig <zmoelnig at iem.at>
> stefan wrote:
>> I'm working on a patch where I have to load multiple image to create an
>> (I don't want to make a .mov file cause it's kind of real-time editing)
>> I tried with pix_image, pix_film, pix_buffer...
>> and with all of these objects (same if frames are looped or not) the
>> used-memory increase until it crash pd...
>> some people already had the same problem before:
>> I was wondering if there is a way to fix this without having to restart
>> a way to unload the image which stays in memory?
> first of all, this bug in Gem has been fixed in recent SVN (after your
> initial bug-report)
> the obvious solution is to run the hottest Gem (no release out, though; so
> you have to compile it yerself)
> and since it is (was) a bug in the implementation of Gem, there is no way
> you can "fix" it in Pd. the only workaround is to restart Pd (which will
> free all stray memory). "unloading" does not work, because the memory had
> been lost.
> "and the patch : put this to / and put a folder called "frames" beside
> do not do that.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list