Aperture 1.1 & RAW

Currently I'm not using Aperture 1.1, or 1.0 or at all.
I don't want to spend an extra £350GBP to receive £130 Apple Credits/Vouchers to purchase V1.0 to upgrade through the web to 1.1 or now 1.1.1. As I don't need to bank with Apple. This means that I have still to wait, yet another week, until the Retail Boxed Version 1.1 might be available.
So, in my anticipation I have idled my time away reading about all the problems you guys seem to be having, with what seems to be (aside from the bugs) an amazing piece of software. I wonder why Apple haven't provided all of us Intel Mac owners a key through the web and a download for the application, and send the box out when it's available?
The knock on effect of which, is that instead of purchasing this software and spending my time using it, I'm trying out Lightroom (which incidentally, is nowhere near the mark yet) and reading about all the issues Aperture is presenting, leaving me a little aprehensive about purchasing it.
A large number of posts and coments seem to revole around Aperture operating sluggishly on high spec systems. I think it would make sense for users to add additional details to their personal details, pertaining to their equipment and average RAW file sizes. Maybe include on each post rough number of images in open projects.
Surely this would help each other and anyone on the Aperture Team looking here for user issues? Or is it possible to monitor performance without all the relevant details?
Intel iMAC 20" 2.0Ghz 1gb RAM 256VRAM   Mac OS X (10.4.6)   Canon 350D, RAW - Avg 9.0mb raw files

NO NO NO. "Repair permissions" as proscriptive
medicine is pure voodoo.
This is not the time or place to really get into this...
Sorry, but directing anyone away from this is important enough that any time and place is the time to get into this! I don't know Gruber, but I do know Macs, and Gruber's advice is WRONG (more below).
If you think that Repairing Permissions might be a mistake, this MacFixIt article may enlighten:
<http://www.macfixit.com/article.php?story=20060413075624652>
I oversee 7 Mac boxes with a wide variety of apps on them including all the apps in Adobe's Premium Creative Suite, Aperture, MS Office, etc. I am absolutely convinced that religiously Repairing Permissions immediately before and after every installation leads to a long term totality of a much more stable box.
Many folks on the Adobe Photoshop Mac Forum, each of us with decades of Mac experience using notoriously difficult apps, will concur with the recommendation to Repair Permissions immediately before any installation of any kind.
Not a scientific sample, but I do note that frequently on various forums when folks are saying some OS/app combination does not work I am responding "that's funny, it works fine for me and I have the same configuration..."
IMO a side benefit is that repairing Permissions twice sort of forces one to think about the installation: Do I really need it? Is it absolutely safe? Where should it go? What else on the box may be affected by the installation? Is there something I should back up first? etc.
Another totally valid MacFixIt recommendation that Gruber falsely called bogus was:
"We recommend the following procedure when installing Mac OS X 10.4.6.: First, avoid performing any other operations (in Mac OS X or third-party applications) while the update process is occurring... Also, disconnect any FireWire/USB devices before applying Mac OS X 10.4.6, then re-connect the devices one by one after the update process is complete and the system has restarted."
Although not all FW devices succumb to a System Update many (including one of mine) have. Similarly many of us have had crashes by getting too impatient and trying to multitask during OS updating. The MacFixIt advice is sound and Gruber is again flat wrong.

