garageCube

[rogierbrood]

Hi,
I've got this next problem since I've bought a new macbook pro,

Modul8 removes media's from my memory while there is enough momeory (4gb)
to hold all my 128 media's
I make sure that my media's are not to big in size,
modul8 doesnt import my media's as uncompressed, so that's not the case either,

In the medias preference, I've filled in 60 mbyte, 80% and 3000 mbyte,

does anyone had an idea about other elements that could be of influence?
as soon as I got more than some 40 medias imported im modul8, modul8 starts to release several medias out of the memory.
I use photojpg .movfiles of 400x300,

macbook is a 2.8Ghz intel core 2 duo, 4 gb 1067 Mhz ddr3

thanks in advance for any tip,

Rogier

[rogierbrood]

.. I tried to check out what's happening in my atMonitor,

whenever I start up modul8 (with no other applications open) my macbook is using 38% of the memory, I gues this is just normal.

When I open one of my modul8 files, and modul8 is starting to fill the memory with media's, the RAM meter is going to 80% and after that it suddenly goes down to 50% and stays there.
Almost all my media's are released at that moment and most of the red dots come back.

anyone had a similar experience?

thanks!

[glancer]

thats also my experience. modul8 seems to use only 50% of the installed memory.
(or storing the clips twice).
after o lot of loading and unloading clips during a vj session, the memory management
totally crashes. all clips are stuttering.
this can be solved by restarting every 3 hours.
its good to have a second computer and a vga/dvi switch as backup.

[david]

Hello,

When I open one of my modul8 files, and modul8 is starting to fill the memory with media's, the RAM meter is going to 80% and after that it suddenly goes down to 50% and stays there.
Almost all my media's are released at that moment and most of the red dots come back.

anyone had a similar experience?

I will try to explain how this memory management works.

1) Modul8 is a 32 bits application so could only use at max 4GB of RAM
2) Modul8 limits its use of memory to 70% of 4GB = 2.8GB. This is to avoid crash, because OpenGL/QuickTime could allocate large amount of memory on some occasions.
If you open ActivityMonitor (enable View | Columns | Virtual Memory), you will see this limitation : virtual memory will increase until it reaches 2.8GB, then Modul8 will begin to free some medias.
Virtual Memory is ALL the memory "allocated" by the process (Frameworks, drivers + their data, Modul8 data, ...)
When you say Modul8 uses only 50% of the available memory, you are speaking of "Real Memory".

3) when the memory usage goes over the limit, Modul8 tries to get some memory back by freeing media that were not used lately (using a timestamp)

And this is "the problem", media imported (and not used) have the same timestamp. Same for the media loaded when a project is loaded. So Modul8 decide to free all the media with this same timestamp (instead of choosing randomly among them).

Regards.

[rogierbrood]

HI,

thanks for the explanation,
I think I'm starting to understand how it works, but not entirely,
because my when I check my activitymonitor, and I open my modul8 file (and the memory is sucking all the media's in) I see the virtual memory go up to indeed 2.8GB, but what happens, is that modul8 starts to release media's till the virtual memory is back to somewhere about 1.4 GB,

I first thougt that was the timestamp: modul8 released a lot of medias at the same time, but when I start triggering medias who are red dotted, modul8 suck them in the memory, but releases some other media immediately.

why does the virtual memory stay at 1.4 GB, while it's assigned to stay at 2.8 GB? even when I retrigger al the media's with red dots..

Sorry if something slipped my mind, It's kind of a hard thing to understand,

thanks again for any answer!

[david]

I first thougt that was the timestamp: modul8 released a lot of medias at the same time, but when I start triggering medias who are red dotted, modul8 suck them in the memory, but releases some other media immediately.

why does the virtual memory stay at 1.4 GB, while it's assigned to stay at 2.8 GB? even when I retrigger al the media's with red dots..

I do not manage to reproduce this behavior on my Modul8 2.6.1

Except for the first "bach release", afterward, if I retrigger the media they a reloaded until the virtual memory gets close to 2.8GB.

Then, if I trigger one more media, it frees one or more media to make room for the triggered media. It will free "older" media first.
Of course, if this "older" media is 1GB and the new is 500MB, you will end up having 2.8+0.5-1= 2.3GB used

Regards

[rogierbrood]

Then, if I trigger one more media, it frees one or more media to make room for the triggered media. It will free "older" media first.
Of course, if this "older" media is 1GB and the new is 500MB, you will end up having 2.8+0.5-1= 2.3GB used

jep, that's clear, but that's not realy the case, my media's are an average of 15 mb, could it be some kind of wrong communication between the macbook and modul8? is it possible that the preferences of modul8 don't communicate with the memory?

thanks!

[rogierbrood]

..did a few more tests,
I've downloade an app called iFreeMem, which optimizes the ammount of free memory of your mac, after that I also rebooted.
When I startup my modul8 file, the virtual memory doesn't even reaches the 2.8 GB, when my 'real' memory reaches 1.6 GB, it just stops importing media and trows everything out (probably timestamp) and when I trigger all my media's it just stops again at 1.6 GB, while my piechart in the ActivityMonitor shows nearly 1 more GB of free memory space

I realy dont have a clue..