garageCube

[deepvisual]

OK I finally made some progress with this...

I installed SMC fan control which made a big difference.
I also updated OsX and QT to the latest versions.

usually there is no crash report as the whole system locks up.
last night I only had one problem - M8 began to stutter playing back only 4 clips then quit without crashing the OS.

I'll try and dig out a crash log - but I suspect it is a different problem.

It looks to me like the MBPs can overheat when playing back

[gnoma]

I believe that and proven everything already. restarting the preferences by defect it does not work either.
I have the activity monitor and see that it does not release the memory. it continues loading and when it arrives at it limits is closed unexpectedly.
It seems that it has installed Windows.
I'm desperate.

please, sorry for my babelfish translation.

[david]

Hello gnoma,

I believe that and proven everything already. restarting the preferences by defect it does not work either.
I have the activity monitor and see that it does not release the memory. it continues loading and when it arrives at it limits is closed unexpectedly.
It seems that it has installed Windows.

Which kind of media are you loading (Images and/or video, width, height, length) ? With which settings (direct to disk, ram preload, ram preload uncompressed)?

We also have found that media with a width not multiple of 4 could cause a memory hog with some OpenGL drivers.

David.

[gnoma]

my old loops are 320x240. The new ones to 480x360, 512x384 or 768x576.
Everything in JPG or Animation codec, 25FPS.

At this moment I have installed one matrox dualhead2Go to the internal NVIDIA GeForce 8800 GT 512mb, to have a dual screen on my mac pro.

[gnoma]

Can be the additional pairs of 2x 2gb of ram memory?

[david]

my old loops are 320x240. The new ones to 480x360, 512x384 or 768x576.
Everything in JPG or Animation codec, 25FPS.

At this moment I have installed one matrox dualhead2Go to the internal NVIDIA GeForce 8800 GT 512mb, to have a dual screen on my mac pro.

768 could cause the memory used to double and cause memory crash.

In the activity monitor looks at the virtual memory used by Modul8 when loading/playing 768x576 movies.

Trying changing the settings on your movies from ram full preload to ram preload. Trying lowering the "start releasing medias when Modul8 uses more than %..."

David.

[david]

Can be the additional pairs of 2x 2gb of ram memory?

First when running Modul8, use the activity monitor to look how much virtual memory is used by Modul8. If it goes to close to 4Gb, Modul8 could crash, you should then change the settins for the movies using too much memory.

If they are ECC, you could look in the system information if there is error correction occuring.

If not, you could start your mac with the startup disc and start the hardware diagnostic (D key pressed).

David.

[gnoma]

all this already is checked without no positive result. I have lowered to the minimum the preferences of pre load of memory in modul8 and continues crashing. I believe that I am going to lower all the resolutions 512x384. it seems to me a good resolution. thank you very much by you aid. itself trying it.

all this already is checked without no positive result. I have lowered to the minimum the preferences of pre load of memory in modul8 and continues crashing.



I believe that I am going to lower all the resolutions 512x384. it seems to me a good resolution. thank you very much by you aid. itself trying it.

[deepvisual]

all my content is 720 x 576 AIC or photojpeg

it worked fine before I installed 10.5

[sprung]

I have the same problem as well and sent a few emails to the support team.

- It happens that Modul8 freezes or crashes during a logical record
- During a performance, Modul8 kind of overflows his buffer or something like that and it slows down the application.
- Sometimes, Modul8 freezes and I try to quit the application but the Filter module remains. Right after the colored spinning wheel of OSX starts to run; I have to force the quit

I doubt that the problem is the hardware, since I performed with 2 other guys for a 7 week residency and all of us had the same problem.

Maybe part of the problem is OS X 10.5.4 ?

Here's my configuration:

Hardware Overview:

Model Name: MacBook Pro
Model Identifier: MacBookPro3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: MBP31.0070.B07
SMC Version: 1.16f8

G-RAID firewire 800
Edirol Evolution midi controller
Quicktime Pro 7.4.2
Photo JPEG codec 80% compression
720x540 frame size

I made some tests on my desktop machine; a MacPro 2.8GHZ 8 cores w/8GB ram W/ Gforce 8800 GT 512mb ram video card running the clips on a RAID 0 and it doesn't change anything; crash, freeze and the frame rate slows down while the performance goes on.

In the past, for 1 year running Modul8 v2 on a PowerBook G4, I never had a single crash...

I'm confident these problems will be solved or at least stabilized really soon. This application has a lot of potential.

[gnoma]

It is exactly what it happens to me. it fails in my Powerbook and the Mac Pro. for that reason I discard hardware: memory, etc.

I Work with Modul8 from the V1 and I have never had problems.
It will be imcompatibilidad with Leopard or something similar.
Only that I have work and I have to look for another Software immediately! I cannot work with this mystery.
Modul8 is great but...

[deepvisual]

so..
My MBP is just used for performances.
Should I spend a day nuking the hard drive and re- installing OSX 10.4 which works great, or should I just wait until this OSX 10.5 problem is sorted out?

[gnoma]

Hello David,
I have detected that still closing Modul8 the memory is not released.
it can be the source of the problem?
Modul8 is closed, but the memory follows in use.
see the activity monitor. it only happens with Modul8.

[ilan]

Thank you gnomo. All very valuable details. At the moment David is away for the coming week. We are definitely aware of this problem as we have received two instances of this problem and we'll get David working on a solution once he returns.

Thank you again for the feedback and you patience.

Best,

[gnoma]

thank you very much