Proper metadata management is important for optimal compatibility and longevity. Many RAW processors out there have a somewhat sub-optimal metadata handling. When you add/edit metadata, it is usually best to do it in IMatch. You can specify one of the versions to be used as the Visual Proxy for the RAW, which allows you to see the RAW in IMatch as it looks in your RAW processor. IMatch can then keep metadata synchronized, show you the versions you have created, you can automatically stack versions etc. you produce from your RAW file as versions of that RAW file. This unique concept allows you to tell IMatch to consider the JPG/PSD/TIFF. If you don't use DNG, but keep the original RAW file and one or more renditions of the file you produce in your RAW processor separate, you should setup a file version in IMatch: File Relations: Versioning This is done in IMatch by defining a buddy file relation: File Relations: Buddy Files The other application may produce buddy/sidecar files (for settings or similar) which you will want to keep together when renaming, moving, copying or deleting files in IMatch. Other C1 users here in the community can surely help. Although I remember that C1 does not really support the Windows standard protocols for "file open" and hence this may not work that well. Which explains how you can open files from IMatch in other applications. In general, to cooperate with other applications, there are some points you want to check: Remember that you can use the fully funtional trial version of iMatch to test all this. I hope this helps a bit and maybe you could give us more details what exactly you want to know. It's more complicated and more work, but it works for me. In iMatch I have defined a buddy file relation so that iMatch will use the processed JPG for displaying the raw files (see attached screenshot). What annoys me very often is that when I re-process an image in C1, there is no option to simply overwrite the old JPG. You can, of course, use any other path to put them in and you can use a lower resolution JPG. What I do is process the images, once I'm satisfied with the treatment, to export to a full size JPG in a subfolder named "JPG" under the folder containing the raw files. Now, with C1 it's gotten much more complicated, but it works. The DNG workflow had the advantage (for me) that I only had to manage a single file for each image, which included a full size preview which iMatch displayed in thumbnails and viewer, so I could see the "developed" version of the images. I have only been using C1 for some months now, my old workflow being exclusively with Bridge/ACR und all DNG files.įirst, I am not a professional photographer and I don't submit images to agencies or sell them to clients, so you may have very different requirements.
0 Comments
Leave a Reply. |