Zum Hauptinhalt gehen

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Importing CR2 RAW files from Aperture to CO8....

Permanently deleted user
At this stage, rather than import my whole Aperture 3.6 library into CO8, I would like to import one file at a time to explore working on.

My original file will have been imported direct from camera and opened in Aperture but not edited there. So, will Aperture have already carried out its own RAW conversion? And if so, will CO8 overwrite that conversion when importing the RAW file?

I recall that Aperture offers the option to Export Original and so I would first Export the original CR2 RAW file from Aperture to the Finder before Importing to CO8.

Thanks for any help/advice
0

Kommentare

6 Kommentare

Datum Stimmen
  • EnderWiggins
    [quote="RedRobin" wrote:
    At this stage, rather than import my whole Aperture 3.6 library into CO8, I would like to import one file at a time to explore working on.

    Just to clarify: you can't run the Aperture Importer of C1 for single files, only for the library as a whole. So what you would have to do is
    a) export the originals from Aperture and then import them in C1 (if you are using a managed library) or
    b) just import them from whereever they are on your HD (if you are using a referenced library).

    [quote="RedRobin" wrote:
    My original file will have been imported direct from camera and opened in Aperture but not edited there. So, will Aperture have already carried out its own RAW conversion? And if so, will CO8 overwrite that conversion when importing the RAW file?

    If you have a RAW file in Aperture, without changing any of the sliders, what you see in Aperture is the OS X Core Image "interpretation" of the RAW data. Aperture never writes anything into the original file, this will stay completely untouched. This "interpretation" is written in a sidecar file in the database. When you then import this file in C1, C1 will do its own RAW interpretation, which will look different from Aperture (some more, some less, depending on the camera).

    However, since I deal with .CR2 files myself I can assure you, they will look better. 😊
    0
  • Permanently deleted user
    [quote="EnderWiggins" wrote:
    [quote="RedRobin" wrote:
    At this stage, rather than import my whole Aperture 3.6 library into CO8, I would like to import one file at a time to explore working on.

    Just to clarify: you can't run the Aperture Importer of C1 for single files, only for the library as a whole. So what you would have to do is
    a) export the originals from Aperture and then import them in C1 (if you are using a managed library) or
    b) just import them from whereever they are on your HD (if you are using a referenced library).


    ....Thanks, I wasn't intending to run the C1 'Aperture Importer' because I realise that it imports the whole library. Thanks for your clarification though - Much appreciated and also useful for someone else reading this.

    [quote="EnderWiggins" wrote:
    If you have a RAW file in Aperture, without changing any of the sliders, what you see in Aperture is the OS X Core Image "interpretation" of the RAW data. Aperture never writes anything into the original file, this will stay completely untouched. This "interpretation" is written in a sidecar file in the database. When you then import this file in C1, C1 will do its own RAW interpretation, which will look different from Aperture (some more, some less, depending on the camera).

    However, since I deal with .CR2 files myself I can assure you, they will look better. 😊


    ....That's good news - Thanks. Do you know if ONLY creating a crop on a .CR2 file in Aperture will have actioned Apple's RAW Converter? < I tend to think that it will have done.

    Yep, I am certainly expecting C1's RAW Converter to offer superior results as independant user demonstrations also versus Adobe Lightroom have already proved. It's exactly because of C1's superior potential that I will bother to import a few .CR2 files from Aperture which I hadn't processed yet. I'll Export Original Version individually from Aperture to the Finder and then Import from within C1.
    0
  • EnderWiggins
    [quote="RedRobin" wrote:
    Do you know if ONLY creating a crop on a .CR2 file in Aperture will have actioned Apple's RAW Converter?

    I would assume that any import into Aperture triggers a sidecar file with adjustment/conversion information, because as you may know, you can set different RAW interpretation behaviours like Moire, Initial Noise reduction, "Boost" etc. So in order to have that processed, Aperture needs to write something into the database. That means something is always there and a crop is just step #2 after that.

    [quote="RedRobin" wrote:
    It's exactly because of C1's superior potential that I will bother to import a few .CR2 files from Aperture which I hadn't processed yet. I'll Export Original Version individually from Aperture to the Finder and then Import from within C1.

    I've imported my whole Aperture library and re-edit my best images (by filtering the star ratings) from time to time with C1, basically throwing away the Aperture Importer Settings and start from scratch. The improvement is so significant, that I like to invest this time. My Flickr portfolio is now growing faster than ever just because of the switch to C1.
    0
  • SFA
    Robin,

    The RAW file is just a data file with no visual aspect to it until interpreted by something, typically using minimal "default" settings. Do be able to display the file to you to create the crop would normally require the base conversion to take place so that you can see what you are working with. I suppose it could work with the jpg rendition from the camera which is embedded in the RAW file but I suspect that most RAW converters will anticipate that the user wants to do some full editing when the file is opened rather than just cropping.

    I would guess that application with an option to crop that does not involve opening the file - maybe a crop from browser facility or what C1 allows from a catalog when the source image is off-line - could be classed as "unedited" but, as previously mentioned, the only factor involved here is whether you want your changes - in this case a crop - brought over from Aperture or not.

    As EnderWiggins has pointed out you have your RAW file (which should be unchanged) and then whatever edit file or files the converter/editor provide to record your changes. Whether the modification files can be read and used by another application is a different matter. Probably not - hence the use of TIFF files to embed the changes with minimal loss of detail when -passing them to another application for further work. IPTC information, on the other hand, is at least intended to be exchangeable between application with some element of commonality so passing on any work you may have undertaken there could be worthwhile.

    So ... if all you have done in Aperture is create a crop and you are not looking at moving over hundreds or thousands of images .... My personal opinion is that I would just bring in the original RAW file, crop that based on what you did before and keep life very simple. That way, if you were running with referenced files, you would not have to touch Aperture at all. (Except to view th crop you previously applied in order to repeat it in C1.

    HTH.



    Grant
    0
  • Permanently deleted user
    [quote="SFA" wrote:
    Robin,
    So ... if all you have done in Aperture is create a crop and you are not looking at moving over hundreds or thousands of images .... My personal opinion is that I would just bring in the original RAW file, crop that based on what you did before and keep life very simple. That way, if you were running with referenced files, you would not have to touch Aperture at all. (Except to view th crop you previously applied in order to repeat it in C1.


    ....That's good 😊 Keeping life simple is what I like 😄

    The only reason I have asked about the cropping aspect is that in Aperture (before I had even heard of C1) I would often do a quick crop as I first went through my imported images as well as click a 1-star so I could quickly delete unwanted images and return to more fully editing the cropped and/or star tag'd images later. Being a retired Art Director I am hardwired into instantly being able to recompose an image through cropping.

    I have continued my initial crop-n-tag habit in C1. Afterall, cropping can be easily revised later if desired.
    0
  • Eric Nepean
    What I am doing to move my images from Aperture to COP8, and it seems to be working pretty well, is that I started with a test batch, some of my recent work, about 20 images of various types, all managed images. In Aperture I made a new library (Test1_A) with these images (which left these images in my main library as well). I then imported the new Test1_A library into COP8 TEST1_C catalog to see what would happen. I then saw that changes would have to be made, so I deleted the Test1_C catalog, changed the Test1_A library and re-imported into a fresh Test1_C. I repeated this several times until I was happy with the process and understood what I have to do to the Aperture library to get the results that I wanted. Now the Test1_C catalog is deleted.

    I have updated my main Aperture Library so that the keywords are properly structured for import, and added keywords to identify images which will have lost adjustments and images which are stack picks, and am working on saving the version names. I will probably rename the files with their version names.

    I have selected my last years work and moved it to one folder (about 10% of the Library), and now I will create a new Aperture library with these images and import them into Capture One Pro.

    I will probably learn more from that exercise, which I will then apply to the next import, which will be larger.
    0

Post ist für Kommentare geschlossen.