Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Session Folders - how do images get into Select/Trash/Output folders

Comments

7 comments

  • SFA

    David,

    The default session has some "Physical" folders named Selects, Trash and Output but the references to Selects, Trash and Output found in the library are in fact links that, by default on creation, point to the folders. 

    You can change where those links point within you system or network should you feel a need to. They could point to any folder. The "default, physical" folders in the Session folder structure will still exist.

    The Trash folder is only ever updated "automatically" if you choose to "delete" something or use the "Move to trash". functionality. (Basically the same thing.).

    "Move to selects" as a function needs to be actioned, one way or another, before an image and its edits would end up there other than by dragging and dropping rather than using the "Move" option. Again, basically the same thing.

    "Output" is generally going to be the result of running an output processing recipe session but, as with any folder, files may be sent there in other ways by user interaction. I cannot think of any process in C1 that would sent files to the Output folder without a user instigating a process to make that happen.

    So, for example, running an output process would not then send the processed file to trash or selects or whatever.

    Did you have a specific use case example to consider?

     

     

    0
  • Permanently deleted user

    There is no magic or automation going on in the Session file structure. Move files to the folders that suit you. You can even move them in the Finder without messing up anything in your Session.

    0
  • Permanently deleted user

    Hi both, thanks for the swift replies. I have been using C1 on and off for 12 months, and have been using a catalogue. I was put off using sessions since I imagined that they were intended for targeted photo shoots, and that there was some associated automation that would move files around to Selects (possibly in response to flags/stars) , to Trash (in response to a delete) and to Output in response to executing an output process.

    I use Lightroom to organise my images and C1 for processing my Fuji files, so didn't want C1 automatically moving any files about.

    After watching a couple of videos one with Joe Cornish and one with Joe McNally, both working with sessions, I thought it was time to try a switch. So my post was to check if there were any circumstances where C1 would move files around.

    Sessions could be the way to go as the downside on Catalogues for me is that I have to have a catalogue on an external SSD drive, and the import (leaving the files on a NAS and just detecting duplicates and building previews) takes a day and an age.

    Thanks again.

    0
  • Permanently deleted user

    There is a menu option "Image -> Move to Selects Folder" which has the shortcut ⌘J.  At least that is the shortcut on my system.

    0
  • SFA

    David,

    OK, if you are using LR to manage your files from a catalogue point of view then you are correct - you would not want any files moved around without understanding the potential effects.

    If you move anything around with out LR knowing about it you may have problems.

    You would have no need to use "Move to selects" option. However it is nondestructive but none the less just avoid it.

    Avoid the delete option as well. Delete images in LR.

    You will need to consider under what, if any, circumstances, you might want to delete from C1 but not LR or from both applications. At the moment I would guess that deleting from LR but not C1 is not a concern.

    Output can be sent anywhere according to your purpose. You will, presumably, know where you want an output file to be sent on the basis of what you plan to do with it next. So you will be in charge of it and in any case there is no impact on LR operations.

    However Allen's advice about copying things around using the in Finder should not imply that moving files outside C1 will be certain to maintain image edit integrity. Nor would moving a file using LR.

    In a session situation C1 creates all of the files used for Editing, Layer masks, Preview Files, Thumbnails and a couple of other things in "sidecar" files and these ae saved in a folder called Capture One that will exist in every folder that contains one or more image files and that you have opened with Capture One.

    If you move files using the C1 facilities to do so all of the subfolders and the files in them that relate to a specific image will travel with them. If you move just the image file using an operating system instructions or a different application the file will move without its associated edit information. The edit information will become orphaned where it was.

     

    It's not the end of the world but perhaps is not what you might wish and would suggest then a need for some tidying up admin becoming a requirement at some future point.

    0
  • Permanently deleted user

    SFA, thanks for the very detailed reply, really helpful, in fact much more helpful than the C1 help desk! Much appreciated.

    0
  • SFA

    You are very welcome David.

    If you are working with 2 separate applications it is very likely that there may be conflicting admin requirements or some additional tasks if you need to re-organize images. So long as you know what is where the task is not too difficult to think through and manage.

    Dealing with entire folders is quite easy. C1 sessions just expect to find a Capture One folder in the same folder as the images. If you open a folder of recognized file types C1 will seek out the folder and use its contents. If no folder exist or the contents are not complete for the images it has discovered it will create the required files. 

    There is a little more work to take on if moving only some files from a folder and doing it outside C1. To retain existing edit info you would need to move the related settings files as well. Easy enough as an activity but a little extra work to pick the individual files needed and move them.

    As for the session database file ... if you are simply opening a folder, editing and closing it when ever you need to there is no effect on the session file if you move things around. (So long as you were not live editing any of the files at the time!)

    If you have the folder in which the files reside(d) saved as a Session Favourite folder moving the folder or any of its contents is likely to break some links. But other than taking steps to revise the links as required I cannot think of any other significant impacts.

    If you have created fixed albums from a selection of images and the images have moved outside C1 some maintenance of the album may be appropriate. Smart albums will simply self amend.

    Realistically if one is using and "open" session the chances are that albums within C1 are not a primary requirement so you can probably forget about them. Indeed such things are likely to be handled by the other application used as the primary Asset Management tool.

     

    There are probably a few other nuances of operation that could arise depending on how one does things but based on your outline of how you work with C1 they are very likely not relevant to you. They are also the sort of things that you have to be doing for any discussion to be meaningful. We can cover such things if ever new questions arise.

    0

Post is closed for comments.