Aperture 3 RAW Files

I've been using Aperture 3 since it first came out.  I shoot using a Nikon D90 using RAW+Fine setting.  I always import the files into Aperture as RAW-JPEG pairs using RAW as the master file.  Although I have imported the files and have applied an effect/preset upon import, lately I've been importing the files without any effect added.  As I watch the import proceed, I initially see the thumbnail previews, which display very quickly.  I can then watch the processing and see the images change.  I'm assuming new previews are being generated by Aperture using the default RAW settings for the D90.  Am I correct about this?  When the processing is complete I can view a RAW image to which no other adjustments have been made other than the default RAW settings.  However, I can switch between two "versions" of thie RAW file my hitting the M key to view the original file.  Is this right?  Why is there a difference between an original and the RAW file at this point? I didn't think there would be, since I have not made any additional adjustments to the imported RAW file.  I'm a little confused exaclty what Aperture is displaying at this point.  I thought I understood this....
Thanks for any insight. 

However, I can switch between two "versions" of thie RAW file my hitting the M key to view the original file.  Is this right?  Why is there a difference between an original and the RAW file at this point?
Have you applied any settings in the Raw fine tuning brick? There may a camera default be set.

Similar Messages

  • Aperture RAW files preset

    I've been importing RAW files from my Sony A77 for awhile now. When they import they look like the flat image I would expect. When I open a photo though and wait for a few seconds, Aperture "adjusts" the photo with heavier contrast/color/etc. Even when I adjust the RAW Fine Tuning, I can't seem to get the image back to the original flat one I want to work with.
    Help please? Thanks!

    What William said  , but with the caveat that your RAW Fine Tuning settings play a determinant role in the extent of the adjustments you can make _with the other adjustment tools_, and in how you perceive the Image.
    (The latter is equally important to the image developer, imho.)
    Somewhat contrary to your thinking, maximizing Boost and Hue Boost, and minimizing Moire and Noise, would (I think -- I'm no expert here) give you the greatest possible range for your adjustments.
    I try to match the RAW Fine Tuning settings to the environmental light.  In the north-eastern United States, where I live, I use a RAW Fine Tuning preset that is about 9 for Boost and 7 for Hue Boost.  During a recent trip to Patagonia, however, I quickly found that I couldn't get the equivalent of something I saw in the world, and then I remembered to raise both Boost and Hue Boost.
    A local painter friend said to me, on arriving in Hawaii, "It's like having your eyes tattooed".
    The settings for your RAW converter are important -- and knowing how and when to change them is, too. There is no reason, in terms of data-retention, to aim for a particular "look" in the converted-from-RAW image.  But the conversion does play an influential role in the appearance of your data.
    HTH,
    Kirby.

  • Aperture RAW file compatibility

    Hi there guys.
    I've been considering Aperture2 for quite sometime now but am disappointed to find out that there is no RAW support for my camera, a Panasonic Lumix DMC FZ-28. The closest support is for an older FZ-50 instead while my camera is newer than this.
    With that, I would like to know what my options are with regards to importing the RAW files from my camera to Aperture2 should I decide to pull the trigger and get it.
    Thanks ahead.

    A couple comments,
    RAW is overrated for small-sensor Digitals like your Lumix. If you shoot in .jpg and use aperture for light editing and organization, you'll probably see an advantage over what you're currently doing. The fact that aperture's ads talk so much about raw is irrelevant, you can do anything it does (other than raw conversion, obviously) with a jpg. The only difference is that you have less control over the raw conversion, which your camera bight do better than aperture (it's a matter of taste at that point, not science).
    Or, you could get a better camera, i.e., a nikon or canon that is actually going to be supported as soon as possible and has decades of history of making good cameras.

  • Why Aperture doesn't send the RAW file to Photoshop

    I've seen the complaint about Aperture not passing the original RAW file to Photoshop in several places in this forum. I think I have a reason for why Aperture doesn't work this way.
    The reason has to do with the 1st law of digital RAW photography. "Never, ever, overwrite the original RAW data from a camera's RAW format file."
    Because of the above rule, both Aperture and Photoshop do not actually work on the original RAW file. They transform the RAW image data into a usable image using user specified settings (which may be the camera's default setting for that image). The original RAW file is left untouched.
    When you open a RAW file in Photoshop and try to save it, you'll be prompted for a new file name. You wouldn't want to overwrite the original RAW file by writing the edited image data back to it.
    When you edit an Aperture RAW file using Photoshop as the external editor, Aperture first creates a TIFF or PSD version image file in its library and then passes that file name to Photoshop. Photoshop opens the TIFF or PSD file and directly edits it. Since this version file is already in Aperture's library, when Photoshop is finished editing it, Aperture automatically sees the edited file because its already in the library.
    If Aperture were to send the RAW file name to Photoshop, Photoshop would open the RAW file and create a new PSD file. When it came time to save your edits, where would you save it. In order to get it back into Aperture's library, you would need some form of Photoshop to Aperture communication so that Photoshop would know where to save the edited file and Aperture would know to add it to the library. This would require collaboration between both Adobe and Apple and doesn't seem likely.
    I have a couple of ideas someone can try. These are only ideas and completely untested. I'd do it myself but I don't own Aperture (see my computer info below for the reason).
    1. Create two folders with automator actions. You export your RAW files from Aperture to a "Photoshop-IN" folder. Any new RAW image found in this folder will be automatically opened in Photoshop by the Automator action. Then you save the edited Photoshop file into a 2nd folder "Aperture-IN". Another Automator action imports this into Aperture.
    2. In iPhoto, if you try to edit a RAW image with an external editor, iPhoto creates an intermediate image file (JPEG I think) which it passes to Photoshop. But, if you drag the original RAW image thumbnail from iPhotos library window to the Photoshop icon in the dock, the original RAW image file is passed to Photoshop. You only have the problem of getting the saved Photoshop file back into iPhoto's library. Maybe this same thing would work in Aperture by dragging the Master image to the Photoshop icon in the dock.
    PowerMac G4 Dual 1.25GHz   Mac OS X (10.4.3)   FW800, 4 internal HD - 550GB

    This is all well and good. I wholeheartedly agree with the idea of keeping the "master" sacrosanct. What I object to is not being able to do the conversion in Photoshop (or elsewhere)
    What I want is for Aperture to send the raw over to photoshop when I select "open in external editor", and then follow the current workflow (I do my edits, hit save, and a second master is added to Aperture's db.)
    It's totally possible for them to do this, and it wouldn't break anything in the system, or the philosophy. Of course it's a workaround that wouldn't be necessary if Aperture's converter were up to snuff. But it isn't, and I bet it would be easier to implement the workaround than to fix the fundamental defects in the converter itself.

  • Aperture suddenly displaying "unsupported format" for Nikon D300s RAW files

    I am using Aperture 3.1.3 on my iMac 24 with Snow Leopard 10.6.8.   A couple of days ago I applied an update for Aperture RAW files that was in my update list, even though I don't use any of the cameras involved. 
    After that update Aperture gives me an "unsupported format" error on all my Nikon D300s RAW files. Every RAW file in the library.  I have never had a problem with this at any time over the last 2+ years of using Aperture.
    I have tried using time machine and rolling Aperture back to the end of July (my most recent backup) along with rolling back the RAW file plist. I then did a repair permissions, and reimported the photos after this.  I have rebooted numerous times.  All to no avail.  I have not yet tried a library rebuild that would be next if I must.
    I use a Referenced library, so I was able to check out individual RAW files with Adobe Camera RAW.   They open fine so there is no file corruption issue. 
    Any thoughts on what might be happening?  Any other file(s) associated with RAW conversion that I might need to roll back?   I do not see any mention of a problem like this when searching the web or the forum (although I may have missed something by not searching the correct terms).
    Any help would be greatly appreciated!

    The raw camera bundle is  /System/Library/CoreServices/RawCamera.bundle
    Go to /System/Library/CoreServices with the Finder, locate the the RawCamera.bundle package, select it and then do a File->Get Info on the package. You should have version 3.8.0, that is the latest and the one that you should have downloaded last week. If it is not 3.8.0 stop here and post back what version you do have, something isn't right.
    Assuming you have 3.8.0  use the Finder to navigate to /System/Library/CoreServices and then delete the RawCamera.bundle package. The Finder will ask you to authorize the delete.
    Then go to Digital Camera RAW Compatibility Update 3.7 download and install it. That will put you back to the last CameraRaw update before this one.
    See if that fixes your problem.
    As always when messing around with system files it is possible to mess things up so make sure you have a good backup before proceeding, And if any of these instructions make you nervous you might want to hold off doing them.
    good luck

  • Where can I download raw file converter for panasonic gh4

    Is aperture raw file converter compatible with Panasonic GH4

    Panasonic LUMIX DMC-GH4?  That camera is not yet supported, see the list of currently available RAW support:  http://www.apple.com/aperture/specs/raw.html
    It usually takes a few month after the release of a new camera for the RAW support to be available. As a work-around, use the software that comes with the camera (probably SILKYPIX Developer Studio), to convert your RAW to a different lossless format (e.g. TIFF), while you are waiting.

  • Seeing RAW files in Idvd media browser

    hello,
    is it possible to see the Aperture RAW files in the IDVD media browser ? I can see (some) jpg images that are imported into Aperture but none of the NEF RAW files are visible in IDvd
    or do i need to export the images to jpg first and then import them to IDvd ?
    thanks,
    tom

    in order for any of the iApps to see and use images from aperture you need to do two things ...
    1 generate previews for those images/projects
    2 enable the shraing of those previews with iApps (under preferences)

  • HT3946 What about RAW file compatibility with Nikon D4?

    Having trouble with RAW files from Nikon D4, didnt have issues before update, any help?

    My apologies for the vague question.  To be more specific after installing the latest update to Aperture, RAW files from my D4 after being transfered into Aperture cannot be opened.  Message saying Aperture does not support these files.  Not sure if it has anything to do with XQD card, all formatted as usual.  Stumped.
    thank you kindly for your time.

  • Using Aperture 3.51 I am having frequent crashes and freez ups when editing Canon raw files?

    HI,
         I have an IMac with 4 G of Ram and am using Apeture 3.51. When trying to edit CS2 raw files I experience frequent crashes and freez ups of the whole computer. Any suggestions?

    You didn't mention any color calibration being done on your monitor.  This is an essential part of any color-correct workflow.  What are you using to calibrate your monitor (and your printer)?
    Print profiles (for soft-proofing as well as printing) are for specific combinations of paper & printer.  The nine you have are each, most likely, for a common paper (perhaps mfr'd by Canon) to be used with your printer.
    I don't know what you mean when you say "I choose a high standard print option".
    Have you read the User Manual chapter on printing?
    Printing Your Images
    There is also a good appendix on calibration:
    Calibrating Your Aperture System

  • Few 5DmkII RAW files do not open with Aperture, but OK with other software

    Hi, I have two RAW files which I cannot import with Apple Aperture. The files open fine with Canon Digital Photo Professional, Raw Photo Processor and dcraw (and with various programs on my Windows 7 laptop) and I'm able to create TIFF files from the RAW files with every other software.
    Detail about the files:
    A. they are two first frames of burst (used auto bracketing, which takes 3 images in burst mode, to create HDR image)
    B. there is nothing strange in the files, they are normal RAW files and file size is normal as well (other 28.4MB and 32.7MB)
    C. both files process OK in above mentioned softwares and there are no blocks missing from created TIFF images, also preview JPG in the RAW file is OK
    D. Mac OS X Quick view (press spacebar in Finder) and Preview do show these two RAW images well (I assume they use the embedded JPG image)
    I have installed all the updates available in "Apple icon" -> "Software update..." function. Therefore I have Apple Aperture version 3.0.2. Computer is MacPro:
    Model Name: Mac Pro
    Model Identifier: MacPro3,1
    Processor Name: Quad-Core Intel Xeon
    Processor Speed: 2.8 GHz
    Number Of Processors: 2
    Total Number Of Cores: 8
    L2 Cache (per processor): 12 MB
    Memory: 12 GB
    Bus Speed: 1.6 GHz
    Boot ROM Version: MP31.006C.B05
    SMC Version (system): 1.25f4
    How I can submit the files for Apple to create fix? I searched for Apple Aperture support but there is only this forum, no email address or anything. Do they read this forum?

    Some clarifications and answers to your questions:
    First to Tony Gay:
    I try the feedback later today even they claim "Please know that while we do read these submissions, we cannot guarantee a personalized response.", which is original reason why I'm why I wrote this question here. The url you provided did not work but this should:
    http://www.apple.com/support/feedback
    This is not relevant to sRAW files, I did not change the between camera taking automated bracketed shots the image format for 2 shots to sRAW and took 3rd with RAW, that is not even possible.
    I have copied the images from card to hard drive, not trying to read from the card itself. However now you mention tried also from card = exactly same result. Tried desktop (different HD) and external USB and external eSata, all same result.
    Get info doesn't show anything wierd for the images. All other 192 RAWs from same shoot were imported with exact same methodology (as well as 60000 images before that).
    Then to gosuk2:
    There is no HDR setting in camera, I took the images FOR HDR, but did not use any specific setting, just used 1 1/3 stop bracketing and 2 second times when camera automatically takes 1 1/3 underexposed, correct exposure and 1 1/3 overexposed image (the order of images can naturally be changed via custom function in camera). All this is unrelevant since I shoot quite often HDR with this method (=more than 500 images each month) this way and they have always been fine before these two images.
    I see the files in import panel and I the don't use import dublicates setting so that doesn't affect the situation (why it would, Aperture things files are broken).
    Again HDR cannot be combined in 5DmkII, it's just automatically shoot 3 bracketed shots.
    No I don't get same result no matter what I do, it's just these two files. My other ~5000 HDR bracketed RAWs are importing fine as well as all burst/shots taken in continous shooting mode.
    I'm very aware how stacking of images works, but I do not understand relevance to this issue. I can not import the images at all to Apple Aperture, after importing all images Aperture displays dialog saying that following files could not be imported to Aperture, then displays list with both of these files in the list and gives possibility to locate the files in Finder.
    I have used Aperture since version 1 and I have 70000 images imported successfully to Aperture. Earlier I have seen this dialog "Aperture could not import image" only after hard drive/card failure. However then images cannot be used in Canon's DPP (Digital Photo Professional) or any other RAW software - now the problem ONLY EXISTS in Aperture all other RAW converters are able to open and process SUCCESSFULLY these images.
    So I'm not whining that Aperture is not good, but if it starts to work only part of the images in future and I have to process rest of the images with Canon DPP (that program is really lousy on usability standpoint) then I'm not so happy with Aperture anymore.
    Will report here if I get any comments back from Apple through the Feebback tool.
    Message was edited by: vahonen (due to forum software replacing words like s u c k s etc. with ***)
    Message was edited by: vahonen

  • How can I use EOS 6D RAW files with Aperture 3.2.4?

    The EOS 6D RAW support for Aperture requires Aperture 3.4 or later. I tried to update to Aperture 3.4 but that requires OSX 10.8.3. I am stuck with OSX 10.6.8 for a while because I use Adobe CS5.5 and it is not compatable with newer OSX. So i do not seem to have a path for 6D RAW support. I can use my EOS 20D RAW files just fine. What is it about the 6D RAW file that necessitates OSX 10.6.8 or Aperture 3.4?

    The common way is to try converting to DNG and then use the DNGs with Aperture. The drawback (other than the format conversion) is you lose camera specific optimisations with the DNG (mostly noise reduction tweaks for specific ISO values and colour tweaks).
    In the past it would have been easy to edit a few config files to get Aperture to recognise new cameras with similar sensor tech as existing cameras, but this data is now encoded so can't be changed. It is a bit frustrating when you know there is nothing special about the sensor and Aperture would be able to process the data just fine.
    Andy

  • 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.

  • Convert RAW Files in Your Aperture Database to Adobe DNG Files

    The following describes how to convert all the RAW images in your Aperture database from manufacturer formats, such as Sony's ARW and Canon's CR2, to Adobe's DNG while retaining all the Adjustments already applied to your RAW files.  In the example below I am assuming that your Aperture Library has ARW and CR2 files.  These steps work with the latest version of Aperture, being Version 3.3, and have not been tested with earlier versions (in fact, it probably will not work because the database structure changed in 3.3 - however, this means that the steps below can also be applied to your iPhoto library).  The steps are:
    1. Within Finder select the Aperture Library and Secondary Click to bring up the Shortcut Menu.  From this select "Show Package Contents"; this will open a Window showing all the files/directories contained within your Aperture Library.
    2. Drag the "Masters" folder out of the Package and place it on your Desktop.  The purpose of this step is so that Applications, such as Adobe DNG Converter, can "see" the "Masters" folder, which they cannot do if it is located within the Aperture Library Package.
    3. Run the Adobe DNG Converter, select the above "Masters" folder with the "Select Folder" button, make sure you have selected the option "Save in the Same Location", it is also a good idea to select the option "Skip source image if the destination already exists", check your Preferences then select the "Convert" button.
    4. Adobe DNG Converter will now convert all the RAW files to Adobe DNG files and save them in the same location as your existing RAW files.  Once complete, take a note of (a) the number of files converted and (b) the types of files converted, such as if the conversion includes ARW, CR2, NEF files etc.  In this example I will assume that the converter only found ARW and CR2 files; if your system is different then modify the steps below to make sure it covers all the RAW file types converted in your particular system.
    5. Select the "Masters" folder and in the Finder Window Search Field search for all the files that end in .ARW and .CR2 (this filename search list should match the types of files found by the Adobe DNG Converter in step (4)(b) above).  The number of files returned by the search must match the number of files recorded by the Adobe DNG Converter in step (4)(a) above.  Do NOT put the .DNG files in your search criteria.  Select all the files found in the search and move them to the Trash.  This will delete all the original manufacturer's RAW files from your Aperture Library leaving behind all the new DNG files.
    6. Move the "Masters" folder on your Desktop back to the root directory of the Aperture Library Package Content directory.
    7. Select the Finder Window containing the Aperture Library Package Contents.
    8. If there is a file called "ApertureData.xml" then open it with a text editor.  Search and Replace ".arw" with ".dng", ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (note, do not use the " marks in your search).  Make sure you cover all the file types incorporated in your particular system.  Save the "ApertureData.xml" file.
    9. Traverse to the Database/apdb directory.  Select the "BigBlobs.apdb" file and open it with a Hex editor.  In this example I will use Hex Fiend by Ridiculous Fish (see http://ridiculousfish.com/hexfiend/).  Once the file is open perform a Find and Replace ensuring you are finding and replacing Text and not Hex.  In Hex Fiend this means selecting Edit/Find from the menu and then selecting the "Text" button to the top/left of the window.  In your Find/Replace field you will need to find ".arw" and replace it with ".dng", make sure you select "Replace All" (note, do not use the " marks in your search).  Do exactly the same for ".ARW" with ".DNG", ".cr2" with ".dng" and ".CR2" with ".DNG" (and whatever particular RAW files were in your system).
    10. Perform exactly the same steps in (9) for the files "History.apdb", "ImageProxies.apdb", "Library.apdb" and "Properties.apdb".
    That is it, your Aperture Library now contains DNG files instead of your original manufacturer files while still retaining all the Adjustments originally made in Aperture to those manufacturer files.  Of course, you can repeat the same step and replace your DNG files with the original RAW manufacturer files if you wish.  This process works because:
    1. Aperture does not store the Adjustments in the RAW files, it keeps these in its internal SQLite database.
    2. By using a Hex Editor you (a) don't have to play with SQLite to gain access to Aperture's data and (b) because you are replacing text that has exactly the same number of characters you are not invalidating the format of the underlying data file - this is why you use a Hex Editor instead of a simple text editor.
    Think of Aperture as being a repository that holds Adjustments which then link to the original RAW source.  Therefore, the above process simply replaces your RAW source and therefore all the Aperture Adjustments are still valid; same Adjustments, new source.  In case you ask, no, you cannot transfer Adjustments in and out of Aperture because there is no standard to transform adjustments between different photographic applications.

    A rather involved method, David.
    I am sure it works, and compliments for figuring it out, but I think one critical step is missing in your workflow: Before you begin - backup, backup, backup!
    And I think, all the edits in your database that you are doing so diligently, is what you bought Aperture for to do for you, why do it yourself?
    I convert selected raw files this way - without manually patching the Aperture Library:
    Export the originals of the raw images that I want to convert.
    Run dng-converter.
    Import the converted originals back, flag them,  and move them to the project they came from.
    Sort the project by capture date, so that identical images are show side by side.
    Then I use the Lift&Stamp tool to transfer all adjustments and tags from the original raw to the dng copy. I check, if some edits are left to do, then delete the original.
    It may take a little longer than your method, but this way all edits in the library are done by Aperture, and I am protected from accidental slips when editing the property list files. That requires a very careful work.
    Patching the database files inside the library may be justified as a last ressort, when you need to fix and recue a broken Aperture library, and none of the provided tools is working, but not as a routine operation to do batch conversion of image files. It is very error prone. One wrong entry in the library files and your Aperture Library may be unreadable.
    Regards
    Léonie

  • Is there a way to edit the same RAW file in Aperture 3 and then Photoshop CS5?

    I recently got Aperture 3.4.5 and its been great for stream-lining my workflow.  But for certain RAW adjustments, like applying a gradient, I want to use Photoshop CS5's RAW editing window.  I don't seem to be able to export the file as a modified CR2 from Aperture to Photoshop CS5.  Is there a way to do this?
    And if exporting a modified CR2 from aperture is not possible, what advice can you give me for applying gradients in aperture, or in combinations with photoshop.  Is there a way to open a JPEG or TIFF in the raw editing window by any chance?
    Any and all advice welcome.  Cheers!
    -Mike

    Is there a way to open a JPEG or TIFF in the raw editing window by any chance?
    If you open Bridge and go into the Camera Raw Preferences, you will see a section at the bottom where you can set preferences for TIFF handling. Setting the option to 'Automatically open all supported TIFFs' will result in any TIFF file sent from Aperture to Photoshop via 'Edit with Photoshop CS5' function being launched in ACR and allow you to work on the TIFF file.
    You then have to open the image in Photoshop with the 'Open' button in ACR and save the file (making sure you have the TIFF file extension set when saving). I haven't used this in a while, but I think it may try to save as a '.tif' file which would not be seen by Aperture when you complete the save (and have a '.tif' file sitting in the Masters folder that has no connection).
    This is still not the RAW file - obviously - but will allow you to use the ACR tools on the TIFF file generated by Aperture and return it with those edits if saved correctly in PS CS5.
    Message was edited by: CorkyO2 for grammatical errors.

  • I can no longer import raw files from my Panasonic Lumix LX5 into Aperture 3.3.2 - raw files from my other Canon cameras are fine. Am still running Lion - NOT Mountain Lion. Tried all available software updates - no joy. Any ideas please?

    I can no longer import raw files from my Panasonic Lumix LX5 into Aperture 3.3.2 - raw files from my other Canon cameras are fine. Am still running Lion (10.7.4) - NOT Mountain Lion. Tried all available software updates - all up to date apparently but still no joy. OS X Lion shows the LX5 as a supported file format. I dont want to have to upgrade to Mountain Lion just to see if this solves the problem. Any ideas please.

    Since when did this happen? Directly after you upgraded to Aperture 3.3.2?
    If it happened directly after the upgrade the problem may be, that the raw support for your camera got lost. For some posters it helped to register the raw support again, see this post by Alan Roseman:
    Aperture 3 preview of raw file greenish
    If this does not help, you may need to reinstall Lion to bring back the raw support.
    But if the problem occured independent of a new installation, ypu may have a problem with your camera or the card you are using. Have you tried to use a different card or to reformat the card in the camera?

  • Aperture wants 825 MB more diskspace, but my HD has 630 GB free space. A perture doesn't let me import my latest raw files. What's the problem?

    Hi, I have Aperture 3.2.2 installed on a iMac with OS 10.6.8
    While I plug in my Nikon to import my raw files from today, Aperture tells that I need 825 MB more space on the disk.
    But actually I have more than 600 GB free space on my HD. So what is the problem? What should I do?
    Any ideas?
    Cheers
    Andreas

    Not sure.
    Try these, though:
    . Empty Aperture Trash
    . Close Aperture
    . Empty system trash
    . Reboot
    . Try the import again.
    What does Finder tell you about the free space on the drive volume in question after you've emptied the system trash?
    Are all of your Image's Masters managed?
    Are you sure you have Aperture set to import to the drive you want?

Maybe you are looking for

  • Z68A-GD65-G3 SLI black screen lock ups

    Let me start off by saying I have tried everything and I motivate everyone to prove me wrong and provide me with a solution to this issue. System spex: MSI z68A GD65 G3  2600k Corsair XMS3 1600 16GB Corsair AX1200 2 - EVGA GTX 580 3GB SLI Running bet

  • Mouse turns off after waking up

    I just bought a new keayboard for a PowerMac G4 I was given. I am using a standard 2 button optical mouse plugged into one of the usb ports on the keyboard. After the computer comes back from sleep, the mouse will not work unitl I unplug it and re-pl

  • Statement "CALL SCREEN" is not allowed in this form.

    Hi, Could anyone identify the short dump. Statement "CALL SCREEN" is not allowed in this form. There is probably an error in the program "SAPLKKBL". This program is triggered in the update task. There, the following ABAP/4 statements are not allowed:

  • General use

    This is probably a worn out thread, though I'm gonna post it. I'm interested in getting the Airport Express Base Station, mainly to stream my iTunes wirelessly through my stereo. For those of you who have this product and use it for this, does it wor

  • Domain Administration Server HA

    Greetings, I'm in the process of setting up a Appserver cluster, with four nodes. Originally I planned to install domain administration server on one machine, then install nodeagents on all four machines. I was going to create a cluster and add the n