メインコンテンツへスキップ

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Please Help!! Weird Rating disappearing issue in Cap 12!!

Kim Hardy
Hi guys perhaps it's just me because I cannot find this issue mentioned elsewhere..

Best description of this issue please watch the video here!

So as you can see the ratings just simply disappear, no other setting as far as I can tell are effected. I tried a different keyboard and I also loaded up Cap 11 to see if it was happening also I've reseted all custom keyboard shortcuts. No luck so far and I'm really at a loss!

Any ideas?

Would really appreciate your help,

Kim
0

コメント

6件のコメント

日付 投票
  • Kim Hardy
    VIDEO LINK: https://www.youtube.com/watch?v=fEFSHrgwMmw
    0
  • Paul Steunebrink
    I heard this from another user here as well. Contact support.
    0
  • OddS.
    [quote="NNN636258116873803865" wrote:
    ...So as you can see the ratings just simply disappear, no other setting as far as I can tell are effected.


    Long shot, but is C1 reading and updating the rating from metadata on file, embedded in the image file or sitting in a XMP sidecar file? Check (Edit) Preferences->Image, Auto Sync sidecar XMP. Set it to None if it is not already. The Auto "Load" setting may possibly cause C1 to read rating (and more) from another source.
    0
  • mli20
    ...
    ...without informing the user that it sees conflicting metadata?

    MLI
    0
  • OddS.
    [quote="mli20" wrote:
    ...
    ...without informing the user that it sees conflicting metadata?


    I believe C1 would normally issue a conflict warning. Additions and changes to a major software release, as v12.0 is, may have minor unintentional side effects that needs to be ironed out. An ill placed call to "load metadata" is all it takes in this case, but I have no idea what causes the issue. I was just trying to provide potentially useful info to the OP. What about yourself?
    0
  • mli20
    [quote="OddS" wrote:
    [quote="mli20" wrote:
    ...
    ...without informing the user that it sees conflicting metadata?


    I believe C1 would normally issue a conflict warning. Additions and changes to a major software release, as v12.0 is, may have minor unintentional side effects that needs to be ironed out. An ill placed call to "load metadata" is all it takes in this case, but I have no idea what causes the issue. I was just trying to provide potentially useful info to the OP. What about yourself?

    Asking a simple question.

    MLI
    0

投稿コメントは受け付けていません。