![]() ![]() Is that just a horrible practice and I should stop doing it? Right now, I tell C1 to Auto Sync Sidecar XMP: Load. I have a tendency to bounce back and forth between PM and my RAW editor and often make rating/class and metadata changes. But I read somewhere that C1 is fairly taxing when you tell it to write all data changes to the XMP all the time. Getting PM6 to sync color classes and star ratings to C1 was a breeze, that much I expected. Anyways, I could talk about that for a whole chapter of a book, so I wont. Layers are cool but I haven't ever really had a problem with the brush system in LR. LR is fine, catalogs get a bit bogged down when they're huge and I love to print from LR, but I use C1 for tethering in the studio a lot and I like the methodical way the photo editing side is split up, remind me of working with nodes and grades in Davinci Resolve. Last month I decided I'd give C1 a serious try, but today I decided I'd start tackling full shoots with it. I was about to start a separate discussion about PM/C1 workflow when I stumbled across this one. I spent a few hours in Google and really came up short in comparison to PM/LR workflow information and tips/tricks. My main advice for PM-C1 or PM- is to do all metadata work in PM (not a loss, PM is likely the better metadata tool anyway). The PM-C1 combo works for me even though both applications have their quirks. The only way to zero variants is to remove the image from C1 The first variant is only one out of the huge number of possible first renderings depending on how you configured C1, on your presets and on added adjustments (if any). C1 shows variants only, there is no concept of an "original" plus "additional variants" as some users tend to think when they start using C1, images shown are variants. What does indeed confuse a few C1 users is that the first image rendered from an image file is also the first image variant in C1 lingo. C1 in session mode and C1 in catalog mode has always had the variants as non destructive internal edit instructions, I have yet to see C1 create additional copies of "the file" which I take to mean "additional copies of the original image file", not just additional (internal) cache files. I have used C1 regularly since its version 7 without seeing what you describe. I was thinking of trying Affinity Photo, but their trial period is only 10 days, and when I have had a Serif product in the past, I got pestered with sales calls to buy their other products or upgrade. There seems to be better functionality in some of the less expensive editors. So again, there is nothing non-destructive about the variants.ĭNG files saved with C1 have no embedded preview, or at least not one that can be read by Photo Mechanic.Īgain, I just started the C1 trial, and perhaps there are solutions to the above problems. Variants are just additional copies of the file, not C1 internal editing instructions. The plug-in changes are not incorporated back into C1. So C1 just creates a new file based on the edits you have done thus far. It does this anyway, if the plug-in is open, as that is where the edits are saved. It appears this only works if the plug-in is already running, otherwise C1 just creates a copy of the file in whatever format that was specified with an incremental number added to the file name. I have set up several plug-ins to be able to Edit with from C1. There is no Nikon/Sigma combination for the camera and lens that I used. The C1 lens profiles that I am looking at for this particular image show the lens profile for a Canon, and other Sigma lenses for Nikon. ![]() The image I am working was taken with a Nikon camera and Sigma lens. Other issues I have found in 1 short time of trialing: Fortunately they are all in a sub-folder of the folder containing the images. There is no way to prevent C1 from creating these, and it does not delete them when you close. ![]() The average of this 4 is about 1.5MB per image. One is a settings file (cos), another is a thumbnail (cot), then there are 2 proxy files for each image (coffee and cop). That said, even in "Session"mode, it will create 4 files for every image in the directory of the file you are editing, even if you only open 1 image. I have not been able to get C1 to launch with the file I want to edit using PM's Edit with function. I don't plan to use it for cataloging, only as an editor. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |