On Mon, 18 Mar 2002, IOhannes m zmoelnig wrote:
i do not really now. i noticed similar behaviour under linux. so there is definitey a memory hole somewhere. but i did not notice it with all used libraries (i cannot remember right now which one did not leak: libmpeg1/libmpeg3/libquicktime4linux)
it couldn't be those libraries, i'm actually using windows. ... this problem only seems to occur when the clips, even the same clips, are loaded many times, over and over. maybe the memory map doesn't get cleared and that's what fills up the RAM.
Also, you could try opening up one huge movie with all your clips in it (like a wavetable) and then having messages for each section (start frame end frame etc). This way, you wont ever need to change the clip.
might at least be a workaround
i just tried this and i seems to work... do you have any suggestions on a way to store all the clip in/out points?