Deleted key words won't stay deleted
I imported a collection of photographs to create a new catalogue that had keywords in the XMP files. About 5000 files.
After importing them I realised that I didn't want/need the keywords in the catalogue. I initially tried deleting the keywords in C1, but I couldn't get them to all deleted.
I then decided to delete the keywords from the XMP files using Photo Mechanic, I then re-synched (load only) the files with the same catalogue in C1.
This removed the keywords from all the photograph, but still left about 20 keywords in the keyword catalogue, the majority of the keywords had gone, just this 20 remained.
So I deleted these from the keyword catalogue, but when I re-open the C1 catalogue, they come back.
Has anyone any idea how to delete them properly.
Thanks,
Graham
After importing them I realised that I didn't want/need the keywords in the catalogue. I initially tried deleting the keywords in C1, but I couldn't get them to all deleted.
I then decided to delete the keywords from the XMP files using Photo Mechanic, I then re-synched (load only) the files with the same catalogue in C1.
This removed the keywords from all the photograph, but still left about 20 keywords in the keyword catalogue, the majority of the keywords had gone, just this 20 remained.
So I deleted these from the keyword catalogue, but when I re-open the C1 catalogue, they come back.
Has anyone any idea how to delete them properly.
Thanks,
Graham
0
-
[quote="myotis" wrote:
Has anyone any idea how to delete them properly.
Do you have the Preferences -> Image -> Metadata -> Auto Sync Sidecar XMP to None?
Try that - there is some black magic happening when C1 trying to keep its database and the XMP files in sync.0 -
There is a well known bug about keywords. Those which has been imported from an other database (Lightroom for instance) can't be deleted. More precisely, you can delete them for a while, until you close and reopen C1 : they are still there !!
This bug has been submitted to the staff many times, and they say they are working on it, working, working, but the last versions of C1 didn't solve the issue. Maybe version 10 ?0 -
[quote="BobRockefeller" wrote:
[quote="myotis" wrote:
Has anyone any idea how to delete them properly.
Do you have the Preferences -> Image -> Metadata -> Auto Sync Sidecar XMP to None?
Try that - there is some black magic happening when C1 trying to keep its database and the XMP files in sync.
Yes, I have tried this, it didn't work. Actually, this is the second catalogue I have had this problem with. I managed to fix it for my 2016 catalogue, but not exactly sure how. But it did involve switching of the sync, but once fixed, I have it back to full sync and I can edit the XMPs in Photo Mechanic and all seems fine.
But nothing I do seems to fix it in this 2015 catalogue.
Maybe I just need to keep on doing it until it "takes". I wish I had paid more attention to what I did with the 2016.
Thanks for your help.
Cheers,
Graham0 -
[quote="tenmangu81" wrote:
There is a well known bug about keywords. Those which has been imported from an other database (Lightroom for instance) can't be deleted. More precisely, you can delete them for a while, until you close and reopen C1 : they are still there !!
This bug has been submitted to the staff many times, and they say they are working on it, working, working, but the last versions of C1 didn't solve the issue. Maybe version 10 ?
Thanks, in my case the keywords were added by Photo Mechanic on ingestion, and removed by Photo Mechanic, so this shouldn't be an issue, or maybe PM shares the same problem as Lightroom ☹️
I would hope that this sort of thing could be fixed in a point release and not wait for V10.
Actually, just reread some of the forum posts and see that some that I thought were about hierarchical keywords are actually about the same problem I am having. I obviously didn't realise it was such a well established bug
Cheers,
Graham0 -
Hi Graham, I would hope that this sort of thing could be fixed in a point release and not wait for V10.
I don't think it's acceptable to fix that bug with v10.
Some users upgraded to v9 because of the new keyword handling and in my opinion PhaseOne can't take money for a non-functional feature. So there must be a fix in v9.x.
It's a shame that this bug hasn't been fixed during the last months.
I did also create a support ticket.
But either it's very complicated to fix that bug or PhaseOne has a very low priority for that issue.
Anyway, it's disappointing ☹️
Cheers,
Andy0 -
[quote="ApoFenomeno" wrote:
Hi Graham,I would hope that this sort of thing could be fixed in a point release and not wait for V10.
But either it's very complicated to fix that bug or PhaseOne has a very low priority for that issue.
Anyway, it's disappointing ☹️
Cheers,
Andy
It's really impossible to outguess the scale of the problem and reason for not fixing it quickly.
My very limited understanding of database design/programming shows that it is "very difficult" to design a really robust, fast and dynamic database, and I suspect even more difficult to "add it into" an existing program that wasn't designed from scratch as a specialist database.
But that doesn't alleviate the issues of users needing to deal with the bugs.
Cheers,
Graham0 -
Suffering from the same type of issues after massive transfers from Aperture to C1 ☹️ currently going through the case process... let's see if I can get something out of it! 0 -
Hi,
As I now understand, keywords can be stored in 3 different places.
Inside the COP-catalog
In the XMP-sidecar file
Inside the imagefile itself.
So if you delete them from 1 place, it might seem that they are gone.
But when you close and open the Catalog again, COP might read them again from another place than you have deleted them from.
Just a thought,
Jan0 -
Inside the COP-catalog
Yes, and that's precisely where the bug is: they don't get deleted from the catalog, even if you remove the keywords from the files and reimport them.0 -
[quote="Hassleman" wrote:
Hi,
As I now understand, keywords can be stored in 3 different places.
Inside the COP-catalog
In the XMP-sidecar file
Inside the imagefile itself.
So if you delete them from 1 place, it might seem that they are gone.
But when you close and open the Catalog again, COP might read them again from another place than you have deleted them from.
Just a thought,
Jan
Except, in the situation I describe in the OP, there are no keywords associated with any images or XMP files, they have all been successfully removed. The keywords only exist in the keyword library, and its these keywords that keep coming back after being deleted.
Cheers,
Graham0 -
Yes, I can confirm this. Even if there is no .xmp present and you have removed any keywords from the original file with EXIF editor, Capture One will - goodness only knows how! - recreate the keywords that were once there even if you import into a new blank catalogue. Homœopathic processing! 0 -
Hi Graham,
In your case it seems like the database does not get correctly updated when closing.
Have you tried to "Backup Catalog", and then use the backup database ?
Maybe that does a better job in saving the changes you made.
Although in David's case it is also happening with a brand new Catalog, which seems even more odd....
Regards
Jan0 -
[quote="Hassleman" wrote:
Hi Graham,
In your case it seems like the database does not get correctly updated when closing.
Have you tried to "Backup Catalog", and then use the backup database ?
Jan
Thanks, but this doesn't help.
if you read through the keyword threads, it seems that this is a know problem. I didn't pick up on it before posting as this specific issue is reported along with other issues and I just missed it. C1 support are apparently working on a fix.
Cheers,
Graham0 -
[quote="myotis" wrote:
Thanks, but this doesn't help.
if you read through the keyword threads, it seems that this is a know problem. I didn't pick up on it before posting as this specific issue is reported along with other issues and I just missed it. C1 support are apparently working on a fix.
Cheers,
Graham
They have been working on this since the start of the year and no visible progress so far as customers are concerned. I have moved on for now at least - if you can call going back to Lightroom moving on 😉0 -
[quote="adrianchapman" wrote:
They have been working on this since the start of the year and no visible progress so far as customers are concerned. I have moved on for now at least - if you can call going back to Lightroom moving on 😉
Well, I have moved on as well, sort of. I've moved everything into Media Pro, and I am now just launching C1 as an editor from Media pro, which so far (but only been trying it out properly today) is working extremely well, but still learning, and there are are few wrinkles to sort out.
Media pro is lightning fast, there is absolutely no rendering time for thumbnails or previews, catalogues are tiny, and they open in seconds on my 2011 Mac Mini. So I now have the benefits of a proper DAM program combined with C1 processing.
I just couldn't go back to the slowness of Lightroom and although the integration between C1 and Media Pro is a bit limited its still much better than when I was using Lightroom as my DAM and C1 for processing.
Cheers,
Graham0 -
Buying Media Pro only to get C1's DAM fixed seems a bit too pricey for my taste. The cost of C1 + MP is way more than LR (which also gives you photoshop). Agreed, we all prefer C1 over LR, but their DAM works actually pretty good, and their keywording system is way better. Synonyms, keywords sets, export control, etc. It works and is fast. I've been thinking about using Aperture or LR as the DAM and C1 as the editor, but the ease of use of a single application is not something I want to give up lightly.
I also wonder what the incentive for P1 is to fix and improve the DAM of C1 when they have a real DAM in their portfolio? Will C1's DAM always remain a 'light version', crippled in functionality, less maintained, slower? Suppose they make the DAM of C1 as good as MP, then what's the point of having MP? Maintaining two similar products is not the most efficient way to do business, especially not for a relatively small team (not even for a large team *cough* adobe *cough*).
Cheers,
Peter.0 -
[quote="peter.f" wrote:
Buying Media Pro only to get C1's DAM fixed seems a bit too pricey for my taste.
Cheers,
Peter.
Yes, I agree, fortunately I already had a license for iView media, which gave me a low cost upgrade.
One important difference of Media Pro is that it works with a much wider range of files than Lightroom and C1. It's also in a market with very few low cost alternatives. So they could keep it going and target a market well beyond the current C1 market, if they wanted to.
Hopefully the database expertise learnt by developing Media Pro would then filter into C1. I suspect they will need to rewrite C1 so it becomes a database that incorporates C1, rather than trying to tag on database capabilities to the current program.
Meanwhile, I am rather enjoying my Media Pro/C1 combination.
Cheers,
Graham0 -
[quote="peter.f" wrote:
Buying Media Pro only to get C1's DAM fixed seems a bit too pricey for my taste.
I agree with you, too. And it seems to be unnecessary as well - as the keyword issue in C1 9 Pro (at least in my case) came only after version 9.0.3.
So I still do hope for a speedy fix...
Oliver0 -
[quote="Olyver" wrote:
[quote="peter.f" wrote:
Buying Media Pro only to get C1's DAM fixed seems a bit too pricey for my taste.
I agree with you, too. And it seems to be unnecessary as well - as the keyword issue in C1 9 Pro (at least in my case) came only after version 9.0.3.
So I still do hope for a speedy fix...
Oliver
I agree as well, if the concern is just the keyword issue, that is no reason to buy Media Pro.
Cheers,
Graham0 -
[quote="John Doe" wrote:
Inside the COP-catalog
Yes, and that's precisely where the bug is: they don't get deleted from the catalog, even if you remove the keywords from the files and reimport them.
Bug seems to be fixed in Capture One Pro 10. Hooray!0 -
[quote="John Doe" wrote:
[quote="John Doe" wrote:
Inside the COP-catalog
Yes, and that's precisely where the bug is: they don't get deleted from the catalog, even if you remove the keywords from the files and reimport them.
Bug seems to be fixed in Capture One Pro 10. Hooray!
Excellent 😊
Cheers,
Graham0 -
Hooray!
I think there's no reason for hooray, I've bought C1 v9 a few months ago and now I have to pay again for a version, where a bug is fixed, that was known for months.
I'm really pissed off.0 -
YMMV. 0
Post is closed for comments.
Comments
23 comments