I'd like to be able to open CO without a session.
Like the same functionality as a session but with the "System Folders" panel only. This would make it easier when working in Lightroom to send a file over for editing in CO.
-
You have to have the reference control of either a session or a catalog to connect all of the parts of C1 together. Session sounds right for your purpose. You only need one for the requirement you described.
Your options would be to always "send" the file to the same folder and simply have that folder set up as a "Favourite" folder in the session; OR put the file wherever you want to put it and navigate to the folder in C1 in order to open the file. (With or without making it a Favourite).
That said there may be some more specific suggestions available if the purpose for using C1 as a Lightroom "plugin" was known. It sounds a little unusual to me, which is why I think knowning the purpose would allow people to optimise their suggestions.
0 -
This "reference control" you mention is not necessary for the "System Folders" panel to work or the actual editing. Creating a special session just for one-off LR edits won't work because, as far as I can tell, there's no way to choose which session opens when I send a file to CO. It just opens the last session I used. And it doesn't open up to the file I tried to send to it; I still have to go to "System Folders" and dig until I find it. I'd like CO to open up with the file I sent to it selected and the folder it's in open.
Exporting the file from LR to a specific folder is not what I want either. That's actually more work than what I do now. Presently, I have to open CO to some random, unrelated session, go to the "System Folders" panel and dig until I find the image. Exporting from LR first to a favorited folder would save the digging steps but it would add even more steps with the exporting and re-importing in LR, plus it would create extra copies of files, which I don't want. And anyway, in order to save the digging steps, I'd have to be using this special session created for this purpose which means I couldn't send the file directly from LR at all because I can't choose which session opens. And if this special session wasn't in the "recents" list then I'd have to dig into the file system to find the session and open it, which means it's not saving any digging steps at all; merely relocating them.
I use CO for my professional contract work in session mode because those jobs are stand-alone but I use LR for my personal photos because its cataloging is better. My LR catalog goes back more than a decade and contains tens of thousands of photos. When it comes to RAW editing, there are things CO does better or different from LR and so there are times when I have a photo in my LR catalog that I'd really like to edit in CO and see if I can get a better result. This is when it would be great to select "Edit in CaptureOne.exe" in LR and have CO open right up to it without having to create a session, dig through the file system, or import it into a catalog.
0 -
The only thing I can suggest for now is that you simply open C1 and edit the image rather than seek a C1 "plug-in" from LR. After all, you would have to return the edited image as a tiff or a jpg (or perhaps PSD) and that will be irrespective of whether you open the image directly in a C1 session or by sending a command from within LR. It would be the same situation if editing something in LR and returning it to C1.
Realistically the editing part of it is probably secondary to having a mechanism that the hosting "catalog" can use to become aware that it has a new file (or a new version of an existing file) to manage. In that respect, you may need to be looking at LR for the solution.
0 -
Simply opening C1 and editing the image is what I'm doing now. It just takes a lot of clicking and digging and is time consuming. I'm requesting a feature that will streamline the process. The issues that you mention with round-tripping aren't issues at all: that functionality already exists. Both applications are capable of this. All that's needed is for C1 to be able to open directly to a system folder and with only its core functionality in place. No new functionality really; mainly just stripping out and streamlining existing functionality. I recognize that this change may not be trivial from a software development standpoint and is probably unlikely to happen but I thought it was worth putting out there. I like C1 and I'd like to see it get better.
0
Post ist für Kommentare geschlossen.
Kommentare
4 Kommentare