Jump to content

Aperture 3 and M9


Recommended Posts

Advertisement (gone after registration)

do plugins like Silver Efex and Viveza 2 have to be reinstalled, or are they picked up automatically by Aperture 3?

 

The plugins are picked up automatically. Almost none of the plugins have been updated to 64-bit yet, meaning you have to use Aperture in 32-bit to use the plugins. Works well.

 

By the way, as another poster was mentioning noise control, I use the NoiseNinja plugin for noise reduction and it works perfect.

Link to post
Share on other sites

Guest malland
...The Aperture version looks more detailed. The Lightroom has a more digital look to it...
I've started using Capture One v5 to develop Ricoh GXR/A12 files, for which someone has made an excellent profile, because Aperture 2 didn't produce good colour — I could get nowhere near the colour quality I now get with C1 — but, still, Aperture gives the best highlight recovery. However, for the M9, Aperture produced good colour, as Jono has testified.

 

—Mitch/Bangkok

Paknampran – Colour

Link to post
Share on other sites

I find A3 is quite slow importing M9 16 bit DNG's from an SD card. I am using a 13" 2.53 gHz MacBook Pro with 4GB. It takes about 2 times as long as C1 V5 Pro before all the images have proper sharp thumbnails. No crashes however. As it currently defaults to the M8 profile, I find the same issue as LR 2.x of over-saturated red channel, particularly for Caucasian skin tones. As I commented with LR, it looks as if everyone has dined well but not wisely. Jono kindly gave me his recipe which was to move the colour slider towards yellow and then reduce the red saturation by around 8% and increase yellow by about the same amount. I think I will stick to C1 until a proper M9 profile arrives (A4 may well be out by then). FYI the US educational pricing is $179 for the full version.

 

Wilson

Link to post
Share on other sites

Almost none of the plugins have been updated to 64-bit yet, meaning you have to use Aperture in 32-bit to use the plugins.

Strange. LR running in 64-bit can use the 32-bit plugins just fine. The plugin concept is extremely simple anyway; essentially just using the external applications to process an exported copy of the original. Shame to have to restart Aperture for that.

 

Better plugin integration is one of my big wishes for both Aperture and LR and I know I am not alone. This shouldn't take years to realise.

Link to post
Share on other sites

 

Jono, thanks for taking the time to wrote out the laborious procedure. Are you making the same basic adjustments in Aperture to M9 files that you've described elsewhere for Aperure 2 (pulling back on Boost and adjustment to reds)?

 

—Mitch/Bangkok

Flickr: Mitch Alland's Photostream

 

Hi Mitch

Thanks for your email - more later when I've done some work!

 

And yes - I'm using the same adjustments in A3 as in A2 for the M9 with similar results.

Link to post
Share on other sites

Moved all from LR 2.6 to Aperture 3 last night. Works flawlessly on my iMac 24". Fast, smooth, precise, fun.

 

Balivernes,

 

If I may ask, how did you move your LR library? Did you export it first with sidecars? I have to go through the same, and would appreciate knowing your procedure and process.

I am using LR 2.6.1 and just acquired A3.

 

thanks,

 

Jim

 

http://www.jimtrunck.com

Link to post
Share on other sites

I started playing with Aperture 3.0 this morning (previously used C1 and LR). So far, I must say I'm impressed. A couple questions:

 

- Why don't they provide ability to control curves?

- I can't seem to figure out what it means to designate either the RAW or the JPEG as the master. Can anyone explain what that is all about?

 

Many thanks.

Link to post
Share on other sites

With Aperture 2 when you imported a Raw and Jpg of the same file only one image appeared in the browser. You could however create a new version from Master (raw) or a new version from the hidden Jpg. With Aperture 3 you have the option to import both and view both at the same time in the browser. From my understanding should you wish to import both a raw and Jpg of the same file into Aperture you can have it 3 ways,

 

Raw as master imports both files, but shows the raw file only, create new version form master creates a new version from the raw file or you have the option to change the master to the hidden Jpeg which then becomes the master image from which versions are created.

 

Jpeg as Master is the reverse of above.

 

Both as master brings in both files and shows both files as individual files in the browser, you can then work with either and create new version from master will create a new version of which ever file was selected.

Link to post
Share on other sites

For those having issues with A3 - in particular importing A2 libraries - you are not alone. See this article in Softpaedia Aperture 3.0 Deemed a Scandalous Release, Full of Bugs (Unconfirmed) - Yet many seem to overlook the extensive set of Support documents aiming to make the upgrade a seamless process - Softpedia .

 

Wilson

Link to post
Share on other sites

I started playing with Aperture 3.0 this morning (previously used C1 and LR). So far, I must say I'm impressed. A couple questions:

 

- Why don't they provide ability to control curves?

- I can't seem to figure out what it means to designate either the RAW or the JPEG as the master. Can anyone explain what that is all about?

 

Many thanks.

 

With Aperture 3, you can control curves. In the adjustment TAB, scroll down and select curve.

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

Link to post
Share on other sites

Guest joewehry

Running Aperture 3 with 2 GB ram on MacBook Pro 2.26 works fine for me.

 

When I first imported images, it was painfully slow, but launching the Show Activity from the Window menu indicated it was updating thousands of preview files. Even though I would quit the process (at which point performance was flawless) every time I relaunched Aperture 3 it would dutifully start rebuilding the preview database.

 

Once that process was done, I've had no problems with Aperture. I did install it as a clean install, not an upgrade, so not sure if that had a problem. That is, I reimported all raw files, not the previous Aperture library.

 

Please note: OS X wants approx 15% of your hard drive free to use for its own processes. So if you have a 60 GB Drive, for example, OS X will work optimally with about 9 GB FREE hard drive space. That's not free space to add photos, that's just free space. Period.

 

Also I prefer to have Aperture create its own preview file rather than use the imbeded JPEG (under Aperture prefs.) At least for me it seemed a little snappier.

 

Finally, someone told me that iTunes can be a processor hog, and running it in the background can have an effect. Not sure if that is true, but passing it along to test on your machine.

 

Finally, you can always launch Activity Monitor from the utitlities folder and see how your ram, processor, hard drive usage is being allocated and make upgrade decisions from there for either more ram or larger hard drive.

Link to post
Share on other sites

[quote name=joewehry;1238357}

 

Please note: OS X wants approx 15% of your hard drive free to use for its own processes. So if you have a 60 GB Drive' date=' for example, OS X will work optimally with about 9 GB FREE hard drive space. That's not free space to add photos, that's just free space. Period.

[/quote]

 

I know that is what some experts say but I feel it is much too simplistic a calculation. For example, the system hard disc in my Powermac is 1.5TB. I cannot really believe it is necessary to leave 225 GB free.

 

Wilson

Link to post
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...