Apple Aperture 3 is here!!!

Lars Daniel wrote in post #9606353
Can anybody confirm that A3 takes advantage of the hi-perf GPU of a Macbook Pro? Normally I have my MBP on the "small" GPU because I don´t have any real use for it, and I hate the fan noise. But perhaps A3 needs the "big" GPU?

Ap3 uses Grand Central and will use the 9600 cores if you enable it. It also runs with the 9400, too.

Jesus Christ this software is terrible. It keeps crashing when I try to edit some keywords, and now the software won't even open.

Have you repaired disk permissions lately?

mrkgoo wrote in post #9608287
Jesus Christ this software is terrible. It keeps crashing when I try to edit some keywords, and now the software won't even open.

Do you have any plugins that load when A3 starts, might want to try removing them.

Also what do the crash logs say. This may help work out why things are not working for you.

OK, I officially wish that I hadn't bothered to upgrade to Aperture 3. It has NOTHING to do with speed issues. In fact, I think Aperture 3 feels significantly snappier than Aperture 2. No, it's because some freakin' IDIOT at Apple decided to change the way import works!

Ever since Aperture 2 was released, I've been organizing my files on my Photo Drive the way that *I* want them organized. That means I create a folder/subfolder system that makes sense to me. I do it manually by physically drag copying the files from the CF cards directly to the appropriate subfolder (using my specific dating/naming convention) on the drive. Only after all of the photos are ALREADY on my Photo Drive, do I then import them into Aperture. Within Aperture's Inspector/Library file system arrangement, I already have my hierarchical system of project names created. Those project names exactly match the name of each top folder that corresponds to it on the Photo Drive. But those project names are by YEAR. So, when I import a subfolder full of photos, I am importing them into the YEAR project ("Photos 2009", "Photos 2010", etc.). The subfolders on the photo drive are each date and event.

So, what I did with Aperture 2 was highlight the appropriate project YEAR, and then choose "Import/Folders as Projects". Under Aperture 2, that automatically created an album (subfolder) within that year project that was named exactly the same as the subfolders on my Photo Drive. In other words, it was EASY to duplicate the exact hierarchical file organization within Aperture's Inspector to match how they were arranged on my Photo Drive.

Now, with Aperture 3, attempting to do the exact same import function (Import/Folders as Projects) results in a NEW FREAKIN' PROJECT being created for each folder.

I realize that's what the name of the command says it will do. But that's what it's been named for years and it worked the way I wanted it to before. With Aperture 2, if you didn't already highlight an existing project, THEN it would Import folders as NEW projects. But as long as you highlighted an already existing project name, it simply imported the folders as albums.

WHY ON EARTH DID THEY CHANGE THIS?!?!?!?

The pisser is that I can't figure out a way around it short of MANUALLY creating a new Album name to match each subfolder name and then simply importing the photos only into that Album. Extra and unnecessary work!

I've never heard of anyone complaining about the way it worked before so WHY "fix" it?



Mark

I have a question about the embedded jpeg that you see on the back of the camera when you take a RAW photo. I assume that JPEG uses the picture styles settings set on the camera, but of course the RAW is, well, raw. Anyway, when imported into Aperture 3, I notice that it 'processes' the embedded JPEGs. So does it show that jpeg in the browser? Otherwise, what is it processing?

So far pretty happy with AP3, I like the brushes, it handles the 7d RAW files nicely.

Why on the export to Flickr do they not have an add watermark feature? Am I missing something?

And to that end, why didn't they add a watermark tool like Lightroom 3....?

This is really different to work with and I can't really tell if it's slower rendering development module stuff or not but I'm seeing some pretty amazing sharpening things happening when working with eyes in a portrait and other things, at first seeming a lot more pleasing to look at than what I'd gotten out of Lightroom but still have a lot to lear with this program. The skin softening tool is very nice and and edge detection while sharpening and lightening the teeth blends and edges wonderfully, there's some powerful stuff. So far when sharpening, I'm not noticing as much weirdness when you would normally do it too much.

My first impression was not too good but found the slowness I was getting when moving around in 100% crop by dragging was causing it instead of moving the little crop box in the side window which is immediate. I just need to learn the program.

Is there any sort of hotkey to jump to a brush and not the global adjustment? I'm getting really annoyed having to press the brush icon to clone, for example, instead of just pressing "X" and having the brush pop up every time.

toxic wrote in post #9612091
Is there any sort of hotkey to jump to a brush and not the global adjustment? I'm getting really annoyed having to press the brush icon to clone, for example, instead of just pressing "X" and having the brush pop up every time.

I think all the shortcuts are the same as they were in A2. The Retouch brush opens when I press "X".

Ctrl+H still opens Highlights & Shadows, but it does go to the global adjustment. I would still have to click the gear icon to selectively brush them in.

Anyone else noticing that Aperture 3 defaults to processing RAW files just a bit darker than Aperture 2? I'm sure seeing it. But I'm not sure it's a bad thing because, with Aperture 2, my prints were usually a tad bit darker than my display. (Yes, I calibrate both my display and my printer.) Prints being slightly darker has been an "issue" since Snow Leopard. I haven't printed anything yet with Aperture 3 but I wonder if I'll get a closer match to the display now.

Mark

billybookcase wrote in post #9606166
I feel your pain, i'm running a CoreDuo MBP and it does the rendering whenever I move the loupe, this is uncharacteristic of AP2

mjm80 wrote in post #9606258
I have a similar problem with adjustments. There is a delay while processing which is really annoying. Don't think I'll be rushing to upgrade until I see LR3.

In addition to the slow loop I found another issue. When I open a prior 2.1.4 library in Aperture 2.1 (I have both programs on my machine) I can no longer export master files in any form. I can export a version but not a master. I'm assuming the Aperture 3.0 trial has a bug in it locking the masters in my 2.1 libraries, as all my libraries have icons like the Ap3 library regardless of version. If I import a project from 2.1.4 into 3.0 I can export a master then.

I'm likely just going to switch full song to 3.0 and deal with the issues until patches come out because I don't want to bother figuring out how to uninstall the demo and get my Aperture 2.1 program running like normal again - as I assume it won't.

I'll just learn to deal with the loop slowness for now. It's not like Apple will be going back to 2.1 again so I might as well stay current. I have no intention of switching to LR and learning that program. My apologies to anyone that really loves the program, I just have no desire to relearn a new workflow app.

Loupe.

It's frustrating being zoomed in and trying to move around the picture. Are people with new macs havng this slowness issue?

Mossman6 wrote in post #9613756
It's frustrating being zoomed in and trying to move around the picture. Are people with new macs havng this slowness issue?

What is your computer?