Author Topic: Color Class not saving  (Read 6016 times)

Offline piccyman

  • Newcomer
  • *
  • Posts: 4
    • View Profile
Color Class not saving
« on: September 03, 2012, 03:20:01 PM »
I am running Photo Mechanic version 5.0, build 13217  and I run Mac OS X 10.8.1 on my Intel-based Mac

This should help you recreate the problem,

 If you open up an image using the i button, update the iptc data and then select the command button and a number to set the colour, or just set it via the colour class bar, then save using the save and move forward button, the color class does not save.
The color class save if you don't update the iptc data, but doesn't if you do.

It worked in v4, as it was part of my workflow to identify images with updated iptc data.
« Last Edit: September 03, 2012, 10:53:58 PM by piccyman »

Offline Major Tom

  • Newcomer
  • *
  • Posts: 12
    • View Profile
Re: Color Class not saving
« Reply #1 on: September 04, 2012, 09:54:13 PM »
I find that same behavior, running Windows 7 and same PM build.

Offline Rguzmanphoto

  • Full Member
  • ***
  • Posts: 158
    • View Profile
Re: Color Class not saving
« Reply #2 on: September 05, 2012, 05:48:52 AM »
Doing the same thing on Mac running 10.6.8

Offline piccyman

  • Newcomer
  • *
  • Posts: 4
    • View Profile
Re: Color Class not saving
« Reply #3 on: September 18, 2012, 01:09:57 AM »
I have decided to switch back to v4.6.9 for now, this problem is disrupting my workflow too much and I am unable to find a workaround, hopefully it will get fixed in the next update

Offline Juerg

  • Sr. Member
  • ****
  • Posts: 260
    • View Profile
Re: Color Class not saving
« Reply #4 on: September 18, 2012, 01:54:11 AM »
Same issue here on Win 7 64-bit

And not only the color class, also rating and tagging does not stick if at the same time ITPC data is updated.

Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 24730
    • View Profile
    • Camera Bits, Inc.
Re: Color Class not saving
« Reply #5 on: September 18, 2012, 07:01:23 AM »
The next build will fix this issue.

-Kirk