Full Version: the spinning ball of death
I don't get it. I gave up on 1.5 because of the spinning ball of death. I have now downloaded the new version. Its no better. Who the hell can make use of it? I am running on 2.66GHz dual core w 4G ram w the 7300GT graphic card. My test library has about 4k 1dsII raw images. It started out nicely and smoothly but now every adjustment every zoom requires 10-60s. Installed latest Prokit, turned off preview generation. Anyone knows what gives? As it is, its unusable so it must be the case that not everyone experiencing it.
QUOTE (yoni @ Jun 29 2008, 04:32 PM)
I don't get it. I gave up on 1.5 because of the spinning ball of death. I have now downloaded the new version. Its no better. Who the hell can make use of it? I am running on 2.66GHz dual core w 4G ram w the 7300GT graphic card. My test library has about 4k 1dsII raw images. It started out nicely and smoothly but now every adjustment every zoom requires 10-60s. Installed latest Prokit, turned off preview generation. Anyone knows what gives? As it is, its unusable so it must be the case that not everyone experiencing it.
I have the same computer , might not be the same monitor, I have NEC 26090 WUXi monitor and have no problems.EXCEPT I have some RAM dying trying to figure THAT out now.I run bootcamp and windows XP pro also.Other than than the RAM thing all works well.I'm NOT running PS3 on MAC just Lightroom.
QUOTE (yoni @ Jun 30 2008, 12:32 AM)
I don't get it. I gave up on 1.5 because of the spinning ball of death. I have now downloaded the new version. Its no better. Who the hell can make use of it? I am running on 2.66GHz dual core w 4G ram w the 7300GT graphic card. My test library has about 4k 1dsII raw images. It started out nicely and smoothly but now every adjustment every zoom requires 10-60s. Installed latest Prokit, turned off preview generation. Anyone knows what gives? As it is, its unusable so it must be the case that not everyone experiencing it.
You could try to sample Aperture when it displays the spinning ball of death. It might give you an idea of what's happening and/or you could send a bug report to Apple.
QUOTE (francois @ Jun 30 2008, 11:15 AM)
You could try to sample Aperture when it displays the spinning ball of death. It might give you an idea of what's happening and/or you could send a bug report to Apple.
You mean monitor activity? It says Aperture not responding.
got 30" apple display. Sent bug reports on 1.5 regarding it. Clearly they didn't fix it.
QUOTE (yoni @ Jun 29 2008, 06:32 PM)
I don't get it. I gave up on 1.5 because of the spinning ball of death. I have now downloaded the new version. Its no better. Who the hell can make use of it? I am running on 2.66GHz dual core w 4G ram w the 7300GT graphic card. My test library has about 4k 1dsII raw images. It started out nicely and smoothly but now every adjustment every zoom requires 10-60s. Installed latest Prokit, turned off preview generation. Anyone knows what gives? As it is, its unusable so it must be the case that not everyone experiencing it.
Can you give some more details. System 10.4, 10.5?, Other programs running? I run 2.01 on a G5 dual 2 Ghz, 3 gig RAM and while only doing D20 size images, have noticed no particular slowness. Runs on my MacBook Pro 2.16 Ghz too without problems.
Dave
QUOTE (yoni @ Jun 30 2008, 12:28 PM)
You mean monitor activity? It says Aperture not responding.
Select the Aperture process in Activity Monitor and click the Sample Process in the toolbar (or menu View>Sample Process). This should generate a report of Aperture, even if it's not responding.
Thanks, but cant really decipher whats it doing from the activity monitor sample process. I give up. On two machined 10.5 and 10.4, and UI is jerky with ball of death appearing regularly. Not sure why, but unacceptable performance. thanks everyone for your help.
Well I found a helpful guide: http://www.bagelturf.com/files/b84395d029b...2ede1e-1061.php
Solution to my problem: delete the preference file. Simple enough.
Solution to my problem: delete the preference file. Simple enough.
QUOTE (yoni @ Jul 4 2008, 03:23 AM)
Well I found a helpful guide: http://www.bagelturf.com/files/b84395d029b...2ede1e-1061.php
Solution to my problem: delete the preference file. Simple enough.
Solution to my problem: delete the preference file. Simple enough.
Glad to see that you managed to get rid of the SBoD in an easy way
Yes, sample dumps are not easy to decipher but they could have told ou where Aperture was spending time.
Anyway, have a good day!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.