Migrating from Aperture
Hi all,
I am having some troubles with C1 current version while trying to migrate from Aperture (last version).
All images are in a separate master folder structure; when importing the Aperture catalog, c1 just tells me "1xxx objects not imported...".
Now I have contacted support --> "no log files for catalog import" --> no luck. How the heck can I find those >1000 objects that werent imported? Cant be that I am the first one to have that problem - also, cant be that there is no way of having an import-module that doesnt log errors...
Furthermore, what happens if you add pictures in the folder structure outside C1? Does it recognize that there has been a file added? Because somehow ti doesnt look that way. Maybe someone can share a light on this as well.
I am really getting more worried every day that I bought the wrong solution with C1... I really loved Aperture, although it was quite slow etc. in the old days 😊
I am having some troubles with C1 current version while trying to migrate from Aperture (last version).
All images are in a separate master folder structure; when importing the Aperture catalog, c1 just tells me "1xxx objects not imported...".
Now I have contacted support --> "no log files for catalog import" --> no luck. How the heck can I find those >1000 objects that werent imported? Cant be that I am the first one to have that problem - also, cant be that there is no way of having an import-module that doesnt log errors...
Furthermore, what happens if you add pictures in the folder structure outside C1? Does it recognize that there has been a file added? Because somehow ti doesnt look that way. Maybe someone can share a light on this as well.
I am really getting more worried every day that I bought the wrong solution with C1... I really loved Aperture, although it was quite slow etc. in the old days 😊
0
-
Hi,
I migrated 4 years ago from Lightroom to Capture One. My LR catalog contained about 15,000 images. It took a long, long time (about a full night) to import and build the previews. After migration, I must say that I "lost" some hundreds of pictures, I don't know why. Actually, I didn't loose them as they were still in the main storage folders of my RAWs. They were just not imported. So, I had to go back to each of the RAW folders and identify (by difference) the pictures which were not imported, and import them individually. A little bit cumbersome, but it was worth to do it, and I don't regreat at all my migration, as Capture One was far better than LR at this time (I don't know now).
When you add pictures in the folder structure outside, Capture One doesn't know it, and you have to import them in your catalog, anyway, if you want to work on them.
Robert0 -
First, about your "what happens if you add pictures in the folder structure outside C1" question: It's really easy.
- If the folder you're adding images to already shows in C1, right-click on the folder in the Folders section of the Library and select "Synchronize" from the contextual menu. New images in formats that C1 understands will be added to the library AND will show up in the most recent Recent Imports collection.
- If you created a new folder (i.e. C1 doesn't yet know about it), Click the "+" icon in the Folders section, navigate to the new folder, and select it. The folder will then show in Folders. At this point right-click on the newly added folder, select "Synchronize" and you're set as above.
As for "images not imported", I can think of 3 possibilities:
1. They could be Aperture variants (like C1 versions), which of course aren't distinct image files at all. C1 only imports actual image files, not all versions. I think this is most likely what happened.
2. The files were formats that C1 doesn't understand. If I recall, Aperture may support some file formats that C1 doesn't. The only fix I can think of is to go into Aperture and export them as JPEG or TIFF.
3. It's unlikely, but C1 may have skipped some files it shouldn't have. If that's the case, go through your folders and synchronize as described above.
As for finding what's missing...
On the assumption that it's versions that are missing, you could go into your Aperture library, click on any image that has multiple variants and show the image in the Finder. Note how many files are in that folder. Then go into C1 and check how many files C1 imported from that folder. I'm guessing that the number will be the same, i.e. Aperture's showing a lot of "virtual objects (aka variants) that C1 can't import (probably because C1 can't interpret Aperture's adjustments).
Alternatively, can you go into Aperture and have the program show only variants? If you can, it'll give you a clue about whether the import "problem" is one of variants.
I've kept my old Aperture library around for reference, but of course that won't be useful for macOS 10.15 or later unless I run Aperture in a virtual machine. At this point (5 years into C1) it really doesn't matter, as I haven't referred back to the library in years. C1 does such a better job and is so much more user friendly for me (after I got used to it and made my own workspaces) that I don't miss Aperture at all. I hope you find the same.0 -
I migrated a large number of images fro Aperture to Capture One a few years ago. I haven't opened my Aperture Library for a couple of years now.
In your situation, there are likely a small number of causes for the missing images, each issue repsonsible for a grroup of missing images. Don't assume there's just one cause, but there's unlikely to be more than 5 or 6.
RAther than identify each individual missing file, the trick is to identtify each "cause" and all the files affected by it (in Aperture) Then find the work around, e.g. convert to TIFF, and import those again.
The typical cause of failure to import is unsupported file formats.- Capture One does supports only a few video formats. I excluded all my video and audio recordings from my final import.
- Capture One still does not support certain RAW formats. E.G. Panasonic FZ80.
- A TIFF file can contain almost anything. Certain types of TIFFs are not supporte. This usually traces back to a certain scanne, or a certain SW tool, like an HDR processor..
What I would do in your shoes is start with some of the smaller albums, comparing the count of images between Aperture and Capture One. This should turn up a few missing images without too much work. Once you find a couple, note the file types and the camera or scanner or application of origin. Check if the file type is supported, check if the camera is supported.
Once you think you have a type that didn't get imported, use Aperture to idenfy all the images of this type, and what albums and projects they are in. Now check C1 to see if any got imported. Likely not.
In my case I excluded video and audio recordings, and converted unsupported file types to TIFFs. Images with less than 512 pixels in a dimension are uneditable, these I either padded with a border, or used an interpolator to double the pixel count.
After the each fix, I found it easist to simply delete the previous catalog, and redo the import with the fix in place.0 -
Hi all,
many thanks for all the answers!
Going through the folder structure manually sounds sort of hard - there is quite a chance that i miss something by mistake...
Maybe there is another way: if I export ALL objects from the imported catalogue and then do a folder / file compare in osx, I would be able to get the difference...
I have now experimented with the export, but I cannot get it to export ALL objects somehow; will keep trying & keep you posted. currently, something is broken because clicking on any folder in the catalog crashes c1... and believe it or not, i havent done anything strange. but ticket is on its way, maybe they can analyse the logs.
cheers
mario0 -
quick update:
every click in the folder structure or "all images" (left toolbox) did crash c1.
fix: delete the c1 plist file, at first reopening it will crash again, but at the second everything works like it should (no crash).
but when exporting, i would need it to export to the same structure as in the source filesystem. but i cannot find a variable for like "full path to image", only the first parent folder name...any thoughts?0 -
[quote="NNN636579228497173990" wrote:
when exporting, i would need it to export to the same structure as in the source filesystem. but i cannot find a variable for like "full path to image", only the first parent folder name...any thoughts?
Are you using the Export command, or a Process recipe?
In the Export dialog box, there is a section called Recipe, with a File tab within it. On that tab there is a Root folder drop down and one of the options there is Image Folder. Using that will put your exported output in the same folder as the raw file.
If you are using a process recipe, there is a similar File tab in the Process Recipe tool on the Output tool tab.
Ian0 -
[quote="Ian3" wrote:
[quote="NNN636579228497173990" wrote:
when exporting, i would need it to export to the same structure as in the source filesystem. but i cannot find a variable for like "full path to image", only the first parent folder name...any thoughts?
Are you using the Export command, or a Process recipe?
In the Export dialog box, there is a section called Recipe, with a File tab within it. On that tab there is a Root folder drop down and one of the options there is Image Folder. Using that will put your exported output in the same folder as the raw file.
If you are using a process recipe, there is a similar File tab in the Process Recipe tool on the Output tool tab.
Ian
I am using the export command from file menu; I think exporting into the same folder where the raw file is would basically mess up my master-folder completely. The purpose of generating an export that mirrors what c1 has in its database (excluding the initial missing 1100 images) would not be covered I guess. The whole idea was to get that export and do a filesystem-level compare / diff etc. to reliably identify the files that have not import from aperture.0 -
another update:
procedure was: importing from aperture into new catalog; aperture had only referenced images (re. to my masters-folder on my internal disk)
now import has been done, ~1100 objects not imported
first strange thing: i get two entries for the same structure, one green, one red, same name, obviously same content.
second: in the masters-folder, i created a new folder "incoming" for - well - new images 😊 from the manual i learned to use the "sync" command from the context menu to make this new folder appear. but it doesnt. what it does is it imports all my files from the masters-folder again, doubling them in the catalog. but no incoming folder, none of its pictures.
maybe c1 and me arent meant for each other, but this is very confusing; having a filebrowser which is not actually looking into the live-filesystem, i dont get it. but maybe i am "holding it wrong" 😊0 -
Go back and carefully read my post about how to add and then sync folders in C1. Your description sounds like you're doing too much work, and some of it's not the right work. 0 -
Further to Nature Isme's comment, Capture One's browser only shows folders and images that are "known" to it.
(technically - "known" means registered in Capture One's database).
This is the way the user prevents Capture One from acting upon every file and folder one every drive of the Mac. Only the ones that the user has identified.
It shows folders which have images in them that are referenced by Capture One.
It shows all the parent folders of these folders
(Your new folder doesn't fall in either of these categories)
It also shows folders that you, the user, manually add using the "+" icon.[quote="Nature Isme" wrote:
If you created a new folder (i.e. C1 doesn't yet know about it), Click the "+" icon in the Folders section, navigate to the new folder, and select it. The folder will then show in Folders. At this point right-click on the newly added folder, select "Synchronize" and you're set as above.0
Post ist für Kommentare geschlossen.
Kommentare
11 Kommentare