Button or Hotkey to move images back to Capture (similar to "move to selects" button)
What problem do you see this solving?
Often times after culling, I move images to the selects folder to work on. But while editing, I realize some photos aren't worth being selects, so I'd like to push them back to Capture. . . but there is no button like the "move to selects" button.
When was the last time you were affected by this lack of functionality, or specific tool?
Daily
Current workaround
Are you using any workarounds or other solutions to achieve your goals in Capture One?
I have to manually go back to the folder tab, and then drag back.
I'm wondering if a back-to-Capture folder is a properly complete solution.
Imo, it is a proper solution.
It is not a "move back to Capture folder" hotkey but a " move to Capture folder". You can set a Capture folder or leave the standard one and move it there, a simple thing.
Such a basic function (which move to a set folder is) does not need to be the complete answer to all questions and workflows, on contrary, it lives on its own rights, because it is an elementary function, and can be used where applicable.
Like fire, also a basic element. Fire is not a properly complete solution to everything, but can be used where applicable, e.g. if it is cold outside on your camping trip, or if you established a proper solution to warm but not burn your house. Use it where it suits.
In your mentioned cases, SFA, you should not use the "move to Capture folder" hotkey, it wouldn't suit.
For such a basic feature there is no ambigiuty, it would do what it said, just move an image file to the current Capture folder.
If it fits many users workflows and is an easy to understand concept, like "Move to Selects" or "to Trash" is too, I have no arguement against it, especially as a possible alternative implementation for cases you mentioned, e.g. a "send back to original folder" hotkey, comes with its own downsides:
"Send back to original (or last) location" is against what I believe is a core value of sessions, i.e. its simple design and implementation, which contributes to the stability, robustness and ease of use of C1 sessions over all those years.
Imagine you are moving an image from any system folder to the Selects folder, then move the complete session from your notebook (or from backup) to your desktop computer, what would such a "send back to originals folder" do? Annoy the user with a message that it is not possible because the folder cannot be found? Possible, but leaving me with a sense of concern.
For that reason (ease of design, limited complexity), I don't even want sessions to separate variants, i.e. put one variant into a virtual Selects "folder" instead of the file into the real folder, which could be seen as a logical step in the evolution of sessions, since this is possible in albums in catalogs. No no, don't want that.
There is even another case for "move to Capture folder", i.e. you browse your system folder hiearchy which you want to delete later (let's say thousands of bird photos shot with 20 images/second) from a one week trip to a bird destination, but prior to deletion you want to put your keepers into a Capture folder in order to find and select the best ones later (your 'real' Selects). A "move back to Capture folder" would not help here, a move to Capture folder would.
There is always drag and drop
The same could be said for file moving to the Selects and Trash folder.
So, move to Capture folder is not a complete answer to everything but beautifully simple and it would complement the existing "move to" functions.
I'm wondering if a back-to-Capture folder is a properly complete solution.
There's no reason why a Select file should have come from the Capture folder in the first place. When I import to a session the imports usually go into subfolders within the Capture folder.
Also, if I have deselected a previous select - does that always imply it should go back to a "Capture" pot? What if I work with a "probably rejects" folder prior to a final rejection into Trash?
I'd love to see a "Move To Capture". Like the OP, I sometimes move files to Select so I can work on them, but later realize they should be back in Capture. We have a "Move to Trash", adding a "Move to Capture" seems logical to me, and I would use it regularly.
Yes, a "move the image back" button makes things complicated (btw, there is no 'move back to original location from trash' either.)
But a "move to Capture folder" is easy, fits many workflows, and is symmetrical to 'move to Selects folder', and 'move to trash', and does comply with the simplicity of how sessions work, i.e. folder based, not knowledge about image history based.
P.S. A useful feature. The only reason I don't upvote is because I use sessions but not the Selects folder
I don't have a workflow that would result in this issue (Everything goes into Capture, then into Selects) but I see the complication. In the meantime for those on simpler workflows, a "Move to Captures" shortcut, perhaps? :D
C1 Sessions automatically creates certain default folders - like Capture and Selects within the file structure BUT also creates references to those folders allowing each folder to be associated with any other folder in the system. This is the basis of David Grover's suggestion earlier in the thread.
So there are a couple of issues about setting up a shortcut that makes an assumption about using the "capture" folder as a desination or, indeed the "selects" folder as a source, since either option could be pointing elsewhere that to the default location.
Going further with that observation, files in the "Selects" folder may not have been sourced from the "Capture" folder - neither the C1 created Captureflder or the virtual link folder as currently active.
These factors are the basis of my proposal, above, that the only real solution to the problem (for foreseeable, practical use cases) would be to know where the image file came from originally and send it back there. If the target location is not available, ask the user what they want to do next.
Designating the selects folder seems like a pretty bad workaround, especially if you forget and then "Select" further images without realising and lose a bunch of work as the images are no longer put anywhere...
How about just changing the behaviour of Ctrl+Shift+J to "Swap image between Capture and Selects" ? Then if you're in selects it'll send it back, if you're in capture it'll select it.
You already have a Delete key to send to trash, so it wouldn't interefere there, and the coding overhead for this change has to be minimal.
Everything in Capture, then cull good/maybe images to selects to edit.
Then while editing, I realize that some of those selects are not good enough, so I'd like them back to the Capture folder.
Would just love a hotkey to move it back vs having to do all the manual stuff.
And yes David, it would be a pain to continually have to change that folder all the time, so seems like a quick "return to capture" or "return to previous folder" would be a nice option due to me falling out of love with some of the selects :)
There is, of course, the possibility that the selected file did not get there from the nominal default Capture Folder and may have come from elsewhere. Indeed the current "Capture" folder may not be the capture folder it came from.
Maybe a "return to previous location" facility could become popular?
11057524292637 - I think there is an advantage to the Selects folder. I always start work in a session, and I use the Selects folder for the images that I consider "keepers". Ultimately, that folder is added to my master catalog, and the Capture folder is not.
375258577258 - agreed, you can do it that way, though it would be a pain to have to remember to change it back to the actual Selects folder afterward. I agree with the suggestion. It would be good at least to be able to have a "move to selects" command that we could assign a key combination to. I find like the OP does that sometimes I think again about images that I have put in Selects, and end up dragging them back manually.
If you find this happens a lot, Michael, just avoid using the Selects folder until you are fairly sure the image is worth Selecting.
For what it is worth, I almost never use the Selects folder.
Now, if I was doing a studio shoot with a client and they were selecting their preferred as the session passes, then I would likely use the Selects folder quite extensively. But outside that scenario I am less convinced of the need, although now and again I might use it to avoid a one-off need to group and process some images for a specific purpose on a temporary basis.
This might sounds strange but there is already a way to do that. The Capture, Selects, Output, Trash can be assigned to any folder. So if you right click on the Capture Folder and say "Show in Library" you can right click again and set it as the selects folder.
Then your shortcut will send them back to the "Capture" folder.
Imo, it is a proper solution.
It is not a "move back to Capture folder" hotkey but a " move to Capture folder". You can set a Capture folder or leave the standard one and move it there, a simple thing.
Such a basic function (which move to a set folder is) does not need to be the complete answer to all questions and workflows, on contrary, it lives on its own rights, because it is an elementary function, and can be used where applicable.
Like fire, also a basic element. Fire is not a properly complete solution to everything, but can be used where applicable, e.g. if it is cold outside on your camping trip, or if you established a proper solution to warm but not burn your house. Use it where it suits.
In your mentioned cases, SFA, you should not use the "move to Capture folder" hotkey, it wouldn't suit.
For such a basic feature there is no ambigiuty, it would do what it said, just move an image file to the current Capture folder.
If it fits many users workflows and is an easy to understand concept, like "Move to Selects" or "to Trash" is too, I have no arguement against it, especially as a possible alternative implementation for cases you mentioned, e.g. a "send back to original folder" hotkey, comes with its own downsides:
"Send back to original (or last) location" is against what I believe is a core value of sessions, i.e. its simple design and implementation, which contributes to the stability, robustness and ease of use of C1 sessions over all those years.
Imagine you are moving an image from any system folder to the Selects folder, then move the complete session from your notebook (or from backup) to your desktop computer, what would such a "send back to originals folder" do? Annoy the user with a message that it is not possible because the folder cannot be found? Possible, but leaving me with a sense of concern.
For that reason (ease of design, limited complexity), I don't even want sessions to separate variants, i.e. put one variant into a virtual Selects "folder" instead of the file into the real folder, which could be seen as a logical step in the evolution of sessions, since this is possible in albums in catalogs. No no, don't want that.
There is even another case for "move to Capture folder", i.e. you browse your system folder hiearchy which you want to delete later (let's say thousands of bird photos shot with 20 images/second) from a one week trip to a bird destination, but prior to deletion you want to put your keepers into a Capture folder in order to find and select the best ones later (your 'real' Selects). A "move back to Capture folder" would not help here, a move to Capture folder would.
The same could be said for file moving to the Selects and Trash folder.
So, move to Capture folder is not a complete answer to everything but beautifully simple and it would complement the existing "move to" functions.
There is always drag and drop.
I'm wondering if a back-to-Capture folder is a properly complete solution.
There's no reason why a Select file should have come from the Capture folder in the first place. When I import to a session the imports usually go into subfolders within the Capture folder.
Also, if I have deselected a previous select - does that always imply it should go back to a "Capture" pot? What if I work with a "probably rejects" folder prior to a final rejection into Trash?
I'd love to see a "Move To Capture". Like the OP, I sometimes move files to Select so I can work on them, but later realize they should be back in Capture. We have a "Move to Trash", adding a "Move to Capture" seems logical to me, and I would use it regularly.
Yes, a "move the image back" button makes things complicated (btw, there is no 'move back to original location from trash' either.)
But a "move to Capture folder" is easy, fits many workflows, and is symmetrical to 'move to Selects folder', and 'move to trash', and does comply with the simplicity of how sessions work, i.e. folder based, not knowledge about image history based.
P.S. A useful feature. The only reason I don't upvote is because I use sessions but not the Selects folder
I don't have a workflow that would result in this issue (Everything goes into Capture, then into Selects) but I see the complication. In the meantime for those on simpler workflows, a "Move to Captures" shortcut, perhaps? :D
C1 Sessions automatically creates certain default folders - like Capture and Selects within the file structure BUT also creates references to those folders allowing each folder to be associated with any other folder in the system. This is the basis of David Grover's suggestion earlier in the thread.
So there are a couple of issues about setting up a shortcut that makes an assumption about using the "capture" folder as a desination or, indeed the "selects" folder as a source, since either option could be pointing elsewhere that to the default location.
Going further with that observation, files in the "Selects" folder may not have been sourced from the "Capture" folder - neither the C1 created Captureflder or the virtual link folder as currently active.
These factors are the basis of my proposal, above, that the only real solution to the problem (for foreseeable, practical use cases) would be to know where the image file came from originally and send it back there. If the target location is not available, ask the user what they want to do next.
Designating the selects folder seems like a pretty bad workaround, especially if you forget and then "Select" further images without realising and lose a bunch of work as the images are no longer put anywhere...
How about just changing the behaviour of Ctrl+Shift+J to "Swap image between Capture and Selects" ? Then if you're in selects it'll send it back, if you're in capture it'll select it.
You already have a Delete key to send to trash, so it wouldn't interefere there, and the coding overhead for this change has to be minimal.
SFA, it's just my process.
Everything in Capture, then cull good/maybe images to selects to edit.
Then while editing, I realize that some of those selects are not good enough, so I'd like them back to the Capture folder.
Would just love a hotkey to move it back vs having to do all the manual stuff.
And yes David, it would be a pain to continually have to change that folder all the time, so seems like a quick "return to capture" or "return to previous folder" would be a nice option due to me falling out of love with some of the selects :)
There is, of course, the possibility that the selected file did not get there from the nominal default Capture Folder and may have come from elsewhere. Indeed the current "Capture" folder may not be the capture folder it came from.
Maybe a "return to previous location" facility could become popular?
11057524292637 - I think there is an advantage to the Selects folder. I always start work in a session, and I use the Selects folder for the images that I consider "keepers". Ultimately, that folder is added to my master catalog, and the Capture folder is not.
375258577258 - agreed, you can do it that way, though it would be a pain to have to remember to change it back to the actual Selects folder afterward. I agree with the suggestion. It would be good at least to be able to have a "move to selects" command that we could assign a key combination to. I find like the OP does that sometimes I think again about images that I have put in Selects, and end up dragging them back manually.
Ian
I had no idea that Selects exist - I either star and then filter, or add to albums. Is there an advantage to Selects?
If you find this happens a lot, Michael, just avoid using the Selects folder until you are fairly sure the image is worth Selecting.
For what it is worth, I almost never use the Selects folder.
Now, if I was doing a studio shoot with a client and they were selecting their preferred as the session passes, then I would likely use the Selects folder quite extensively. But outside that scenario I am less convinced of the need, although now and again I might use it to avoid a one-off need to group and process some images for a specific purpose on a temporary basis.
Hi Michael,
This might sounds strange but there is already a way to do that. The Capture, Selects, Output, Trash can be assigned to any folder. So if you right click on the Capture Folder and say "Show in Library" you can right click again and set it as the selects folder.
Then your shortcut will send them back to the "Capture" folder.