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

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

Some photos show the eye-icon, for not changeable photos without any reason. How to change this?

コメント

8件のコメント

  • Ian Wilson
    Moderator
    Top Commenter

    It may be that they are not in a supported format (perhaps a greyscale TIFF). Or it may be that they are too small - see the release notes here which show that 512px is the minimum size that can be edited. (Under File Size Limitations, near the end of the article.)

    Ian

    0
  • Ulrich Schifferings

    Hi Ian,
    ok... thank you. I thing you got the point.
    All related photos are small scan of historic photos. They are below 512px.
    Sad is, that it is even not possible to change the metadata from these files.

    Thank's for your advice.

    0
  • Ian Wilson
    Moderator
    Top Commenter

    No, you can't even do that. I would find it helpful to be able to at least add keywords.

    Ian

    0
  • Ulrich Schifferings

    Hi All,
    these unchangeable images are still an issue for me.
    Ian told me that images below 512px can't be changed.
    Some of my images were below 512px, so he was right.

    Because I have to keep these images and want to get rid of formerly used keywords I increased the pixels by exporting these images (using capture one) with a fixed width of 1500px.
    I replaced the original image at the original place using the export function.
    After that capture one shows the enlarged pixel size correctly in the metadata of the file.

    Unfortunately the "read only" icon is still there and the image still can't be changed.
    I tried to snyc the folder again, synced the metadata again, closed and reopend capture one.

    Nothing helped. Capture one still says these images are not editable.
    Exporting the image to a diffrent name leads to a new, editable image.

    Because of the amaout of images, it is not thinkable to export all these files to diffrent names, delete the originals and rename the new files to the old name. This wouldn't work.

    Any idea how to get rid of this f*** read lony icon for the enlarged images?

    Thanks for help
    Ulrich

     

    0
  • SFA

    Ulrich,

    Apart from the size consideration, are the images also "colour" rather than greyscale?

    Greyscale is not supported by C1 as it requires a colour based processing space to function.

    Are the images in a catalog?

    Are there any edits for the images other than the keywords?

    Realistically the best option for removing embedded keywords in original files would be to use an EXIF editor outside C1. 

    In the first place if the KWs are embedded in the original file (no matter what size, etc.) C1 will never change them. So no matter what you do in C1 the KWs will not disappear. C1 never makes changes to an original file.

    Within C1 there is an edit instructions "file" (easily found for a session, not so readily visible for a catalog) that contains ALL the edit information including any added Keywords. It also includes basic data about the source file and, I suspect, some indication of editability based on the initial "import" or "first read" assessment. There are a couple of fields that look like possible candidates for such an identifier but the names are not explicit for such a purpose and the available valid values unknown.

    Since all C1 added data uses this Edit Instruction set the concept of allowing partial edit of certain file types for certain content fields is not so easy as a "turn on and off".  And in any case, if the KW's are embedded in the original file it would make no difference anyway since C1 will always look for KWs embedded in files.

     

    That said there may be some benefit in reviewing your Preferences settings related to metadata. The link below is to one part of the set of User Guide articles related to Metadata availability and manipulation. It's not an area where I have in-depth knowledge. It is probably of more interest to people importing from another application or sharing images between applications. However, there may be a way of suppressing the use of embedded KWs without deleting them from the source file.  

    On the other hand, this subject comes up a lot in the forum and so far I cannot recall seeing anyone propose a full solution based on metadata options. Perhaps I missed it.

     

    Metadata in XMP sidecar files – Capture One

     

    0
  • Ulrich Schifferings

    Thank you SFA!
    The images are colored (only very few are not) and have been processed with lightroom in the past.
    I will read your adviced article but I gess this stuff is fare more complex then I hoped...

    0
  • Ulrich Schifferings

    By the way,
    I copied the file I enlarged to a different folder and imported it there to capture one.
    It is editable in the same moment, so, I guess there is a read only flag in the C1 Database that is unchangeable once it has been set.
    For C1 the copy at a different location is new to C1 and therefore it checks if it is editable when importing, but once C1 decided it is not editable, it will not change this status any more....

    1
  • SFA

    Ulrich,

    I think that is a correct assessment. 

    I have some thoughts about how one might work around the problem within C1 BUT they would involve creating new files and, in your example, enlarging and then reducing the size and that would not really help the jpg quality. That may not always be important for small files but for larger files, it would probably not be a great idea.

    It could be a workaround (if it would work) for some files from time to time but probably not a great approach for a large number of files.

    However, if the problem is related to embedded keywords in the original file and the original file is still retained in the catalog or session then the KWs will still be discovered every time the file is "discovered" 

    Creating and saving a NEW version of the file WITHOUT the keywords and have only that version in the catalog or session would resolve the problem. Whether that is acceptable in terms of file archive management has to be a personal decision by the file owner!

    0

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