Metadata
I employ metadata in my workflow and the CO method is not working for me. Up until I started using it, I would create a template in Adobe Bridge and apply it to my RAW files. If I look at the files in any program the data is there but...not in CaptureOne? Why is that?
Further, I tried to import one of the templates I made into CO but it won't import.
Further, I tried adding my licensing information into the Rights Usage Terms field but it does not allow me to Paste any text into it.
Further, I tried typing my two paragraph licensing info into the same field but it only permits a certain number of characters. What's up with that?
I'm guessing that CO attaches this metadata to the XMP file which doesn't do me much good if it gets separated from the RAW file.
Please help me resolve this.
ON A SIDE NOTE: If I were to update something like my contact info in the metadata in say Bridge and I was using Lightroom, Lightroom would see the update and happily allow me to:
a. Import the update - which would promptly throw out any editing I did to the file and make me start from scratch
b. Allow me to keep what Lightroom already has applied which keeps my edits but doesn't update anything I changed
At least with CO it didn't look at my metadata at all, that's not a good thing by the way. It seems to me that the software companies need to figure out a way to separate image editing info from file metadata. If someone gives me a file that has a bunch of metadata filled in that was input through some third party application, what this tells me is CO will ignore it.
I'm sure I'm confused and just not following instructions so please, enlighten me.
Thanks for your help.
Further, I tried to import one of the templates I made into CO but it won't import.
Further, I tried adding my licensing information into the Rights Usage Terms field but it does not allow me to Paste any text into it.
Further, I tried typing my two paragraph licensing info into the same field but it only permits a certain number of characters. What's up with that?
I'm guessing that CO attaches this metadata to the XMP file which doesn't do me much good if it gets separated from the RAW file.
Please help me resolve this.
ON A SIDE NOTE: If I were to update something like my contact info in the metadata in say Bridge and I was using Lightroom, Lightroom would see the update and happily allow me to:
a. Import the update - which would promptly throw out any editing I did to the file and make me start from scratch
b. Allow me to keep what Lightroom already has applied which keeps my edits but doesn't update anything I changed
At least with CO it didn't look at my metadata at all, that's not a good thing by the way. It seems to me that the software companies need to figure out a way to separate image editing info from file metadata. If someone gives me a file that has a bunch of metadata filled in that was input through some third party application, what this tells me is CO will ignore it.
I'm sure I'm confused and just not following instructions so please, enlighten me.
Thanks for your help.
0
-
Please sync Metadata to XMP.
Capture One is read only and we will not write the metadata to the RAW, only to a sidecar XMP.
You can then change the sync settings in Capture One to automatically read this file should it be edited in another software, your changes are then reflected in Capture One as you require.0 -
If you sync to XMP in Lightroom it will create an xmp file for each image file. This can then be read by Capture One (as per Drew's update) so that your metadata will show up in CO also. You can manually force LR to write out the xmp by selecting all the files you want included and then hitting cmnd+s.
Note that development edits won't get transferred using this method. Some simple edits (e.g. crop, exposure etc) can be transferred if you import the LR catalog into CO. This will also take all the metadata across.
LR will allow you to update / sync metadata without losing any development changes, just don't re-import images or you will lose changes which I think is the mistake you were making.0
Post ist für Kommentare geschlossen.
Kommentare
2 Kommentare