Enhancing the session mode for external DAM users
Hi,
Many Lightroom users have added C1 to their workflow in order to better handle some RAW types. Most of them want to keep Lightroom as their DAM. In this case, using the C1 catalog is a dead end, especially because the hierarchical keyword library cannot be transferred (I tried). So using the session mode is the workable solution. However, there's a problem with the way sessions currently work. When you select a folder, all files from this folder are automatically added to the session. There's no workaround, as confirmed by the support :
Yes this is the way capture one operates and is designed when using a session. Only way to only generate companion files to only one file is to have only one file in the folder you are watching.
Usually, when using an external DAM as Lightroom, this is not what the user wants. Only some files in the folder will be handled by C1. Systematically adding all the files in that folder to the session generates a bunch of useless files cluttering the disk space. So I have made the following enhancement request:
Once a folder has been selected in session mode and all files in this folder therefore added to the current session, it should be possible to select some files in the folder, right-click the selection and use a command like "Remove from session" which would remove these files from the browser (can be done with a specialized filter) and would delete all companion files for these excluded files, of course **without deleting the files from the folder**. I'm a former developer and I'm sure this can be done rather easily. Please consider that you have a lot of potential Lightroom users considering using C1 for RAW development at least for some file types but are reluctant to throw away all the DAM work they have already done in Lightroom. To encourage this move, C1 needs to be more "Lightroom user-friendly".
If you're interested in this enhancement, please add your vote.
Thanks.
Many Lightroom users have added C1 to their workflow in order to better handle some RAW types. Most of them want to keep Lightroom as their DAM. In this case, using the C1 catalog is a dead end, especially because the hierarchical keyword library cannot be transferred (I tried). So using the session mode is the workable solution. However, there's a problem with the way sessions currently work. When you select a folder, all files from this folder are automatically added to the session. There's no workaround, as confirmed by the support :
Yes this is the way capture one operates and is designed when using a session. Only way to only generate companion files to only one file is to have only one file in the folder you are watching.
Usually, when using an external DAM as Lightroom, this is not what the user wants. Only some files in the folder will be handled by C1. Systematically adding all the files in that folder to the session generates a bunch of useless files cluttering the disk space. So I have made the following enhancement request:
Once a folder has been selected in session mode and all files in this folder therefore added to the current session, it should be possible to select some files in the folder, right-click the selection and use a command like "Remove from session" which would remove these files from the browser (can be done with a specialized filter) and would delete all companion files for these excluded files, of course **without deleting the files from the folder**. I'm a former developer and I'm sure this can be done rather easily. Please consider that you have a lot of potential Lightroom users considering using C1 for RAW development at least for some file types but are reluctant to throw away all the DAM work they have already done in Lightroom. To encourage this move, C1 needs to be more "Lightroom user-friendly".
If you're interested in this enhancement, please add your vote.
Thanks.
0
-
Have you considered using the "Selects" functionality to put the file into a folder of your choice for processing purposes?
That would position the files you want to work with in their own folder as required by C1 as it currently functions.
I have no idea how LR functions these days. I abandoned it after buying in to version 1 as I disliked having to load everything into a catalogue which, it seemed, disallowed the use of other editors unless one kept duplicated sets of images.
Grant0 -
[quote="SFA" wrote:
Have you considered using the "Selects" functionality to put the file into a folder of your choice for processing purposes? That would position the files you want to work with in their own folder as required by C1 as it currently functions.
Yes but this not a good solution when using an external DAM. The last thing I want when using an external DAM (be it Lightroom or anything else) is to have the files moved to another folder. I want them to stay in their original folder.[quote="SFA" wrote:
I have no idea how LR functions these days. I abandoned it after buying in to version 1 as I disliked having to load everything into a catalogue which, it seemed, disallowed the use of other editors unless one kept duplicated sets of images.
Actually, the problem is not related to Lightroom. My files are organized according to a given hierarchy with subfolders containing images that might come from various cameras or even from negative scans. For example, my "Berlin" subfolder contains images coming from a Canon EOS, from a Zeiss Ikon analog camera, from a Fuji X-Pro1, etc. And I want this to stay so. When opening the "Berlin" folder in a C1 (global) session, I know in advance that the TIFF files coming from the scans of the Zeiss Ikon negatives will not be handled in C1. I have another workflow for these files. So I don't want to create proxies and setting files, etc. for those files. And I don't want that my images from Berlin be dispatched in various folders. I want to keep everything in my "Berlin" folder.
Currently, C1 doesn't allow me to handle this cleanly and easily.0 -
+1
I've already thought about using LR plugin feature to achieve a good integration, but I think that some options are missing from COP: a few command line switches and some simple tweak in the program are probably enough and not very difficult to implement.
What I like is:
-A way to open a RAW from LR UI in COP (using a LR plugin), adding it to a specific session (or catalog).
-When finished editing, generate a preview (JPEG or TIFF) and automatically import it in LR (using recipe in COP and LR plugin).
-A way to modify my previous edit in COP from LR (so modifications in COP must be stored in a session or catalog).
-Eventually synchronize metadata between LR and COP, but not mandatory.
There's probably some issues regarding the synchronization of file when deleting/moving an edited RAW in LR, but I think I can live with it.0 -
[quote="Samoreen" wrote:
Systematically adding all the files in that folder to the session generates a bunch of useless files cluttering the disk space.
+1[quote="Samoreen" wrote:
So I have made the following enhancement request:
Once a folder has been selected in session mode and all files in this folder therefore added to the current session, it should be possible to select some files in the folder, right-click the selection and use a command like "Remove from session" which would remove these files from the browser (can be done with a specialized filter) and would delete all companion files for these excluded files, of course **without deleting the files from the folder**.
This proposal would be better than the present procedure, however the more efficient behavior would be to add to a session only the file sent to C1 from the external DAM without the clutter of the additional files in the folder and the addition of an option that would automatically return the new converted file to the original folder.
(I am a former Lightroom user but now utilize IDimager Photo Supreme for my DAM.)
Bob0 -
Hi
Not Lightroom but I use Daminion as a standalone DAM along with C1P 8.3.3 in session mode with no usage of the C1P default subfolders, my process recipe is set up to place the C1P JPEGS alongside the original NEFS for re-importing back into Daminion.
I stumbled on the undocumented(?) "feature" that if I open C1P from Daminion with the following command syntax:
"C:\Program Files\Phase One\Capture One 8\CaptureOne.exe" "F:\nikon D7100\2016\2016-01-18\rjf_20160118_1925_v00.NEF" "F:\nikon D7100\2016\2016-01-18\rjf_20160118_1925_v00.NEF"
as an example, C1P will then display only the single image in the browser along with creating an Untitled Session Album with only the single image. The associated files in the Capture One subdirectory are created only for the single image , not all images in the folder. C1P seems to treat this double image name entry as a direction to create a Session Album. Using the same command with only a single file location entry for an image of course, opens the whole folder of images in the viewer along with all thumbnails and associated files in the Capture One subfolder. I have both set up in Daminion.
Hope this helps.
bob0 -
[quote="NN635343926268268912UL" wrote:
Hi
as an example, C1P will then display only the single image in the browser along with creating an Untitled Session Album with only the single image. The associated files in the Capture One subdirectory are created only for the single image , not all images in the folder.
Bob,
Thanks a lot. This "useful bug" appears to be a temporary solution waiting for an enhancement in C1. I tested this trick in C1 v9 and it worked. I will now try to translate this into a LUA script that could be launched from Lightroom.0 -
Thanks Samoreen
Nice to know it will still work in V9 which I will update to when I return from travelling. Now if only the labels were configurable ...
bob0 -
For those interested in making the trick described by NN635343926268268912UL working directly from Lightroom :
1. Create a text file named "Edit in C1.lua" in notepad or in any text editor and insert the following text :
local LrApplication = import 'LrApplication'
local LrTasks = import 'LrTasks'
local catalog = LrApplication.activeCatalog()
local LrShell = import 'LrShell'
local function openWithExternalProgram()
local programPath = "C:\\Program Files\\Phase One\\Capture One 9\\CaptureOne.exe"
local photo = catalog:getTargetPhoto()
if photo ~= nil then
local onePath = """ .. photo:getRawMetadata('path') .. """
local photoPath = {onePath,onePath}
LrShell.openFilesInApp(photoPath, programPath)
end
end
LrTasks.startAsyncTask(openWithExternalProgram, "openWithExternalProgram")
Edit the file in case captureone.exe is installed in a different folder.
[color=#00BF00:25r6txok]Credit: original LUA script for running external programs from LR authored by Maurizio Agelli. Modified by myself to adapt to C1[/color:25r6txok]
2. Put "Edit in C1.lua" in C:\Users\<username>\AppData\Roaming\Adobe\Lightroom\Scripts
3. (Re)Launch Lightroom. The Scripts menu should display the "Edit in C1" command.
4. Select an image and use that command against it. C1 should be launched and the target image should be added to an unnamed album, ready to be handled in C1. Only the companion files needed for that file will be created. Other files in the same folder will be ignored.
This is just a temporary workaround until P1 give us a better solution for working with external DAMs.0 -
[quote="NN635343926268268912UL" wrote:
Nice to know it will still work in V9 which I will update to when I return from travelling. Now if only the labels were configurable ...
bob
Bad news! Unfortunately, the trick doesn't work all the time. Sometimes, the thumbnail is not created, so there's nothing to see in the browser. The album is created, all companion files are created except the thumbnail.
I can't find any pattern in order to reproduce. Sometimes it works, sometimes it doesn't. So this is a real bug, not a hidden feature 😕 .0 -
Since I'm rather stubborn, I have found another solution that works better for sending an image from Lightroom to C1.
1. I created an empty catalog and made it active in C1 (which can be closed, no problem).
2. I created the following script named "Open in C1.lua":
local LrApplication = import 'LrApplication'
local LrTasks = import 'LrTasks'
local catalog = LrApplication.activeCatalog()
local LrShell = import 'LrShell'
local function openWithExternalProgram()
local programPath = "C:\\Program Files\\Phase One\\Capture One 9\\CaptureOne.exe"
local photo = catalog:getTargetPhoto()
if photo ~= nil then
local photoPath = {photo:getRawMetadata('path')}
LrShell.openFilesInApp(photoPath, programPath)
end
end
LrTasks.startAsyncTask(openWithExternalProgram, "openWithExternalProgram")
3. I stored it as usual in C:\Users\<username>\AppData\Roaming\Adobe\Lightroom\Scripts.
4. Now, when I select an image in Lightroom and run the script from the Scripts menu against that image, C1 opens and displays the Import dialog. I just have to click on the image and then click on "Import 1 image" and that's it. Only that image is imported and not the whole folder. No more useless files cluttering my disk.
Note for NN635343926268268912UL:
This means that passing a single filename on the command line to captureone.exe when C1 is running catalog mode or was closed while in catalog mode, there's no need to pass it twice. Only that file will be imported.0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare