Hard Disk Full
Apr 7, 2006 at 6:18pm
Hard Disk Full
Hi – just re-posting this from previous post as it is a seperate question and nothing to do with previous post.
When running this patch for more than 20 minutes, the patch uses up all my hard drive space (about 2.5. gb free)
Since i’m not writing to disk, this shouldn’t happen – right?
Do i need to clear the kill the grab object after every loop or something?
Any advise would be great
Apr 7, 2006 at 6:32pm
400 * (320 * 240 * 4 * 8bytes) / 1024 = 960000K / 1024 = 937.5MB
How much RAM do you have installed on your system? I am pretty certain
Apr 7, 2006 at 7:01pm
Note that you are using quite a bit of ram in this patch and If
320 x 240 x 4 x 200 x 2=122,880,000bytes == ~122MB
If you were to change the matrixset sizes to be something like 2000,
Btw, int->[prepend index]->[prepend set]->message box, is probably
Apr 7, 2006 at 7:16pm
I’m using a powebook G4 with 1gb of RAM and was still gettng the problem when using a matrixset size of 100.
If i supply more hard drive space will it stop the problem, or will it just continue to take whatever space i give it?
It’s for an installation which is to run for about 2 days.
Apr 7, 2006 at 7:58pm
Then it sounds like a memory leak either in Jitter or the video
Also, it would help us out If you could also take some time to
- Does it happen when you replace jit.qt.grab with jit.qt.movie?
- If you’re running OS X, and you run process viewer or “top” from
- If you remove the jit.matrixset portion of your patch (just use a
- Is any other patch open or are any other applications on the system
Apr 8, 2006 at 12:05pm
2. Same original setup reading from a qt.movie into matrixset with dimmap and fade (of about 100 MB) – same issue
3. Matrixset objects replaced with single matrix object (everything else the same including fade and dimmap etc..) Same issue – if anything this take the RAM faster than any other tests so far
4. Same original setup without the Fade – Same issue
5. Same original setup without the DIMMAP – No problem
The exact issue is that MAX is taking approx. 2mb of RAM for every second that the patch is run – i’ve also briefly tested this on my iMac G5 (which is too big too use for the show) and am getting the same problem – although i haven’t tested this as much as with my powerbook set-up (i should get to this today)
I’ll play around with alternatives to the dimmap object and will post any further results.
Thanks everyone for being so helpful, i only started using Jitter last Monday and it’s a real delight to fins such a helpful community here – hopefully i can return the favor in the future as i learn the software further
Apr 8, 2006 at 12:24pm
Ok Update: I went through the same debugging steps on my iMac G5 with exactly the same result so i’ve now swapped the ‘jit.dimmap @invert 1 0′ object for a ‘jit.mxform2d @offset_x -320 @boundmode 4′ object and everything is running steady
Hopefully this will help anyone who hits the same problem
******fixed patch – but not completed with desired efect yet***
You must be logged in to reply to this topic.