Aperture 1.5.2 Update is now available

[JosephSchorr]

This was just posted today. This free update addresses a number of issues related to contact sheet printing, watermarks, Smart Albums, and other items. It's free to any registered Aperture users.

Available through standard Software Update, or can be downloaded from http://www.apple.com/aperture/download/

Joe Schorr
Sr. Product Manager, Aperture
Apple

 

[Johanfoto]

I hope the following bug is also fixed: If you have lost the reference to an external file, and the file was edited after it was created and changed considerably in that edit (for example because you lowered the depth from 16 bits to 8 bits), Aperture doesn't understand it's still the same file and refuses to reconnect it (the button stays dimmed). And there seems to be no way to force Aperture to reconnect a file it thinks is not the correct one.
--
Johan
http://www.johanfoto.com

 

[allanimal]

I have already submitted a bug via the feedback page, but GPS metadata is not exported. This is a serious flaw, IMHO. This can't be that difficult - please retain ALL metadata on export, at least when the "retain metadata" checkbox is used in the export presets.

 

[Najinsky]

Seems faster displaying projects too.

-Najinsky

 

[Chris_B1]

What happens to the older updates? Are those files safe to delete?

 

[Alpha Doug]

This is in response to Johanphoto. If I understand it correctly, you had lost the reference to an outboard file, perhaps because you moved it. Then after moving it you edited fairly severely in an outboard editor, then you tried to reconnect to that file from Aperture.

If this is correct, this is not a bug. This is an unreasonable expectation to expect Aperture to reconnect to a file that truly is no longer the file it had referenced. The program has to make absolutely sure that the referenced file is indeed the file that you originally referenced. More than just the name is considered, since you might have applied the same name to two different files. I'm not sure exactly how the program does it, perhaps it compares EXIF information, or does a check sum, but if those don't match, it will not reconnect.

This points out one of the reasons for not using outboard referenced files, and one of the best reasons for importing you original images into the Aperture managed database. A lot of the folks who were paranoid about allowing Aperture to manage their files pounded Apple to provide this capability, and they did. But you have to take some time to understand the ramifications, which not many of the folks who lobbied for this did. Anytime you move, edit, or otherwise change an outboard referenced image, you risk the loss of the link in Aperture. The same thing happens in LightRoom.

I have become very comfortable with allowing Aperture to manage all my files. It requires me to work up a sane back up schedule, and offload images when the library or Vault get too big, but the ease of workflow more than makes up for it.

--
Only my opinion. It's worth what you paid for it. Your mileage may vary! ;-}

 

[leicaman]

No question... faster all around after the update. The are continuing to fine-tune and fix.

 

[Johanfoto]

This is in response to Johanphoto. If I understand it correctly,
you had lost the reference to an outboard file, perhaps because you
moved it. Then after moving it you edited fairly severely in an
outboard editor, then you tried to reconnect to that file from
Aperture.

No, you do not understand it correctly. The file was editted BEFORE it was moved, but Aperture apparently gets its information about the file at the moment it was CREATED (or first referenced), and doesn't update that information afterwards. So if the file was 96MB at the moment it was created, and it is 48MB now (because it's now 8 bits), Aperture still thinks it is 96MB and doesn't recognise it if it needs to be reconnected. Yes, the file was moved to another (bigger) disk. That was the reason it needed to be reconnected. But is wasn't altered after it was moved.

If this is correct, this is not a bug.

It's not correct, and in my opinion it's a bug that Aperture doesn't update its information about a file after you've edited it in the external editor. I used Aperture to create the file and send the file to the external editor, so it would only be logical if Aperture checked what I did and updated its information. Apparently it doesn't, because it thought the file was still 16 bits.

This is an unreasonable
expectation to expect Aperture to reconnect to a file that truly is
no longer the file it had referenced. The program has to make
absolutely sure that the referenced file is indeed the file that
you originally referenced. More than just the name is considered,
since you might have applied the same name to two different files.
I'm not sure exactly how the program does it, perhaps it compares
EXIF information, or does a check sum, but if those don't match, it
will not reconnect.

