my guess - aperture 2.0 coming out soon.

Reply

core animation will help make aperture a next gen app.

Reply

Nik -

Two quick notes - it's spelled "existence," not "existance." Also, whenever I'm reading through TUAW posts and hit "whilst" in one, I always know that you wrote the post - just a funny British-ism that gives you away every time.

Reply

I ended up backing up Aperture to another drive then removing it for now.

Reply

Is it confirmed that this is an issue with 1.5.6? The Apple page doesn't say, and I think 1.5.6 was released the same day. It's possible they just haven't updated their page yet. OTOH, I'm not going to risk it...

Reply

Thanks for this post! I just mounted the Aperture disk image in Leopard and was about to install when I read this. I'll hold off until Apple comes up with a fix!

Reply

err couldnt you just stick the aperture liberary in a seperate folder and exclude that folder from time machine backups? I think that should work

Reply

I'm pretty sure this will effect all versions of Aperture. I think the issue is the the user will be writing to the files while Time Machine is backing them up. Because Aperture is nearly always doing some kind of file writing it could be a problem. I think a simple Time Machine update should fix it. All they need to add is a check like if Aperture is not running proceed. If aperture is running stop and ask for user input. - That seems like a simple solution.

Reply

I'm pretty sure this will effect all versions of Aperture. I think the issue is the the user will be writing to the files while Time Machine is backing them up. Because Aperture is nearly always doing some kind of file writing it could be a problem. I think a simple Time Machine update should fix it. All they need to add is a check like if Aperture is not running proceed. If aperture is running stop and ask for user input. - That seems like a simple solution.

Reply

Well, this just SUCKS! I'd expect better integration with Apple products and its key OS services.

Reply

I'll be delaying my upgrade to Leopard. Aperture is just too important to me.

IMO it would be better if Aperture could disable Time Machine when its running then restart the service when the end user quits Aperture. That would at least be a decent short term solution.

Reply

why not write an applescript that:
1) turns off automatic backups
2) launches aperture
3) waits for aperture to close
4) re-enables automatic backups

Reply

Couldn't you just unplug your backup external hard drive (which would prevent Time Machine from doing a backup) when you want to run Aperture? Then, when you're done in Aperture, plug back in.

Reply

Too bad the support article is so low on details.

I already have my Aperture library excluded in Time Machine, as I just use the built-in vault functionality to do backups. But I have no idea if this will save the library from corruption. Is it Time Machine backing up the Aperture library that causes problems? Or is it more generally Time Machine running file system operations at the same time as Aperture?

Reply

Hi... I also noted that if you have Aperture open in one space and then switch to the next, once you come back to the previous space the HUD display is shown in a weird way (i.e. even if you were not in full screen mode). Apple better fix Aperure soon enough or else I might not be interested in using the software. (too bad I paid hard cash for it!!).

Apple better fix it soon!

(please tell me I am not the only one experiencing this weird bug. Timemachine is not active (drive is disconnected) and I did a clean install of Leopard (all updates have been made)). The only thing might be that Aperture is currently processing previews (had to reimport everything)....

Reply

To me this post reads,

"Time machine screws up backup and restore of open files."

If it can't back up Apeture, what other programs is it going to completely stuff up?

Reply