How to duplicate instead moving when dragging files to another folder ?
-
I think this is not supported and I really don't see any benefit of duplicating a raw file.
Because C1 never modifies a raw file (all adjustments and metadata changes are kept in the database), there is no need to keep multiple copies of a raw file. In C1 this is done with variants.
0 -
Mario is correct.
If you can describe your Use Case someone may be able to make some suggestions about workflows to use to achieve your desired results.
Knowing whether you use a Catalog or Sessions could influence the suggestions.
0 -
It sounds like you want file(s) to show in several folders. Capture One doesn't duplicate files—it moves them. However, C1 can clone images and you can have the clones show in multiple albums or projects or whatever. But you'll still have only one original file. If you want to do different edits on the same image, create new variants, either by creating a new variant (i.e. starting with no adjustments) or cloning an existing variant (i.e. starting from a processed image) and go from there.
If you really must have duplicate original files, you'll have to create them in Finder, then Synchronize the folder in Capture One and have Capture One move the duplicate file to wherever you want.
Personally, I think duplicating files is adding needless complexity, as you'll then have multiple original files to keep track of and then have to remember what you did to which file. I find working and filing different variants to be more than adequte.
0 -
Abbott, cloning images can be misunderstood as copying images. And variants of an image can only be duplicated to another collection/album by duplicating the source and the variant images, but these variants are not independent. Meaning, if I move an image with two variants to another collection, I then will have three new images in the new collection, but all are connected together. I cannot edit a variant No. 2 of image 1234 in one collection and edit the variant No. 2 of image 1234 in the other collection in a different way. Some apps can copy or clone variants. Copying means: same source RAW, different edits possible without showing up the parent RAW with all of it's child variants. Cloning is: same source RAW, but for different edits you'll need another clone, and wherever you want to add one of the clones, all other variants will show up as well (of the same RAW).
In Aperture both possibilities were doable, but C1 is a bit constrained in this aspect of independent variants of the same RAW.
Like Mario, I also don't see a benefit of copying RAW files. But I do understand better, why the DAM part of C1 is the way as it is, as users are sort of allergic against learning how to use it.
0 -
I cannot edit a variant No. 2 of image 1234 in one collection and edit the variant No. 2 of image 1234 in the other collection in a different way.
You want to edit the same variant (No 2) in different way in two different collections? Or did you mean edit variant #2 in one collection and edit variant #3 in another. If the later you can do it with a little work. Give each variant a unique keyword. Create a smart album that filters on the keyword you just created. Only the variant with the keyword will be in the smart album. Repeat and modify as necessary.
I tend to use smart albums over regular albums and assign a keyword to the images I want to show up in the album. It's easy to clone a variant and edit the keyword in the clone to move it to a different smart album.
0 -
Difficult to explain, Marco, but your second option was the right one I failed to explain. I want from the same RAW two different variants and use one of each in a different collection/album. I don't need to show up the RAW in another way or with another child variant in two different collections. Should not be too hard. But is impossible in C1.
This ado with keywords and smart collections is simply too much circumstances for a simple operation like this. Especially when I need different collections, maybe for different customers. And don't want to mix and mess up stuff which doesn't belong in a particular collection.
Simple sample: From one shooting session I come home with mostly landscape oriented images. But they have enough reserves to crop portrait oriented images out of it. In C1 it's impossible to create two collections (landscape and portrait, i.e.) from the same images without having both variants in both collections. Using keywords to clear up what the C1 devs "forgot" to implement is in my eyes an abuse of keywords. And calling for other problems with them. But this is the reason why people want to duplicate RAWs.
Look, I'm working on a daily basis with a real content management system. This kind of stuff is simply normal and one of the easier operations to perform. Like I said, on a real content management system, not a wannabe DAM. But I realize a lot of users have a different background and this kind of needs is rather exotic. Most people prefer to copy as much as they need to work with the same image and edit it differently. Although leaving one source image and saving the edit operations would save diskspace. Like in "single-source-publishing", another buzzword which in reality usually doesn't keep it's promise.
0 -
Hi guys !
Thanks for answering and all the support. I am Digital Operator so I am working on sessions and constantly adding picture from previous folder as a reference in the new folder, to be sure we have same light, same balance and check the mood is still going in the same direction. My goal is not to move but to copy as this way I can the copied image as reference in the new folder.
Actually I am doing this using "alt" button pressed and its coping and not moving. I was wondering if maybe we can switch between "moving" and "copying" but it seems it's not possible.
Anyway I ll continue on my way its works fine.
Big up for everybody contributes to my question !
Have a nice day guys !
0
Post is closed for comments.
Comments
7 comments