5.2 does have bugs after all... Not good. I only found this now since I've rarely used GB since my MBP was replaced. Apple better fix this with a 5.3 update...
I attempted to use Garageband and found that it takes a long, long time to open up, even when there aren't any files in the GB folder. Sometimes you have to force quit to get the icon to stop bouncing in the dock, but if you are patient, it loads after a minute or two... I don't think this is normal. It gives you the "initializing" window during this time, and the Finder reports that it isn't responding as well. But it does load. Any known cause for this? Repairing permissions didn't help anything...
I know my Mac has shown my those "ACL found..." lines in Disk Utility, but I doubt that they could conflict with GB. Still, it's a possibility ;). I plan on wiping out one of my externals though, so I could archive and install to see what happens in addition to that, but that might not do any good. Nothing wrong with cleaning out everything though.
At least other people seem to be experiencing this as well, shown by that link I posted I believe.
my point is it refuses to respond during this time. It used to be able to load quickly in the usual 20 seconds, but since the 5.2 update, it now takes longer. I think there are too many old bulls that are walking around for this to be a mere coincidence. It will be fixed sooner or later, I hope.
I have a FireWire iSight camera, but I've never plugged it into this Mac.
Hmm... this is odd. I just got GB to open, and under the Audio/MIDI tab, the audio input and output tabs were set to "System Setting". I have just switched them to built-in output and built-in microphone... and no luck. It still does not respond and takes awhile to load. This is unusual. It works when it finally manages to load, but for some reason, it takes much longer to open than it should and used to.
What kind of things should I look for that could be conflicting with it?
about this. One of them is at: http://discussions.apple.com/thread.jspa?threadID=1391586&tstart=0
I'm thinking that there is a file somewhere that interferes with GB's initialization process. Either that, or it searches the whole hard drive for the file that was last opened... I doubt that, but it wouldn't surprise me if that was the case.
So that implies that there is something bothering Garageband and not the user files, I guess. I was planning on making some podcasts but this hinders my ability to do so...
I haven't been using any audio peripherals with this Mac. Some people who do claim to have found a solution, but they have used some type of speakers or external mics, etc
The only third-party software that I use is the Office 2008 suite... I do have Webkit along with its debug app, Paintbrush, and Firefox, yet they shouldn't have an affect on any of it...
Garageband is an important app for some of us, and an important app for Apple's lineup. When they release an update, it shouldn't break anything that was already working... Hopefully they can release a fix for it soon as I could really use it.
I also found that I can't load applications off of my external drives anymore... I've done that before, but now I get error codes instead.
I hope they are working on it, but who knows? There are some discussions on Apple's support site regarding this. BTW, I tried plugging in my FireWire iSight and it did make it work slower when GB managed to load, but creating and fixing the problem solved nothing.
It seems that for me, GB takes at least 30 seconds to load when it loads "quickly", and sometimes even longer... Loading a project or not does not affect it... Come on Apple, I have podcasts and tracks to record!
You need to supply us with some more information. First, we need a question. Second, we need to know what version of OS X you are running, which Mac you are using, and the version of GarageBand '08 that you have. Only with more details can we diagnose where the problem with Magic GB is.
Help, my PC with Windows 10 won't shut down properly
Since upgrading to Windows 10 my computer won't shut down properly. I use the menu button shutdown and the screen goes blank, but the system does not fully shut down. The only way to get it to shut down is to hold the physical power button down till it shuts down. Any suggestions?