Can I convert an already completed job into a "Session"?
Can I convert an already completed job into a "Session"?
I want to try using Sessions and Smart Albums, etc.
My normal and previous workflow has just been to browse to the folder containing the job and to begin work from there but since the demise of V3.7.10, that method I used is now creating folders all over the place instead of keeping everything from the job, all in one root.
If I can convert these already completed jobs (created in V6.2), it might help me learn and understand the Sessions thing a little easier.
Obviously, I dont want to try this if it means that I will lose any of the work I have already done.
While I am on the same subject, which files created by C1 are safe to delete without losing any previous work, (i.e. which files can be deleted to clear clutter, that will just re-generated, if and when needed if the job is revisited again?). I know it would be safe to delete the Preview file (the .cop file), which other files can be dumped?
I want to try using Sessions and Smart Albums, etc.
My normal and previous workflow has just been to browse to the folder containing the job and to begin work from there but since the demise of V3.7.10, that method I used is now creating folders all over the place instead of keeping everything from the job, all in one root.
If I can convert these already completed jobs (created in V6.2), it might help me learn and understand the Sessions thing a little easier.
Obviously, I dont want to try this if it means that I will lose any of the work I have already done.
While I am on the same subject, which files created by C1 are safe to delete without losing any previous work, (i.e. which files can be deleted to clear clutter, that will just re-generated, if and when needed if the job is revisited again?). I know it would be safe to delete the Preview file (the .cop file), which other files can be dumped?
0
-
I don't use "sessions" but I do organize projects by folders. I first create a primary folder, then create subfolders to contain major elements of the job. So I'm not sure about "converting into a session" but you could move the photos into a logical group structure.
I always delete the "Cache" folder which removes all the preview files since CO will recreate them as needed. Everything in the Settings folder should be kept, along with your Raw files of course. You could, if you need the space, delete the processed files, since with the Raws & Adjustments, you could just reprocess again.0 -
That sounds good, Coach. What I am really after is that everything that I need to be kept from a job is is built in the same parent folder, the same folder that the original RAW files to be worked on, are in.
I'm not bothered about hard drive space, it is more about not keeping unnecessary clutter as this just unnecessarily complicates and lengthens any backup procedures I have (Ghost, Virus scans, etc).
For instance, I have my job folders on an additional drive to the of the Operating system, programs, etc (including CaptureOne), yet, if I delete RAW files (as I do as I deem them not to stay), they get transferred to the Trash folder (a central folder, where every trashed file from every job ever done) which is on the Primary drive where C1 is installed. I want everything to stay inside the original folder that contained the RAW files I began with. This is the way I always used to work up until the demise of v3.7.10.
I just thought perhaps, this smart album thingy might be a useful feature, but you dont feel the need to use it yourself?
It is a real pity there is not a procedure available where the cache is deleted after a designated period of time, like there used to be in and up until the demise of v3.7.10
I always deleted the processed files once they had been written to DVD because, as you quite rightly state, the same files can just be re-generated again, if and when, ever needed.0 -
[quote="NN122830UL1" wrote:
Can I convert an already completed job into a "Session"?
No problem. Just create a untethered session. Next, from Windows explorer move the image folder (with the image files and the Capture One subfolder with previews and adjustments) to the session folder. Maybe you have to reopen the session again but you will have your image folder within the session.
Alternatively, you can create a tethered session. In that case you suggest you move from within CO6 the images (select all images, not it folder) to the Capture folder of the new session.0 -
If your desire is to retain the develops in a subfolder(s) as in 3.x.....you don't even need to use sessions (I don't)
Select a recipe, then go to the "Advanced" tab of the "Process Recipe" tool....name the subfolder appropriately for the recipe type...as "Develops" if you want the 3.x convention....then select "Image folder" for the root directory.
Using this method, in my workflow...all files relating to a client session and the resulting output are located in a single folder. I use it just as 3.x with the exception that Cone files are ALSO in that folder rather than a single central cache. Makes using a NAS or shared image HD across a network a snap. Burning that single folder in total archives everything including the COne settings/previews
That suits my needs, other users might have different workflows ( stock, fine art, client work over time, etc) that make using smart albums/sessions the best choice.0 -
I agree with John4's advice for locating your image folder. It keeps all the files to backup in one location.
Your Trash folder can also be set to some other location on your secondary drive. In your Library, right-click on the folder you want to use, then click "Set as Trash Folder." This is how I use it, despite CO's warning that it could cause problems. While I do get many annoying errors when deleting files, it has not made a difference, in my case, on where the Trash and Raw files are located (C drive or other drives). One reason I like having Trash on the same drive as my Raw files is that the operating system can just do a file allocation function (more of a renaming) which is much quicker than moving the file to another hard drive.0 -
As it stands, I have no problem with where the develops are put as in the Process tab, you are given the option of choosing where to put them and this works fine for me.
It is good to know I can designate wherever I want the Trash folder to be too, although it is a shame that the trashed files do not stay in the original directory where they began, the way v3 used to do it by just changing the file extension. This to me, was a much better system, with all of the work files staying together, too.
Many thanks for the advise folks, it is very helpful0 -
To take it one step further, if you want to keep the Trash in the same folder structure, you could create a subfolder, mark it as your Trash folder. You would however have to do this procedure for each project. 0 -
Whilst not perfect, coach, that would be preferable....thanks again 0
投稿コメントは受け付けていません。
コメント
8件のコメント