Dreaded Read-Only icon
As a longtail refugee from Aperture I finally took the leap in autumn and did an import of my Aperture library to CO on the trial (using CO-20). All seemed good so bought it on pre-sale.
I've now upgraded to C21. Editing new photos has been great, but I've dipped back into my archive this Christmas and it seems all the photos that came from Aperture are in read-only mode with the dreaded eye symbol by the preview. Basic edits, ratings, etc are all intact (some preview as B&W as they were in Aperture) but I can't touch them in CO.
C21 is activated using a full, perpetual CO-Pro license and it works fine with new photos from that same camera - this is not a case of trying to edit Nikon RAWs with CO-for-Sony or something!
I'm at a loss as to whether this is a version issue (something introduced by C21); whether it doesn't like that they were imported under a trial license (which would be odd) or if it's just a straight-up bug. Any ideas?
-
Where are the source files?
Did you import them into the catalogue or are they referenced to somewhere else? Perhaps another drive?
Does the original path name for the drive and location still exist just at is was back at the time of import? (Assuming they are referenced files.)
Note added: You mention some B&W files - they would need to be in an RGB colour space for editing to be possible.
Also there are some size qualifications (see the release notes, etc. for details) but I would think that would be unlikely to affect "all" files and that in any case you would have noticed that back at the time of the trial.
0 -
The source files are on a NAS, mounted as a local drive. The images are referenced - the Aperture Library was all referenced (originally Managed, but I broke it back out to a Referenced structure years ago when the Library passed 50GB and a single massive blob became unwieldy!).
One possible problem is that on mac the folder is mounted directly as "photos", since macOS doesn't do drive letters. In Windows it's mounted to H:\YYYY\MM\Shoot_Name. There was necessarily a re-referencing event. Obviously I can't just pull the Aperture library directly into CO on Windows (my working platform these days) since only the mac version of CO supports importing Aperture libraries.
Importing the Aperture Library into the CO Catalog was quite straightforward (at the time!).
The images are all .CR2 in an RGB space. Nothing is "natively" black & white as such - my note there was that the previews appear to be rendering correctly using the adjustments from Aperture (those that carry over, not all do). Being non-destructive, the B&W images are colour underneath and of course even if something weird had gone on, those should not cause the wholesale refusal to edit any of the images coming in from Aperture.
0
Post is closed for comments.
Comments
2 comments