IPTC data and Canon cameras
I'm trying to improve my workflow and develop a proper searchable image archive, but I've noticed some problems with the way my Canon files and Capture One Pro handle IPTC data.
I own a 1Ds, but I still use a D60 sometimes for personal sfuff and for smaller jobs for websites, etc. I also use Downloader Pro to transfer files from the CF card and to automatically add IPTC info to the RAW files. When I do this with the 1Ds the IPTC data is visible in C1 and is transferred to the converted files as well. The IPTC data in the RAW and converted files is also visible in Breeze Browser and Bridge, so everything looks good.
However, with the D60 the IPTC data is not visible in C1 and it is not transferred to the converted files. It is visible in Breeze Browser and Bridge and files converted with Adobe Camera Raw also include the IPTC data. So the problem seems to be with the way C1 handles the D60 files and I'm assuming it has something to do the .thm files.
I know the D60 is getting pretty old, but it's still a good camera and if there is a way to solve this problem that would be great. If I have to replace it, will this be a problem with any other Canon cameras?
Thanks,
Andrew
I own a 1Ds, but I still use a D60 sometimes for personal sfuff and for smaller jobs for websites, etc. I also use Downloader Pro to transfer files from the CF card and to automatically add IPTC info to the RAW files. When I do this with the 1Ds the IPTC data is visible in C1 and is transferred to the converted files as well. The IPTC data in the RAW and converted files is also visible in Breeze Browser and Bridge, so everything looks good.
However, with the D60 the IPTC data is not visible in C1 and it is not transferred to the converted files. It is visible in Breeze Browser and Bridge and files converted with Adobe Camera Raw also include the IPTC data. So the problem seems to be with the way C1 handles the D60 files and I'm assuming it has something to do the .thm files.
I know the D60 is getting pretty old, but it's still a good camera and if there is a way to solve this problem that would be great. If I have to replace it, will this be a problem with any other Canon cameras?
Thanks,
Andrew
0
-
I am finding the same problem with 10D files with 3.7.5 0 -
Yeah, C1 seems to cause a lot of roadblocks when it comes to asset management, keywords, iptc, data, etc.
I posted in the topic below about problems adding iptc data to 30D files in Bridge and then having them disappear in C1.
http://forum.phaseone.com/viewtopic.php?t=27610 -
Interesting that it occurs with 30D also. I thought it may have been attributed to the crw/thm file combination and working fine with the cr2 files, but apparently not.
I will probably just assign the generic IPTC data for raw archives at download, and add it again in the DAM for the processed files (after C1) since I would add categories and keywords anyways.0 -
Same problem here with a Canon 10d.
Note that the problem does not happen with version 3.5.1. It is there since 3.7.1 and has not been sorted out. I am forced to stick to 3.5.1.
I must say that were it not for C1 being a better converter I would switch to Adobe Ligthroom which at the moment is even free!
They should have really patched this a long time ago (and give the patch for free).Too bad.
Giulio0 -
My understanding from the Lightroom forum is that it is not a very good DAM. I have downloaded it but haven't played with it yet. For now, my tools are still:
Downloader Pro (ingest)
Breezebrowser Pro (cull and tag)
C1 Pro (conversion)
PSCS2 (edit)
IMatch (DAM)
Qimage (prep or print)0 -
I was just talking about raw conversion.
My workflow is
DIM (file copying to folders from card).
Imatch (DAM and Metadata including IPTC)
C1 (WB, levels (I expose to the right whenever possible,so have to translate in C1),raw conversion)
PS (all the rest)
My problem is that if I use higher versions of C1 than 3.5.1 I loose all IPTC info. This is not the case with lightroom.
giulio0 -
I agree they should patch it since it use to work in 3.5. I understood your original reference to LR was re: RAW development. I was just hoping LR might replace several tools for me, but it doesn't look promising. The 'best of breed' approach is still my preference and the tools are getting better at inter-tool intergration.
Question on your workflow. I see you catalog and add IPTC with IMatch before C1 and PS. Therefore, the C1 bug is a major problem for you.
Do you do all your IPTC and DAM info (including per image info) prior to developing in C1?
Do you recatalog the developed files into IMatch?
Thx, Brian0 -
Question on your workflow. I see you catalog and add IPTC with IMatch before C1 and PS. Therefore, the C1 bug is a major problem for you.
Indeed. It makes sense to me assigning all keywords, location, etc at the earliest possible stage and be done with it. Also C1 IPTC editor is a major pain!Do you do all your IPTC and DAM info (including per image info) prior to developing in C1?
Prior to importing in C1. I add no info in C1.Do you recatalog the developed files into IMatch?
My tiff files have the same name as the raw, just a different extension. I have not tried it yet, but I understand IMatch can propagate categories and keywords. I think it should be straightforward to ask it to do it between files with the same name (I think I have read it somewhere).
best
giulio0 -
My current workflow (detail) is as follows:
DLPro - "automatically" assign job code, rename files to JC_exif date_orig file #, create directory structure (JC, JC/Develops, JC/Proofs, and JC/DNG), convert copy to DNG for second archive, assign generic IPTC data (non-image specific) in one process step.
BBPro - Review, cull, compare, tag, organize, etc. Produce HTML gallery for website (if no editing required for online gallery quality).
C1P - Develop
PSCS2 - Edit
IMatch - catalog, category, keyword, per image IPTC (here I can incorporate the generic IPTC as well so the 3.7 bug is minor)
Qimage - Prep for upload to lab or print locally.0
投稿コメントは受け付けていません。
コメント
9件のコメント