Structured Keywords

[Alberto]

Good morning,
I've been using the PhotoMechanic Plus trial for a while. Compared to Photomechanic 6, searching for a word in the structured Keywords is definitely very slow. (Sometimes it takes more than 1 minute) Is this just my problem or is it generalized? I use Apple Silicon with 64GB of memory. Thank you very much.

[ahoward]

The Structured Keywords Panel hasn't changed at all from Photo Mechanic 6. There should be no difference in performance. If you launch Photo Mechanic 6 and do a search the Structured Keywords Panel, does it locate the word you are looking for immediately?

[Alberto]

Yes, it's immediate. I imagined nothing had changed. I just don't understand what it could be.

[ahoward]

If you want, you can send us your structured keyword file and we could load it on one of our machines to see if we can reproduce the issue. I tried with the default set and experienced no problem. The structure keywords file is available at:

~/Library/Preferences/com.camerabits.PhotoMechanic/StructuredKeywords_UTF-8.txt

If you don't want to share it here you can send it to support@camerabits.com

You could also provide a screenshot of the Structured Keywords Panel before you perform your search so we can match up our settings and see if your combination of settings is somehow causing the issue.

[Alberto]

Thank you very much. I have sent everything to support@camerabits.com.

[ahoward]

Hi Alberto. I'm not seeing a ticket from you. Can you send it again?

[Alberto]

Hi,
no problem I send here.
The version of MacOs is Sequoia 15.4.1
Tks

[ahoward]

Can you give me an example of a search term you are using that produces this issue?

[Alberto]

Any word searched usually produces the same problem. I attach an example

[ahoward]

Any word searched usually produces the same problem. I attach an example

I sent you an email with a link to a build to try that might perform better here. Please check your inbox and let's continue the conversation there.

[ahoward]

For anyone else that might encounter this issue, Alberto confirmed that the build that I sent him fixed the issue. The next build that we release will include this bug fix.