Aftershot keyword bug?

[goatbeater]

I'm a long term user and fan of PSP - since the JASC days.
I wanted to improve workflow and thought I'd move to Adobe products.
Tried Lightroom - even paid the money - and find it unhelpful at best and unworkable most of the time.
So I decided that Aftershot should be OK - Corel product etc ...
Still have the trial but the jury's out right now - how come workflow products are SO complex and SO damn SLOW!!!

Anyway - I added my 50k photos and started to keyword.
Of course I made some mistakes.
The problem is I have some under sets like Subject/People/Family or Genre/Snapshot that are mistakes and I can't get rid of them.
They don't appear on the right hand side in metadata but the images turn up in the collections when selected on the left hand side.

Is this an old/new bug?
It's really causing grief cos I need to get this indexing done or find something else to use

;|

[ogrizzo]

Bibble 5 has always shown, now and then, this bug. The best way to correct it is to remove from catalogue the offending images and to reimport them (it's quite fast since ASP won't reimport what is already in the catalogue).

[ChrisC]

I also had this problem in the past and recoverd by creating a completely new catalogue which took quite a while (Bibble XMPs should exist).
Maybe a little bit stupid but:"how can one remove a single image from a catalogue?" (never realised that this is possible)

[ogrizzo]

I also had this problem in the past and recoverd by creating a completely new catalogue which took quite a while (Bibble XMPs should exist).
Maybe a little bit stupid but:"how can one remove a single image from a catalogue?" (never realised that this is possible)

Take note of the folder where the picture lives: Edit|Version|Show master file location
Most often, you'll have many pictures in the same folder showing the same problem; it could be useful to select 'Link to Catalogs' in the Metadata Browser.

If you did not allow ASP to create .xmp files (which you should), write them for your files before removing them.

Remove the picture: Edit|Version|Remove Version
Don't select 'Move master file to trash', of course

Reimport the folder, or just those pictures using drag'n'drop (this would open a queue). Even if the rogue metadata are still there, you usually can remove them at this point. If that doesn't work, you will have to edit by hand the xmp file.

You will lose history on those pictures, of course; but it's still much faster than reimporting the whole catalog.

Ottavio

[andreas]

also you may try from the menu when one of these images is selected:

- save standard xmp for the version
- merge with external metadata

Please give us an info

- if thats works
- perhaps you can give a hint how to get in this situation

There was a keyword bug in b5 which was solved in the latest b5 version and also in ASP. Maybe there is one deeper left...

Andreas

[ChrisC]

Don't select 'Move master file to trash', of course

so obvious - thanks

[goatbeater]

andreas

- save standard xmp for the version
- merge with external metadata

WOW - I'm impressed by this forum...
I posted then went to bed - got up and there were replies, at least 2 looked promising.

I tried andreas's approach on one example and it worked, so I tried on a Genre: Snapshot that had also crept in somehow - no luck so far!
I'd obviously prefer not to remove images and re-catalogue as this becomes less workable as time goes on.

I'll post with any updates...

...and thanks to everybody for the replies

[goatbeater]

andreas

- save standard xmp for the version
- merge with external metadata

darn posted too soon ....

When I got back to Aftershot I noticed that the Genre: Snapshot had appeared in the keyword lists in red.
This had not appeared before either with one or several images selected!

So ... I removed it from the list and Voila! it disappeared and the entry disappeared from the list at bottom right!

So andreas is spot on and this is a workable solution even with tens of thousands of images.
AF still takes a while to process but at least it's AF doing the thinking and the work, not me!

Thanks andreas!
What a cool forum

[I3ilbo]

Hi,

isn't it time to remove this bug? This bug is known for years and makes catalogs nearly unusable

please resolve this bug in ASP!!!!!!

[bos]

- save standard xmp for the version
- merge with external metadata

I tried this and other suggestions (removing and reimporting), but they didn't always work. Sometimes they even created more problems like, adding additional keywords that weren't in the xmp files (they were embedded in the image since who knows when).

In the end I just created a keyword set with the same hierarchy as the troubled one. Selected all the images and removed the keyword set from selection. The funny thing is that it didn't remove the keywords from the whole selection at once, I had to preform the remove action multiple times and each time it removed the keywords from a random number of images.

It's really time-consuming creating all this keyword sets just so I could get around this bug. In general I find it really hard to remove or add one keyword that is common to a group of images, without breaking all the other keywords.

Does anybody have tips about keywords organization, so to avoid running into this bug every 10 minutes when working with keywords hierarchy?

[marbly]

Please report this bug:

https://www.surveymonkey.com/s/ASPFeedback

[lazyknight]

Just had exactly this problem -- to the best of my knowledge, here's a repro:

* Add a keyword to a set of photos e.g. "Location; Egyp; Red Sea,
* Add another keyword in the same hierarchy to a subset of the photos: e.g. "Location; Egyp; Sharm El Sheikh"
* Select all "Location; Egyp" photos in the metadata browser
* Correct the "Location; Egypt; Red Sea" typo, but not the other, and apply.
* Correct the other typo keyword...

... and see the second one remain in the metadata browser, linked to the same photos. The correct spelling will show up in the Keywords panel in the right panel though.

The fix from this thread fixed -- forced .xmp creation, removed version from catalogue, re-imported -- but this is a rather annoying little bug...