Similar Messages

  • When will Aperture 3 support RAW processing for the Canon 5D III?

    When will Aperture 3 support RAW processing for the new Canon 5D III?

    We are no phophets and also do not work for Apple -  so we don't know.
    See this thread to join into a discussion with others who also are waiting:
    Canon 5D Mk III - RAW update?
    Regards
    Léonie

  • Does anyone know when Aperture will support RAW files from the Canon Eos 7D mkii?

    Does anyone know when Aperture will support RAW files from the Canon Eos 7D mkii?

    Only Apple knows. The never announce upcoming RAW support in advance, sorry. And if anybody knew, it would not be allowed to post this information here.

  • Why won't Aperture 2 support RAW files imported from Canon 60D when it does from my Olympus DSLR?

    Why won't Aperture 2 support RAW files imported from Canon 60D when it does from my Olympus DSLR?

    I'm afriad the fact that your Olympus dSLR is supported is no relevance.
    The Raw from every model of camera is different. Note: that's every model not every brand. So, the NEF produced by a Nikon D40 is not the same as the NEF produced by a D60, the CR2 produced by a Canon 350 is not the same as the CR2 produced by a Canon 400.
    Support for individual camera models has to be added one by one, and Apple will update the OS to work with the most recent version of the software. That's an incentive for you to keep up-to-date. So, for support for your 60D you'll need 10.6.5 plus Aperture 3 and/or iPhoto 11.
    Regards
    TD

  • Aperture imports the raw images from my new Olmpus e-p5 as .orf files and does not recognize them. What can I do?

    Is there another way to convert the .orf files that are not being recognized ?
    I used a card reader.
    The Olympus Viewer software reads the raw images just fine.
    Thanks

    I do not see your camera on the list of supported cameras, sorry.
         Apple - Aperture - Technical Specifications - RAW Support
    The Olympus Viewer software reads the raw images just fine.
    Does this program have an otion to export the photos in a different format? Then it would be the best way to convert the image files to a supported format.
    Or check, if Adobe's free DNG converter supports your camera:  Adobe - Adobe Camera Raw and DNG Converter : For Macintosh
    Aperture can import DNG files with the right settings.
    You might also simply import raw+jpeg and work with the jpegs as original files, while you are waiting for the raw support to be released.
    Regards
    Léonie

  • Where is Aperture support for raw files from Leica X Vario?

    Where is Aperture support for raw files from Leica X Vario?

    It doesn't appear to exist, at this time:
    http://www.apple.com/aperture/specs/raw.html

  • Can Aperture 3 read Raw files from Canon G1X?

    Is Aperture 3 capable of reading Raw files from a Canon G1X?
    I'm currently using an elderly version of IPhoto, having resisted upgrading because of negative feedback about the latest version. My IPhoto version cannot read the Raw files from the G1X. I also tried importing one into Picassa, but the colours looked completely wierd.
    I'm now considering buying Aperture 3 but will maybe wait until:
    a. Aperture 4 is released and;
    b. I know that Aperture can indeed read the Raw files from the G1X.
    Any help/advice gratefully received.
    Frank P

    see this list:
    Aperture 3: Wide raw support for leading cameras:
    http://www.apple.com/aperture/specs/raw.html
    Your camera is supported by Aperture 3.
    P.S. and the camera is supported by MacOS X 10.7.4.,
    see: OS X Lion: Supported digital camera RAW formats
    http://support.apple.com/kb/HT4757
    What is your MacOS version? Perhaps upgrading to 10.7.4 should make the raw support available in iPhoto too.
    Regards
    Léonie

  • Why does aperture convert my raw files to jpegs when I import them from iPhoto?

    Why does aperture convert my raw files to jpegs when I import them from iPhoto?

    It doesn't.
    When you import  Raw to iPhoto the app makes a jpeg preview of the Raw automatically. When you import from iPhoto then Aperture brings over both versions.
    Regards
    TD

  • Aperture 2 and RAW vs JPG ?

    Just downloaded the trial version and haven't done any work yet with RAW files. Previously everything was done with JPG on iPhoto. Should I now shoot RAW+JPG mode on my Canon 30D and then use Aperture for the RAW files? Is using JPG on Aperture worth my time or is RAW the only way to take my next step in photo processing?

    I personally see little reason to shoot JPEG for anything. I haven't shot a JPEG in over 3 years, because you can always generate a JPEG from a RAW file, using tools like Aperture, Bridge, or Lightroom.
    That said, see if you like the processing options before you commit to a RAW only workflow. That's what 30-day trial periods are for

  • How will Aperture treat Nikon raw images which have been enhanced using Capture NX2 software?  Some are cropped and "developed" and some have been enhanced using the control point technology.  I have NIK sw as a plug-in in aperture.

    How will Aperture treat Nikon raw images which have been enhanced using Capture NX2 software?  Some are cropped and "developed" and some have been enhanced using the control point technology.  I have NIK sw as a plug-in in aperture.

    Actually, there is a Nik/Nikon connection — but I am pretty sure it is irrelevant to the OP's question. The connection is that Capture NX2 was written as a joint venture between Nikon and Nik. (The name similarity is a coincidence.)
    Capture NX2 is a cool program that incorporates the features of Nik's Viveza and Nikon's Raw processing engine, along with some other powerful image adjustment features. It provides, like Aperture, a losses workflow. Unlike Aperture, the adjustments (Edit Steps in C-NX terminology) are saved in the original NEF file along with the un-altered raw data. Multiple versions can be saved in a single NEF.

  • How can I attribute my edits before aperture to the raw files as versions?

    Hi,
    I am in the middle of importing all my files (approx 100,000) into aperture. I have previously made edits of my best images and in some cases have several edits for one 'master' file. How can I attribute or link the edits to the master files? I have followed a simple nomenclature, where the camera raw file was say bfes1001.tif, I would name the files bfes1001e1.psd or bfes10001e1-small.jpg, bfes1001e1-epson7600.psd. So my question is really two parts, first is there a way to link my old edits to the master raw files, and secondly is there a way to import photoshop files without flattening them? I can't image throwing away all that time making masks etc. If there is no way to import a layered photoshop file then is there a way to make an association to the files if I leave them outside of Aperture (althought that seems to defeat a big part of Aperture)?
    Thanks,
    Eric

    This is not a method suited to automation, but what you can do is:
    1) Import original RAW into Aperture.
    2) Edit in external editor - it creates a new version based on PSD or TIFF (you choose in options).
    3) Kill external editor, replace created TIFF file with your new "master" tiff (or PSD). To do this just open the Aperture Library package using "Show Package Contents" in finder, do the same for the Project package held within the library, and finding the new TIFF version of your file. You could either replace the TIFF file before you return to Aperture form the editor or replace all the TIFF files with Aperture closed. The name must be identical. If you have a TIFF or PSD not in RGB mode Aperture will not like you much and probably crash whenever you go to view the picture.
    That seems the most space-efficient way to me and keeps Aperture understanding that your edited TIFFS are versions of a particular master.

  • Aperture 3 bad raw conversion with Canon files

    Hi, Aperture is converting my 6400 iso raws into images I can't work with to my satisfaction. For pleasure I shot a staged disco dance event with some fun colorful lighting. When imported into Aperture via card reader the previews look somewhat similar to the Rebel's LCD jpg rendition.
    One example, the stage light beams which are enhanced by smoke machines have one light with blue and another with magenta. When I click on that preview, the spinning wheel appears as usual saying loading which I believe is applying Aperture's interpretation algorithms. The results are stripping all the magenta and no matter what I do with the controls such as enhancement I can't get back the correct color. Remember the first loaded preview are similar to what I see in camera.
    I rarely shoot this high of iso and I'm finding adjustments with highlights to be extremely sensitive with a much lower threshold of adjustment. On most of the previews I attempted adjustment I preferred the look before Aperture converted them. Clicking "M" for master does not revert back to what I first saw before selecting it. I can't get back to that original first imported look. I can see the differences in the previews side by side, one I click on and a similar shot I didn't.
    I have never had this criticism before with this camera at 100 iso though it is recently acquired by a few months and never had this complaint with any of my NEF Nikon files. At first when beginning import the preview widow scrambled the order of the files where some images sat besides other images taken at an entirely different time. I closed everything and restarted and at first it did it again then corrected the order to which I hit the import button. I kept the images on the card and now will reload them directly onto my HD first. I'm reluctant to load into Aperture directly until I figure out what is going on.
    I did download Canon's DPP processor and it did hold onto the colors that you see with the thumbnails you see to the left of the selected image. Go figure. I have not touched any of the import settings in preferences.
    Your suggestions appreciated.
    John

    So what you're seeing initially at import is the JPEG that the camera generates as a preview for the image. All RAW files have this; the JPEG is what's used by the camera itself to give you the preview on the back of the camera.
    When Aperture imports, it will initially show you the JPEG. Then, once it renders its own version, based on the raw converter built into OS X, it will show you that updated preview (which is also a JPEG). From that point on, that's what you'll see, and you can't get the RAW-embedded JPEG again.
    If you use Canon's DPP, you're going to get a rendering that looks like what you saw on the camera, because they have access to their algorithms that they use for RAW->JPEG conversion. Apple doesn't have access to this; they make their own raw converter.
    It may be possible that there are issues with Apple's raw converter in specific circumstances (i.e. high ISO images on a certain camera with heavy magenta or odd lighting). You don't say what version of Aperture and OS X you're using, but it looks like it is not Aperture 3.6 + Yosemite. It may be worth upgrading to see if  it's something that's improved (an easier way is if you have access to a machine with Yosemite, just open one of the RAW files in Preview, as that uses the same raw converter, to see if it's better).

  • Considering buying aperture.  Have raw images processed in NIK NX2 software.  What happens to those files when imported into Aperture?

    Understand NiK is discontinuing Capture NX2.  Therefore would like to buy Aperture as host for image management.  If I do purchase and import RAW files previously processed in NX2 into Aperture.  Is old processing retained?  Doubtful.  Or is new processing required?  Have an iMac with iPhoto 10 etc.

    Richard and Beverly wrote:
    If I do purchase and import RAW files previously processed in NX2 into Aperture.  Is old processing retained?
    You can import the image files converted from RAW and edited by NX2 but they will no longer be RAW NEF files they will be non-lossy TIFF files or lossy JPEG.
    Or you can import the original RAW NEF files into Aperture for Aperture to do the RAW conversion.
    To my eyes/brain with the Nikon cameras I use (D2x, D100, D5100) I find that NX2 provides the most pleasing RAW conversions, but I still use Aperture for its great workflow.
    HTH
    -Allen

  • Aperture 3: Deleting raw files and making the jpeg my new master-

    Aperture 3 has made some great strides in making the following possible ( I posted this originally in 2007):
    What I'd like to do is shoot everything in raw + jpg, and then keep the raw files only for the important shots.
    I really like having the option of raw processing, but the storage demands are very heavy. If I could just make a selection of photos in a roll, and have a command to delete any unneeded raw files from the selected photos, while keeping the original jpgs as master, that would be great.
    Also, it would be great to be able to manipulate a raw file, and then when I'm satisfied with the image, to render a high-quality jpg from that raw file & make the jpg the new master, and then delete the raw file to free up disk space.
    Basically, I want the raw file safety net for everyday images, without gobbling up gigabytes of disk space <<<<<
    With Aperture 3, I can finally change the master to the jpg file, which solves part of the problem. But I still want to be able to manipulate my raw file, and render a new high-quality jpg master.
    Why don't Aperture / Lightroom do this? To me at least, it seems an obvious feature.

    I had a chance to talk to product managers from both Apple & Adobe about this at PhotoPlus Expo in NYC a couple years back. Both seemed receptive, but here we are - years later - no progress.
    I think part of the problem is that there's a purist mentality about RAW files. One should always shoot them - and then keep them forever- after all- they're your negatives!
    But what about event photography? Or weddings, as you pointed out? It makes no sense to burden your workflow & backup system with 4GB of RAW files of people grinning into the camera. Once the adjustments have been made, the RAW files are just a ball & chain on your data management. And let's not forget, once you really know what you're doing, your jpegs should be good most of the time anyway.
    I want RAW files as a safety net for errors in exposure and white balance. Once I know I have good photos, I don't need the safety net anymore- at least not at the price of all that hard disk space and transfer time for online backup. Of course, for my fine art stuff and important documentary work, I'll always keep the RAWs permanently. But not for routine parties/events.
    You put your finger on the problem with re-importing jpegs as a solution. You lose your metadata- rankings/album memberships, etc. This is no solution!
    What I want is simple, and it would be immediately useful to countless photographers:
    1) Let me batch-delete RAW files when the jpegs are ok.
    2) Let me do adjustments on my RAW file, render out a high-quality jpeg, and make the jpeg my new master.
    Whoever does this first - Aperture or Lightroom - that's the product I'll use.

  • Aperture 2.0 RAW import on a MacBook Pro 2.26

    I tried to use Aperture on my old 2.0ghz macbook, once. It was within the system requirements but never would run. I regularly use Aperture 2.0 on my iMac 2.8 and it works fine. Sometimes it hangs but in general the workflow is very smooth. Well, my old macbook died so I bought a MacBook Pro 2.26ghz and was excited to be able to edit photos on the road. However, after importing a 4gig CF card with around 200 shots on it (~12mb per shot, I use a Canon 5D Mark I) Aperture just seems to be spinning away on the data and not producing much. I can click on images in the slideshow frame and some of them will pop-up, without regard to the location in the batch. This has been going on for about 45 minutes. I realize that I should max out the RAM but the machine is well within the system requirements... what gives? Thanks in advance.
    To be more specific, the slideshow along the bottom has hash-marked images but no thumbnails. The whirling grey wheel says "thumbnails..." by it. I do this all of the time on my home machine, bulk RAW files take some time, I know but this is really dragging.

    This problem was fixed with the ProKit update, duh... my fault

Maybe you are looking for