The EXIF information is still the same. The file name is still the same. The path on the disk is the same. The name of the new disk is the same as the name of the old disk was. The only difference is the file size, but that happened BEFORE the file lost its connection. As long as the file isn't moved, Aperture has no problem finding it, even though the file size changed size. Only if the file is moved and should be reconnected, Aperture suddenly doesn't understand it's the same file. An intelligent program would realize that it is possibly the same file, and in doubt would ask me. Aperture isn't that intelligent.

Anyway, it still wouldn't be a problem if I could manually force a reconnect, but unfortunately that seems impossible. And that's all I ask.

--
Johan
http://www.johanfoto.com

 

[Najinsky]

No question... faster all around after the update.

When I first installed the update, Aperture was so much faster at loading projects it didn't seem feasible (almost instant for most projects I clicked). So I re-booted and unfortunatley I was right. After the reboot, there is still noticeable and welcome improvement to the loading speed, but not the turbo-nutter-speed-explosion I initially encountered post update.

However, now I'm intreagued where the false speed boost came from. I'm suspecting possibly the SQL database got fully loaded into RAM during the update and was therefore cached, and perhaps the image previews were cached in RAM too as I was generating a bunch of previews just before installing the update. Whatever the cause, I sure wish I could bottle it.

-Najinsky

 

[Najinsky]

I'm not aware what happens to them. I use software update and never see where the downloads go, I've always assumed they get deleted. I assumed this because I once saw a thread about downloading the updates manually so they could be applied to multiple machines (and that presumably wouldn't be necessary if software update kept the downloads).

-Najinsky

 

[leicaman]

Their competition with Adobe LR is going to be intense. I think you will see more and more updates and fixes as time goes on.

 

[Rotlex]

Their competition with Adobe LR is going to be intense. I think
you will see more and more updates and fixes as time goes on.

Let's hope! I'm loving these past two improvements\updates! Competition can only be a VERY good thing!
--
Steve
http://web.mac.com/rotlex

 

[refsvik]

Yes, I agree. The failure to export a full set of metadata in versions is a fairly significant one, and I hope to see a fix too, sooner rather than later.

Best regards,

Kjell Are Refsvik
Norway

 

[Kendall Helmstetter Gelner]

Their competition with Adobe LR is going to be intense. I think
you will see more and more updates and fixes as time goes on.

Let's hope! I'm loving these past two improvements\updates!
Competition can only be a VERY good thing!

I've always said that even though I like Aperture more, Lightroom is also a fine program - so it's great to see both improving so rapidly!

I do think Aperture has a little more freedom to be more nimble though, as Lightroom has to make things work for not only OS X, but also the myriad incarnations of Windows that must be supported.

--
---> Kendall
http://InsideAperture.com
http://www.pbase.com/kgelner
http://www.pbase.com/sigmadslr/user_home

 

[Johanfoto]

I have to make a small correction to what I said earlier. It seems that this bug only manifests itself with files that were not created by Aperture, but imported as referenced files. A scanned slide for example, in TIFF format. If that is edited after it was imported into Aperture library as referenced file, and consequently the connection gets lost (for example because you move all your files to a bigger disk), you cannot reconnect it because Apertrue thinks it's a different file. Here's how you can check this yoursef:

1. Create a new file in Photoshop, 16 bits, and save as TIFF with no copmpression
2. Open Aperture and import this file as referenced file in the library
3. Keep Aperture open!
4. Edit the TIFF in Photoshop to make it 8 bits and save with LZW compression

5. Look at Aperture. You will see that the thumbnail is updated, so Aperture does know the file was edited!
6. Close Aperture
7. Move the file to another disk
8. Open Aperture again. It will show that the file is not connected

9. Try to reconnect the file using the 'Manage Referenced Files' option. You will see that the 'Reconnect' button stays dimmed, because Aperture fails to understand this is the same file. You will also see that Aperture shows the file size of the uneditted file in the information of what's referenced, so that information is different from the real file size (after editting).

10. Unfortunately, you have no way to force Aperture to accept it for reconnection.

--
Johan
http://www.johanfoto.com