Color Class goes away on when a second color class is used

[Kirk Baker]

Kirk - In an earlier post, I stated " It is also not platform specific. Does it on my Mac with Mountain Lion and my Windows 7, intel based machine."

About to go back to an earlier build of PM 5.  This just started with the latest build.  Although the Color Class shows up in the Metadata, the color is not displayed when looking at the tagged images.  Let me know what else you need.  Thanks.

At this point I need something that helps me reproduce the problem.  Every file you have sent me that has had the color class changed actually has the color class data in it and shows up fine for me.

Perhaps a set of steps to follow to reproduce the problem if having the images be on a CF card are necessary to illustrate the problem.

-Kirk

[DCSportsShooter]

Kirk,

How about if I give you access to my machine?  Then you could see for your self. 

To document the problem here it is:

Camera is a Nikon D3s.  Card is a LEXAR 800x 8GB card.

1.  Card goes into the camera and is formatted in camera
2.  Game is shot and specific images are tagged in camera with lock button
3.  CF card is inserted into the machine (MacBook Pro, 10.6.8 )
4.  Images are sorted on tagged images only
5.  Tagged images are viewed and some images are then color coded
6.  The color coded and tagged images on the card are copied to the hard drive on the MacBook Pro
7.  Those images are edited in PS5 and saved back to the directory.
8.  The color class is still there.
9.  The CF card is ejected and put back into the camera.
10.  Game is shot.
11.  Specific images are tagged in camera with lock button
12.  CF card is inserted into the machine (MacBook Pro, 10.6.8 )
13.  Images are sorted on tagged images only
14.  Tagged images are viewed and some images are then color coded with a different color to differentiate between first half and second half.  When looking at the images, the color code used in the first half is now gone on the card.
15.  The color coded and tagged images on the card are copied to the hard drive on the MacBook Pro
16.  Those images are edited in PS5 and saved back to the directory.

That is my process.  I use the color code to insure that I do not re transmit and image on second edits after the game.

Let me know what else you need.  Thanks.

[Kirk Baker]

7.  Those images are edited in PS5 and saved back to the directory.

The directory on the card or on your MacBookPro's hard drive?

-Kirk

[DCSportsShooter]

Hard drive.  Once the images are tagged and color coded on the card, they are copied to the disk on the computer.  Once they are there, all editing, etc, is done on the computer. The images are never moved back from the hard drive to the CF card.

[DCSportsShooter]

Kirk - Still is an issue. Shot basketball yesterday.  Tagged some of the locked files on the CARD with a color code, copied them to my hard drive and then ejected the card.  After the game, brought the card back in and just looked at the Tagged files on the CARD, where there were 10 images that were also color coded.  Those 10 that were color coded in the first half and copied to my hard drive were still tagged but the color coding was gone.

[Hayo Baan]

Sounds like you have some sort of (caching?) issue reading from your card. From your description PM did write the colour code and tag.

A completely different though: are you perhaps applying a stationary pad at ingest? Please check to see whether or not you have it reset the colour code.

HTH,
Hayo

[DCSportsShooter]

Sounds like you have some sort of (caching?) issue reading from your card. From your description PM did write the colour code and tag.

A completely different though: are you perhaps applying a stationary pad at ingest? Please check to see whether or not you have it reset the colour code.

HTH,
Hayo

Nope. Cache is cleared on every log out, with the EMPTY CACHE on LOGOUT.  I also have manually cleared the cache.
I use the IPTC stationary pad, but it is not set to reset the color. 

This is definitely a build issue.  In addition to the color code, when I also set the rating of some of the tagged images, they go away too when the card is ejected and put back in. 

I just reverted back to 4.6.9 and the problem is gone.

[Gregory]

I have the same problem on my MacBookPro
Reader Lexar Prof USB 3.0
Cards - SanDisk ExtremePro
Camera - 1Dx

I mark some files with color classes on the card, sort by color, copy color-marked files to hard drive, and have only about 10 files with color.

[DCSportsShooter]

I have the same problem on my MacBookPro
Reader Lexar Prof USB 3.0
Cards - SanDisk ExtremePro
Camera - 1Dx

I mark some files with color classes on the card, sort by color, copy color-marked files to hard drive, and have only about 10 files with color.

I have also seen this behavior.  Just the last files color coded are the ones that keep the color. The rest go away.

[Hayo Baan]

I have the same problem on my MacBookPro
Reader Lexar Prof USB 3.0
Cards - SanDisk ExtremePro
Camera - 1Dx

I mark some files with color classes on the card, sort by color, copy color-marked files to hard drive, and have only about 10 files with color.

I have also seen this behavior.  Just the last files color coded are the ones that keep the color. The rest go away.

From earlier comments I understood that the files actually do have their colour codes applied, just that PM doesn't seem to display them. To me this really sounds like a (OS?) caching issue. What happens when you clear PM's cache and completely reboot the system?

[Kirk Baker]

We've been able to reproduce the problem and are working on a solution.

Thanks everyone.

-Kirk

[DCSportsShooter]

Thanks Kirk. Looking forward to the fix.

[Kirk Baker]

Thanks Kirk. Looking forward to the fix.

I fixed the problem.  It wasn't actually related to working on camera cards.  It had to do with working with locked files only.  It doesn't matter where they came from, they just had to be locked.

-Kirk

[DCSportsShooter]

Kirk, will you be putting the fix out in an update?  Thanks.

[Kirk Baker]

Kirk, will you be putting the fix out in an update?  Thanks.

Yes, absolutely.  Expect it soon.

-Kirk