Library image not matching image
After importing images the library do not match the actual image.
Notice that the image selected on the right is clearly not anything like the image to be edited. The image selected on the right (library) is the image from a completely different folder.
I cannot accurately edit my photos with this mismatch.
-
I'd suggest verifying the catalog (or session, as the case may be) to see whether that cures the problem.
Also, is this a catalog or a session?
Ian
0 -
I only use one catalog with every import having a unique folder. I have done a reimport of the files, done the locate on the folder to reload the images again.
The files that the system is displaying in the library do not even share the same name and are not even on the same physical drive.
0 -
Yes, but have you tried verifying the catalog, as suggested?
Ian
0 -
Yes. The system went through a repair process and now the session is in worse shape as closer to 50% of the images do not match verses the earlier about 15%.
0 -
Sorry, but is it after all a session, not a catalog?
Ian
0 -
David,
Tricky one to analyze without access to the system.
I would guess that Windows is struggling with disk and file indexing at the system level.
Are you running Window 10?
If so, which update in the release cycle have you reached?
0 -
Yes I am using Windows 10 build 18363.1316.
I don't think this is a windows issue, if it was this would have happened before. Last week I imported files without issue but since updating Capture One this is now happening. Like I said several of the images appearing do not share the same file name and are not even on the same physical drive.
0 -
David,
I have a later Win 10 update on a newly acquired machine. Build 19041
I'm running C1 V20.
I can create new sessions and access old sessions on my NAS with no significant problems. Some of the display panels seem to take a while to refresh with, for example, thumbnails after using a filter but nothing significant and possibly related to the NAS or the fact that I have several apps running and most of the RAM is used. The Edge browser has the highest memory accreditation. This system only has 16Gb at the moment. More will be added soon.
You mention updating Capture One.
May I ask from what it was an what is now is?
Are you opening pre-existing Sessions (or catalogs?) or creating new ones with new image files?
Has anything else changed on your system recently? For example have you had a crash of any kind? Have the external disks had any work - renaming the disks for example.
Do the folders on the external disks have folder with the same names?
One thing you might want to consider is to close Capture one and them reboot the system 2 or 3 times one after the other without opening any applications. This can sometimes help clear up old "workfiles" and generic temporary files that can be orphaned during normal use. Usually the workfiles will soon have obsolete references and simply be ignored but given enough time, or some other types of events, they may be re-discovered by internal disk management processes and throw up some strange results. That is extremely rare but not impossible.
Does your C: drive have plenty of free space and likewise is there plenty of spare capacity in your RAM memory?
How do the names of the mismatched browser and viewer images compare? Are they from the same camera?
0 -
When photo editing that is generally all that I am doing and system memory usage is very low, I do not keep programs running if I am not using them. At the times of imports Capture One was the only thing running and it uses less than 50% of the memory. More than 20% of the C drive is free so that shouldn't be an issue.
I am using a single Catalog.
Between the files imported on Jan 12th (no issues and 1400+ images) and the ones loaded Jan 23rd (447 images) I had no system crashes, no updates to Windows or any other program of significance. Capture One was updated to version 14.0.2.36
The images having issues have both a unique folder name and parent folder name when compared to any other drive currently. For the screen shot showing this issue the image is named A7R08378 but the file name of the other image is "Mallard - Home - 04012019 - 14". The original name of that file would have been something like A9######. So no they are not from the same camera.
0 -
Hi David,
So much seems to be excludable at this point.
Any surreptitious Windows updates?
The C1 version prior to 14.0.2 was also 14.something?
Are ALL of you catalog imported images referenced and held on external drives?
Are your drives all hard drives or SSDs or a mix of the two? I doubt it is any influence but the 20% disk availability needs to be considered as a storage capacity in Gb that takes into account the needs of the OS for possible RAM overflow and dumps as well as processing requirements. I run and SSD C: drive down to around 10% (Win 7) which is about 48Gb for a system with 24Gb RAM. Anything below that causes evident issues. At that level it is just about usable. For spinning drives I would want to see double the spare capacity - so about 100Gb.
To me it all points to some sort of data index problem that may emanate for the Windows file system referencing and indexing but might also be something to do with the data in the Catalog files. At that point the question becomes "Are you seeing the Preview files as built and saved at time of import or are you seeing something re-calculated. from the RAW file?
Tricky to try to think this through remotely.
Random thought. What happens if you disconnect/Disable the drives with the RAW files on them and leave the catalog to work with just the thumbnails and preview files, bot of which are stored internally to th =e catalog.
Meanwhile, unless you feel able and willing to plough through the log files, it may be a good idea to create a Support Case using the "Submit a request" feature in the Community pages and have the C1 Support Team take a look at the problem for you.
Also check if the latest update created a backup of the catalog file as part of its update process.
0 -
Yes the C1 was 14.0.2 something.
I have a mix of drives with the C being an SSD but the 20% is about 120GB of free space. The external with the files still has a little over 5T left. I only have 16GB of RAM but 3666 speed.
I think what I am going to try and do is copy the files from the original SD card to a formatted card and rename all the files. Wipe the files from the external drive, create a new folder system for this and then do a new import with a very different name. Let you know how it goes.
If this doesn't work I'll go with the Support Team idea.
0 -
I too began having problems immediately after installing update version 14.0.2.36. I'm using a single catalog with child folders for each year. Within each year, there are additional folders. After the update one child folder (2020) was not visible. I verified the catalog, tried reimporting that folder to no avail. I then went to my backup file and that was missing 2 years of images in the database.
All of the images are in exactly the same place that they were in before the update. There is plenty of space on my internal drives.
I open a support request 5 days ago but just got a generic response - we're really busy and will get to you when we can.
There seems to be something wrong with the 14.0.2.36 update, at least for a few users. I'd recommend opening a support request.
0 -
So for my issue the task I did finally worked. Will have to see how the next new file load goes.
Tim - Shortly after I did the update I did a sync and it removed all of the folders linked to the catalog, thankfully I had a backup that was a couple days old or I would have lost all of the editing I did.
I agree that this latest update appears to have cataloging issues.
0
Post is closed for comments.
Comments
13 comments