Problem with Import...
I am trying to import some catalogs from Lightroom. In this process I stumbled across two issues:
1) C1 imported some 17,000 images into a new catalog, but it reported some 970 "incompatible images." However, I fail to see a list of these images to make heads and tails of this message. Is there any way to see which images exactly are "not compatible"? They were all compatible with all versions of LR over the years. Indeed, the LR catalog has 18264 images, C1 catalog only 17276. This is clearly a bummer.
2) C1 ignores directories when importing. I have my files organized in the structure "catalog/year/month-day/*.images"
for example sail/2017/02-21/*.nef or *.cr2 etc. However in the sail catalog I happened to have images from another sail on the very same day in February. Since C1 ignored the year directories in the sail/<year>/mm-dd/ I see in the new C1 catalog something like this:
In Catalog
F: 02-17 300
02-17 250
... etc.
This is also a bummer. Of course these both 17th of February were in the original in different years.
Do I do something wrong, or have I stumbled across a bug?
1) C1 imported some 17,000 images into a new catalog, but it reported some 970 "incompatible images." However, I fail to see a list of these images to make heads and tails of this message. Is there any way to see which images exactly are "not compatible"? They were all compatible with all versions of LR over the years. Indeed, the LR catalog has 18264 images, C1 catalog only 17276. This is clearly a bummer.
2) C1 ignores directories when importing. I have my files organized in the structure "catalog/year/month-day/*.images"
for example sail/2017/02-21/*.nef or *.cr2 etc. However in the sail catalog I happened to have images from another sail on the very same day in February. Since C1 ignored the year directories in the sail/<year>/mm-dd/ I see in the new C1 catalog something like this:
In Catalog
F: 02-17 300
02-17 250
... etc.
This is also a bummer. Of course these both 17th of February were in the original in different years.
Do I do something wrong, or have I stumbled across a bug?
0
-
[quote="herthh" wrote:
1) C1 imported some 17,000 images into a new catalog, but it reported some 970 "incompatible images." However, I fail to see a list of these images to make heads and tails of this message. Is there any way to see which images exactly are "not compatible"? They were all compatible with all versions of LR over the years. Indeed, the LR catalog has 18264 images, C1 catalog only 17276. This is clearly a bummer.
C1 is not compatible with some DNG images - especially the HDR and pano stitches that LR can create. And C1 does not import variants either. It just brings in one version of each image.
What I ended up doing to verify that all my images were properly imported was to use LR to export a version of my catalog that had no dng images and no variants. Then I used that to import into C1. That way I was able to verify that everything came across to C1.[quote="herthh" wrote:
2) C1 ignores directories when importing. I have my files organized in the structure "catalog/year/month-day/*.images"
for example sail/2017/02-21/*.nef or *.cr2 etc. However in the sail catalog I happened to have images from another sail on the very same day in February. Since C1 ignored the year directories in the sail/<year>/mm-dd/ I see in the new C1 catalog something like this:
In Catalog
F: 02-17 300
02-17 250
... etc.
This is also a bummer. Of course these both 17th of February were in the original in different years.
Do I do something wrong, or have I stumbled across a bug?
In the library tool click on the ... button and select the command "Show Folders Hierarchy". I use a similar directory structure and had the same feeling of disorientation.0 -
Thanks for the hint, indeed: I have the directories now right 😄 I think C1 should have this option "on" by default.
If it comes to missing ca. 800 images: I do not have DNG's and even if I had, this would surprise me that exactly the DNG's might be an issue. The "theory" is to convert to DNG, in order to be timeless and secured for the case that some cameras would loose its support in the future.
Still C1 [color=#0000FF:1s904b67]SHOULD HAVE [/color:1s904b67] absolutely provide a list of such "incompatible images" with an explanation, such as "camera not supported" etc. As it is, one has to go through the directories one by one and fiddle out (in 18,000 items in this case) what's missing exactly and why. The missing images are partly the film-scans provided as 16bit TIFF or 8bit TIFF (e.g. screen dump). This catalog 'sail' goes back as far as 1980. No issue for Lightroom, though. Most of the TIFF's are made by NikonScan and LS5000 scanner. Some missing images seem to be almost arbitrary. For example LR shows in one directory 89 TIFF's, C1 imported 86. They are all identical as file format goes. Even synchronize folder does not show the images. One have to search for these exceptions manually. The "Locate" option in C1 goes back to the original LR lrcat file, and not to the selected directory.
One simple elementary issue making search for the culprits difficult is that while LR shows a total image count in all sub-directories, C1 does not. It shows '0' in the root directory. This makes the search a tedious undertaking.
Thanks again for your help! I was already worried that no one reads these messages and as much I hate to succumb to Adobe's subscription scam-scheme (as I call it), I became pessimistic that I will have no choice.0 -
I agree that showing folders should be the default. LR hides them too.
In C1 you can select all images and find the catalog's total count there.
When I ran into import problems I got help from phase of ne support. Ask them about your missing images and lack of error messages.
You don't have to stay with the subscription scam. I made the transition - so anyone can 😊0 -
Catalog total count is visible, but the count in very directory, e.g. the year directory. I see only '0' in every case. After going directory by directory manually and comparing the number of images, I found several cases explaining why C1 does not have this great many images in its collection after the import:
1) some TIFF files are being ignored, but I fail to identify a specific factor why some of these files are "not compatible" and others are, even if they are being generated by the very same Nikon Scan.
2) some cameras are not supported. This includes the Leica/Lumix models, such as the early V-Lux or FZ18.
I have to assume that C1 will never go back and add these missing models. Of course, the images are still there and I have my older LR in perpetual license. Thus technically speaking I could run in parallel LR and C1. LR for older files, and C1 for all upcoming. It is not optimal for sure, and I still have some 2 weeks time to think about it. Alternative: pay the monthly due to Adobe, what is also not optimal. In some cases, when I am busy, I do not touch photography for months, and there is also always the looming scare of losing all the work should the subscription expire.0 -
May I suggest contacting phase one support and provide them with a few of those files that don't import? They will be able to tell if they consider it a bug and possibly how to workaround then.
For the older cameras you could export tiff files for them from LR then you will have a version in C1. Assuming they don't fall into the problem above.0 -
Thanks, I think I will. Which place is it to report bugs or enhancement requests?
I timed the 30-day test period not right, I have only 3-4 days remaining: It ended up in the tax reporting weeks, and in the US we are all stunned by the alleged "tax relief", for which apparently we the middle class have to pay. Confusion, retry, visit tax accountant to check if its real... All this trumps (pun intended) the workings on photography.0 -
Here is the link to report a new case - you have to login with an account first.
https://www.phaseone.com/en/SupportMain ... er-support0
Post is closed for comments.
Comments
7 comments