All I want to see in PSU is exactly what I have keyworded, color tagged and star rated in Capture One. Nothing more - please. I cannot figure out how to turn versioning off - completely. I have been getting very different results in PSU than what I have in Capture One and have spent a couple of days tearing my hair. It appears to be the wonderful versioning in PSU which I really don't want to use or need.
I do not want to see that when I tag the tif file and not the raw file in Capture One that in PSU both are tagged. I do not want other versions of the raw, tif or jpeg or whatever also group and tagged. Just plain vanilla - I tag a tif in CO with green 5 star and PSU shows only that tif with green 5 star. I tag a raw in CO with yellow 3 star and PSU shows only that raw with yellow 3 star.
Please help me to understand what should be checked and unchecked in the preferences. I have tried several different things - one of which versioned every image in the folder to one image, yikes!
Thank you very, very much in advance.
Bob
How to avoid versioning? HELP
Re: How to avoid versioning? HELP
Color labels and ratings are unrelated to versioning.
But if you don't want files to be versioned then don't use that option. In the import module you can switch off the option to create versions on import. If you use Verify Folders then switch off the option to create versions.
But again, color labels and ratings are not version sets related.
Catalog Labels are what is shared among the full set.
But if you don't want files to be versioned then don't use that option. In the import module you can switch off the option to create versions on import. If you use Verify Folders then switch off the option to create versions.
But again, color labels and ratings are not version sets related.
Catalog Labels are what is shared among the full set.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: How to avoid versioning? HELP
Hert
Thanks
Sorry for being such a knot head as I didn't even see that check box.
If you could assist me a little more please-
When I did the original import none of the color tags showed - the star ratings did except for tif's (that's my next question) - I had to use the verify folder command and still no color tags showed up. I eventually selected all images in the folder and then Rt click/Read metadata from file and then the color tags showed up, however, again except for tif's.
Also if I change or add a color tag and/or star rating in Capture One and then sync metadata in Capture One it correctly writes to an xmp file for all modified files including tif's. In PSU I have to go through the same verify then rt click read metadata and PSU picks it up again except tif's..
How do I get the tif files in PSU to display display the color tag and the star rating? These are my most important image files and not one tif in PSU has a color tag or star rating unless I apply individually in PSU.
Thanks
Bob
Thanks
Sorry for being such a knot head as I didn't even see that check box.
If you could assist me a little more please-
When I did the original import none of the color tags showed - the star ratings did except for tif's (that's my next question) - I had to use the verify folder command and still no color tags showed up. I eventually selected all images in the folder and then Rt click/Read metadata from file and then the color tags showed up, however, again except for tif's.
Also if I change or add a color tag and/or star rating in Capture One and then sync metadata in Capture One it correctly writes to an xmp file for all modified files including tif's. In PSU I have to go through the same verify then rt click read metadata and PSU picks it up again except tif's..
How do I get the tif files in PSU to display display the color tag and the star rating? These are my most important image files and not one tif in PSU has a color tag or star rating unless I apply individually in PSU.
Thanks
Bob
Re: How to avoid versioning? HELP
That is certainly not "correctly"Capture One it correctly writes to an xmp file for all modified files including tif's
.As per the XMP standard, metadata for TIF files MUST be stored inside the TIF file and not in a sidecar file. If C1 writes metadata for TIF to a XMP sidecar then that's not good. You can use "right click -> Run Script from Repository -> Metadata -> Import from XMP sidecar file" to import such a file. Please let C1 know that they should write XMP embedded in the TIF file.
There's golden rule: NEVER use different software to update metadata in the same files. When first starting to use Photo Supreme it becomes painfully visible when metadata is not correct. Photo Supreme does have the means to fix such metadata issues caused by other software (like "Convert Metadata to XMP" and import XMP from sidecar files), but if you continue to use other software (in your case C1) to update metadata many efforts that you put into fixing your metadata will be in vain and you will always run into issues. Therefore use the golden rule: only use one software to change metadata. C1 (and DXO for that matter) is a RAW editor. Use it for what it was built for: editing RAW files. Except for Lightroom, all RAW editors that I know of mess up metadata in some way.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: How to avoid versioning? HELP
Hert
It is not a matter of continuing to use other software to update metadata. It is a case that I want to use PSU as my primary catalog for Capture One and want to have all of my color and star ratings and keywords applied from CO to PSU without rekeying. Currently only the keywords came over in my test imports to PSU. I then, as you can see, tried writing CO metadata to xmp files - with only partial success.
If this is possible please give me a step by step outline as I have tried numerous things. I am sure there must be many that have this same question and they must have been successful???
Thanks in advance.
Bob
It is not a matter of continuing to use other software to update metadata. It is a case that I want to use PSU as my primary catalog for Capture One and want to have all of my color and star ratings and keywords applied from CO to PSU without rekeying. Currently only the keywords came over in my test imports to PSU. I then, as you can see, tried writing CO metadata to xmp files - with only partial success.
If this is possible please give me a step by step outline as I have tried numerous things. I am sure there must be many that have this same question and they must have been successful???
Thanks in advance.
Bob
Re: How to avoid versioning? HELP
Hi Bob,
If C1 writes color labels and ratings to an XMP sidecar file for TIF then you should import that XMP file separately. Did you verify that it writes this info into a XMP sidecar file for TIF? If so then follow my instruction as mentioned above.
If C1 writes color labels and ratings to an XMP sidecar file for TIF then you should import that XMP file separately. Did you verify that it writes this info into a XMP sidecar file for TIF? If so then follow my instruction as mentioned above.
If that doesn't help then try right click on the thumb -> Metadata -> Convert Metadata to XMPYou can use "right click -> Run Script from Repository -> Metadata -> Import from XMP sidecar file" to import such a file.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: How to avoid versioning? HELP
Hi Hert,
Are sure that versionning only affects catalog Labels. Is it new. In my experience it was synchronising most xmp metadata:
this how I ended up with all my stacked dng version of a photo being exactly similar. The develop metadata of lightroom were synchronised to be the same across all the versions.
I had several version of my photos as DNG files with develop instruction stored in the XMP. I would view the file in PSU through the embedded preview from lightroom. SO I would not find out that this synchronisation was taking place unless I opened the photo again in lightoom to further edit it.
This the one thing that made me give up PSU but if that is fixed I will strongly think about coming back!!!
Are sure that versionning only affects catalog Labels. Is it new. In my experience it was synchronising most xmp metadata:
this how I ended up with all my stacked dng version of a photo being exactly similar. The develop metadata of lightroom were synchronised to be the same across all the versions.
I had several version of my photos as DNG files with develop instruction stored in the XMP. I would view the file in PSU through the embedded preview from lightroom. SO I would not find out that this synchronisation was taking place unless I opened the photo again in lightoom to further edit it.
This the one thing that made me give up PSU but if that is fixed I will strongly think about coming back!!!
Re: How to avoid versioning? HELP
Only labels are shared among a version set. But there's a feature to cascade metadata from a version to the entire version set.
Maybe you've used that.
But if you're uncomfortable with Versioning then Stacking may be a better match for you. With Stacking the images are grouped while each image remains an individual managed asset.
Maybe you've used that.
But if you're uncomfortable with Versioning then Stacking may be a better match for you. With Stacking the images are grouped while each image remains an individual managed asset.
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message
Re: How to avoid versioning? HELP
Thank you Hert.
Unfortunatelly When that happened the option to cascade the metadata was not used.
I could do with stacking, but I liked the idea of versionning being different from stacking. I think your software is maybe not the most stable but definitively the best I have tested in terms of usability. For sure you have managed to give access to a huge number of metadata field while keeping it simple natural and well organized.
Unfortunatelly When that happened the option to cascade the metadata was not used.
I could do with stacking, but I liked the idea of versionning being different from stacking. I think your software is maybe not the most stable but definitively the best I have tested in terms of usability. For sure you have managed to give access to a huge number of metadata field while keeping it simple natural and well organized.
Re: How to avoid versioning? HELP
Hert,
In reply to your advice to me:
1st CO definitely will not write to a raw file and probably never will. So to get my metadata to PSU I will have to have CO sync metadata to all raw images I want in PSU - essentially writing to xmp files. This I knew and works perfectly with PSU.
2nd for tif files - I was color and star tagging after creation either within CO or roundtripping to PS and back. Virtually all my tifs are like this as often I decide after the fact the final star and color. Apparently CO will not write the metadata to the tif after the fact. However, I find the metadata can be written to the tif as it is being created either in a roundtrip or within CO and this will be picked up by PSU after a verify. Yay! The big downside is that I now have to change my workflow and either decide before hand on the rating and color tags or after the fact if I want to change them I then have to recreate a new tif with the new color and star and subsequently delete the previous tif. ARRGGH!!
Thanks for your patience with me. I knew that is was the standard to write metadata to the tif and because I could see and read the metadata in CO it never twigged that they were not writing it to the file after the fact. I thought it had to be some lack of communication between PSU and CO.
Next question is - can PSU automatically pick up these new tif files and also xmps for the raws or do I have to verify the folder each time I want the changes reflected in PSU which is time consuming and an extra step.
Thanks
Bob
In reply to your advice to me:
I have found an answer - not a prefect solution, however, I can make it work.Hert wrote: 22 Dec 20 9:11 Hi Bob,
If C1 writes color labels and ratings to an XMP sidecar file for TIF then you should import that XMP file separately. Did you verify that it writes this info into a XMP sidecar file for TIF? If so then follow my instruction as mentioned above.
If that doesn't help then try right click on the thumb -> Metadata -> Convert Metadata to XMPYou can use "right click -> Run Script from Repository -> Metadata -> Import from XMP sidecar file" to import such a file.
1st CO definitely will not write to a raw file and probably never will. So to get my metadata to PSU I will have to have CO sync metadata to all raw images I want in PSU - essentially writing to xmp files. This I knew and works perfectly with PSU.
2nd for tif files - I was color and star tagging after creation either within CO or roundtripping to PS and back. Virtually all my tifs are like this as often I decide after the fact the final star and color. Apparently CO will not write the metadata to the tif after the fact. However, I find the metadata can be written to the tif as it is being created either in a roundtrip or within CO and this will be picked up by PSU after a verify. Yay! The big downside is that I now have to change my workflow and either decide before hand on the rating and color tags or after the fact if I want to change them I then have to recreate a new tif with the new color and star and subsequently delete the previous tif. ARRGGH!!
Thanks for your patience with me. I knew that is was the standard to write metadata to the tif and because I could see and read the metadata in CO it never twigged that they were not writing it to the file after the fact. I thought it had to be some lack of communication between PSU and CO.
Next question is - can PSU automatically pick up these new tif files and also xmps for the raws or do I have to verify the folder each time I want the changes reflected in PSU which is time consuming and an extra step.
Thanks
Bob