Page 1 of 1

Modul8 choking on clips in compressed memory

Posted: Tue Oct 10, 2006 7:48 pm
by deckard97
Hello,

I have an issue with Module8, I have a video clip, 720X480 on a 1024X768 stage, medium photoJPEG compression, 30fps, around 7 minutes in length.
Got a G5 dual 2GHZ, 2.5GB of RAM, geforce 6600, RAID 0.

I import it and have it load in compressed memory (640MB), so basically it's totally stored in the RAM.

I then control the playback of this clip through MIDI, I play it once, rewind a bit, increase speed, then normal speed, etc, for about 10 minutes (it's for a theater play).
But then after a while, Modul8 starts to choke, when I fast forward through the clip (increase the layer's speed), Modul8 increasingly chokes up to the point where I get 1 frame per 10 seconds and then it totally hangs.

Activity Monitor reports Modul8 only uses about 1GB of RAM, so there's plenty left, and it's not even using all of the processor's cycles and I have no other application running.

I had to quit and start over for Modul8 to start behaving normally.

It seems like the more I play with a movie clip, the more it chokes up on it, which is odd for me since the computer's performance is not taxed and there's plenty of power left.

Let me know if you need more info or even if you want me to post this in the french section of the forum.

Thanks

Re: Modul8 choking on clips in compressed memory

Posted: Thu Oct 12, 2006 1:06 pm
by boris
What version of modul8 did you use, what version of macosx, quicktime...

Do you have only one geforce 6600 or more ?
Can you check the free physical memory on your computer when the problem come ?

Thanks.

Posted: Thu Oct 12, 2006 7:31 pm
by deckard97
One GeForce 6600.
QuickTime 7.1.3
OS X 10.4.8

Ok, just tested it again, here goes
System Memory:
Wired: 210MB
Active: 150MB
Inactive: 1.87GB
Used: 2.21GB

Free: 300MB
VM Size: 8.26GB

Posted: Thu Oct 12, 2006 8:42 pm
by boris
Can you open a terminal, write "top" ->enter
And copy all data...

And also what is the version of MODUL8 did you use ?

Thanks.

Posted: Thu Oct 12, 2006 11:06 pm
by deckard97
Modul8 Version 2.03.

here's an average of TOP:

Processes: 51 total, 4 running, 47 sleeping... 186 threads 17:01:44
Load Avg: 1.49, 0.81, 0.38 CPU usage: 59.5% user, 6.3% sys, 34.2% idle
SharedLibs: num = 172, resident = 39.3M code, 4.27M data, 5.95M LinkEdit
MemRegions: num = 6877, resident = 1.09G + 8.63M private, 98.4M shared
PhysMem: 216M wired, 140M active, 1.88G inactive, 2.22G used, 281M free
VM: 7.95G + 123M 29079(0) pageins, 120(0) pageouts

PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE VSIZE
649 top 7.7% 0:04.10 1 18 22 460K 296K 2.29M 26.9M
641 bash 0.0% 0:00.01 1 14 16 156K 744K 812K 27.2M
639 login 0.0% 0:00.01 1 16 36 148K 312K 572K 26.9M
637 Terminal 0.3% 0:00.53 4 91 123 1.75M 8.02M 6.43M 357M
635 MIDIServer 0.0% 0:00.54 15 284 166 2.35M 5.46M 6.71M 306M
634 Modul8 115.1% 4:29.46 14 198 817 1.01G- 38.9M 1.01G- 1.42G-
615 mdimport 0.0% 0:00.52 4 62 54 1.05M 2.80M 3.16M 39.8M
571 cupsd 0.0% 0:00.54 2 30 26 672K 776K 1.64M 27.9M
379 StuffItCM 0.1% 0:28.73 2 81 226 3.20M 13.3M 20.0M 384M
256 AppleSpell 0.0% 0:00.51 1 32 34 764K 1.57M 1.93M 37.4M
224 check_afp 0.0% 0:00.00 2 26 22 216K 564K 776K 27.1M
208 nmbd 0.0% 0:02.64 1 14 24 268K 812K 1.10M 27.8M
206 slpd 0.0% 0:00.42 6 31 33 252K 692K 984K 30.2M
199 mds 0.0% 0:08.67 8 96 96 4.00M 1.67M 4.79M 44.6M
191 AppleFileS 0.0% 0:01.14 2 40 43 2.93M 1.09M 3.21M 34.0M
177 Mbox2CS 0.0% 0:00.05 2 27 27 304K 576K 1.04M 27.7M

Posted: Thu Oct 26, 2006 4:49 am
by deckard97
Hi Boris,

do you need further information? I'd like to get some follow up on this problem.
Thanks

Posted: Tue Oct 31, 2006 3:23 pm
by boris
Sorry,

Hum your problem seems very strange, we can continue our discution in french on the support ?

support [AT] garagecube.com

Posted: Mon Nov 06, 2006 10:39 pm
by yves@garagecube
Please could you try Modul8 2.5 beta 8 and let me know if it helps. This version has a new mechanism to prevent movies to be paged out by virtual memory.

Yves.

Fixed

Posted: Thu Feb 08, 2007 6:19 pm
by deckard97
With V2.5 this issue appears to be fixed.
Thanks