If you still prefer using the Lightroom catalog...
Hi,
Since C1 20 brought no enhancement to the catalog (actually it seems to have added new bugs), I have given some thought to how I could use the Lightroom catalog while editing images in C1 when needed. My solution :
1. I have created a LUA script named Edit in C1.lua. Here is the source code :
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 20\\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")
You can create the file with Notepad under Windows. The file should be stored in C:\Users\<user>\AppData\Roaming\Adobe\Lightroom\Scripts. The Scripts menu in Lightroom is not available until there's at least one script in this folder.
2. Then I created an empty C1 catalog named FromLR and I made it active.
3. Now, in LR, if I decide to process an image in C1, I open the Scripts menu in LR and select Edit in C1. C1 is launched and proposes the import of the target image. I acknowledge and that's it. Note that the file sent to C1 is the RAW file, not an exported TIFF or JPEG.
4. After editing, once I have exported the TIFF or JPEG file from C1, I go back to LR and synchronize the folder where the image is stored. Then I can further edit the TIFF/JPEG in an external program more easily than from C1. I can also print the image from LR since the print module of C1 is still rather calamitous.
A simple way to benefit from a better catalog. Don't forget that even if you have cancelled your LR subscription, the LR catalog is still working.
Since C1 20 brought no enhancement to the catalog (actually it seems to have added new bugs), I have given some thought to how I could use the Lightroom catalog while editing images in C1 when needed. My solution :
1. I have created a LUA script named Edit in C1.lua. Here is the source code :
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 20\\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")
You can create the file with Notepad under Windows. The file should be stored in C:\Users\<user>\AppData\Roaming\Adobe\Lightroom\Scripts. The Scripts menu in Lightroom is not available until there's at least one script in this folder.
2. Then I created an empty C1 catalog named FromLR and I made it active.
3. Now, in LR, if I decide to process an image in C1, I open the Scripts menu in LR and select Edit in C1. C1 is launched and proposes the import of the target image. I acknowledge and that's it. Note that the file sent to C1 is the RAW file, not an exported TIFF or JPEG.
4. After editing, once I have exported the TIFF or JPEG file from C1, I go back to LR and synchronize the folder where the image is stored. Then I can further edit the TIFF/JPEG in an external program more easily than from C1. I can also print the image from LR since the print module of C1 is still rather calamitous.
A simple way to benefit from a better catalog. Don't forget that even if you have cancelled your LR subscription, the LR catalog is still working.
1
-
Nice work! 0 -
Credit for the original LUA script (which I adapted to C1) goes to Maurizio Agelli. 0 -
TL;DR: Lightroom users, if you're used to organizing by date in your folders, you can easily find your images using the FILTERS tool, Date tab.
----
What a mess. I've been considering going back to Lightroom because, even though I appreciate what Capture One does for my paid work, I realized that since I started using COne I spend much less time editing personal work - or really anything that involves going 'back in time' to find.
When COne12 came out, they posted one of their seminar videos on *just* working with catalogs, touting that it was newly improved... And then I realized it was a 45 minute video on catalogs. Seriously. If it takes 45 minutes to explain how to use a file browser and organizer, then you have serious issues.
The Library tool is really wonky. Why is so much weight given to Recent Imports" in the Library? Maybe top 5 recent imports, max, 10 is too many and cluttered 3 is probably ideal, a choice even better.
Why are folders not in their own tool?
Yes, I want quality folder management in a RAW processing tool. It's not an effective catalog without it. It's a bit frustrating to feel like I need to use Bridge or Photo Mechanic, on top of this, just to get by.
So much of it stems from the poor organization and implementation of the "Folders" list vs "Filters". A lot of what is missing for people migrating to COne is the "Library" in LR is a folder based approach, as well as having strong collection implementation, so it doesn't matter if you use a date-based organization approach or a topic/keyword/gig based one. Whereas Folders in COne are kind of useless, even if collections are fine.
And in the folders list, please improve adding folders! Why is it that I can't add a parent folder and then have sub-directories automatically propagate into the list? I have a folder structure of /Catalog/Year/Month/Day and there is no way to easily add all of these folders at once when looking at my archives. I know I can right click a folder, choose "Syncronize" and there is an option to "Include Known Subfolders" but why is there no option to automatically ADD subfolders when Syncronizing?
But this shouldn't even be a problem to begin with because these folders should be automatically added when importing!
Is this a bug? Why are they not being added? I could have sworn they were in COne 11, though I had similar issues in COne 12.
Maybe I should be posting this in a new topic so this gets more exposure...0 -
Yes you should and I agree with you, in every single word. I'm just migrating from Lightroom to Capture One, but the DAM part of COne needs a lot of improvement! For this, LR is way better (of course, it was built as a DAM in the first place). But as COne has been receiving updates lately, they could be more careful with the organization part. NN636771337705992097UL wrote:
TL;DR: Lightroom users, if you're used to organizing by date in your folders, you can easily find your images using the FILTERS tool, Date tab.
----
What a mess. I've been considering going back to Lightroom because, even though I appreciate what Capture One does for my paid work, I realized that since I started using COne I spend much less time editing personal work - or really anything that involves going 'back in time' to find.
When COne12 came out, they posted one of their seminar videos on *just* working with catalogs, touting that it was newly improved... And then I realized it was a 45 minute video on catalogs. Seriously. If it takes 45 minutes to explain how to use a file browser and organizer, then you have serious issues.
The Library tool is really wonky. Why is so much weight given to Recent Imports" in the Library? Maybe top 5 recent imports, max, 10 is too many and cluttered 3 is probably ideal, a choice even better.
Why are folders not in their own tool?
Yes, I want quality folder management in a RAW processing tool. It's not an effective catalog without it. It's a bit frustrating to feel like I need to use Bridge or Photo Mechanic, on top of this, just to get by.
So much of it stems from the poor organization and implementation of the "Folders" list vs "Filters". A lot of what is missing for people migrating to COne is the "Library" in LR is a folder based approach, as well as having strong collection implementation, so it doesn't matter if you use a date-based organization approach or a topic/keyword/gig based one. Whereas Folders in COne are kind of useless, even if collections are fine.
And in the folders list, please improve adding folders! Why is it that I can't add a parent folder and then have sub-directories automatically propagate into the list? I have a folder structure of /Catalog/Year/Month/Day and there is no way to easily add all of these folders at once when looking at my archives. I know I can right click a folder, choose "Syncronize" and there is an option to "Include Known Subfolders" but why is there no option to automatically ADD subfolders when Syncronizing?
But this shouldn't even be a problem to begin with because these folders should be automatically added when importing!
Is this a bug? Why are they not being added? I could have sworn they were in COne 11, though I had similar issues in COne 12.
Maybe I should be posting this in a new topic so this gets more exposure...0 -
NN636771337705992097UL wrote:
If it takes 45 minutes to explain how to use a file browser and organizer, then you have serious issues.
It doesn't - but it does seem to take some people an inordinately long time to grasp the notion that Capture One isn't LightRoom.0 -
NN636771337705992097UL wrote:
And in the folders list, please improve adding folders!
[...]
Maybe I should be posting this in a new topic so this gets more exposure...
Won't do you any good - this is a user forum.
If you have a feature request, raise it in an official Support Case.0 -
NNN636478045173271496 wrote:
Yes you should and I agree with you, in every single word. I'm just migrating from Lightroom to Capture One, but the DAM part of COne needs a lot of improvement!
Works just fine for many of us.
At no point was Capture One sold to you as a like-for-like LightRoom DAM replacement, and adapting isn't that hard.
You could also continue to use LightRoom's DAM functions if Capture One's approach really is untenable.0 -
Keith Reeder wrote:
You could also continue to use LightRoom's DAM functions if Capture One's approach really is untenable.
It's not a matter of "approach" or of missing features. This catalog just doesn't work correctly. Just have a look there : [The Capture One forum has migrated to a new platform, as a result all links to Capture One related postsstopped working and have been removed] .0 -
Samoreen wrote:
Keith Reeder wrote:
You could also continue to use LightRoom's DAM functions if Capture One's approach really is untenable.
It's not a matter of "approach" or of missing features. This catalog just doesn't work correctly. Just have a look there : [The Capture One forum has migrated to a new platform, as a result all links to Capture One related postsstopped working and have been removed] .
+1 but what's the point? P1 either aren't listening, don't care or both.
I trialled C1 as an escape route from LR. Let me say, up front, that the editor is FANTASTIC. The rest of it isn't. The very first thing I ran into was "6 of your photos are incompatible". OK. Which 6? How hard would it be to spin off a .txt file with a list of filenames? Apparently I'm expected to scrabble around for hours trying to work it out. That's just the beginning of the broken experience that is C1 file management.
If the file management / DAM / catalog / call it what you will just worked, I'd buy it, but now I understand why so many people use C1 with Photo Mechanic or some other external DAM. No way would I trust C1 with my metadata. Sidecar files for DNG and JPEG?!?!
John0 -
Please find below a variant of the script proposed above. This version will also launch C1 but instead of only proposing for editing the file selected in Lightroom, the C1 import dialog will contain all the image files stored in the folder where the selected file resides. This could make things even easier in many cases. The script should be modified as follows :
local LrApplication = import 'LrApplication'
local LrTasks = import 'LrTasks'
local catalog = LrApplication.activeCatalog()
local LrShell = import 'LrShell'
local LrPathUtils = import 'LrPathUtils'local function openWithExternalProgram()
local programPath = "C:\\Program Files\\Phase One\\Capture One 20\\CaptureOne.exe"
local photo = catalog:getTargetPhoto()
if photo ~= nil then
local photoPath = photo:getRawMetadata('path')
LrShell.openFilesInApp({LrPathUtils.parent(photoPath)}, programPath)
end
endLrTasks.startAsyncTask(openWithExternalProgram, "openWithExternalProgram")
0 -
Samoreen wrote:
Please find below a variant of the script proposed above. This version will also launch C1 but instead of only proposing for editing the file selected in Lightroom, the C1 import dialog will contain all the image files stored in the folder where the selected file resides.
I may have accidentally found another way to do this. When setting up the original script's parameters, I left out step 2 â€" create a blank catalog. What happened when I invoked the script from LR was that ALL the images in the active LR folder were imported into what was an active C1 session.
I haven't tried to duplicate this yet, but I will at some point. Just thought I'd throw this out there in case anyone wants to give it a try.0 -
Filthy Lucre wrote:
I may have accidentally found another way to do this. When setting up the original script's parameters, I left out step 2 â€" create a blank catalog. What happened when I invoked the script from LR was that ALL the images in the active LR folder were imported into what was an active C1 session.
Yes, this is how things work. I have explained this in the antepenultimate message of this thread :
[The Capture One forum has migrated to a new platform, as a result all links to Capture One related postsstopped working and have been removed]0 -
Samoreen, this script is working so well for me. I don't know how I managed without it before.
Thanks!0 -
Filthy Lucre wrote:
Samoreen, this script is working so well for me. I don't know how I managed without it before.
Thanks!
You're welcome. I think that many Lightroom users, like me, are not ready to make C1 the only tool they are working with, even if they consider that C1 has better editing tools. Lightroom has many features that are not present in C1 or that are better implemented than in C1. For example, the printing module of LR is vastly superior to what's available in C1. I use it all the time because I consider that the job is done only when the photo is hanging on the wall. C1 is a professional tool (and it is priced as such) but it doesn't provide any serious printing feature. Are professionals never printing their images ?
Actually, I tend to use Lightroom for my "business as usual" and to delegate to Photoshop, C1 or DxO Photolab or other software when it's necessary. This is where the above script and a few others come in. They are here for those who are working this way. The first version of the script above can be easily adapted to any other program. Only the line containing the path to the executable has to be modified (as well as the script name, of course).0 -
Note that the above scripts should also work on a Mac. Only a few changes are needed :
- The script should be stored in Macintosh HD/Users/[your username]/Library/Application Support/Adobe/Lightroom/Scripts .
- The executable path has to be modified and the separator should be "/" instead of "\\" .0 -
Just a message to mark this thread for future reference. I'm in the middle of de-Cataloging myself from Capture One and will investigate this as a means to continue to manage my image inventory.
Thanks for providing the script.
chris
0 -
Okay I'm FINALLY getting back to this and I need some assistance.
By using this on the command line in Windows:
"C:\Program Files\Capture One\CaptureOne.exe" /SetAsCaptureFolder "%1"
with the entire image path (not just the file name) as the input (%1), Capture One will open in a Session with just that photo highlighted as an unnamed album.
This is EXACTLY what I'm looking for, but the script above does not provide the full path name as best I can tell.
So two questions:
- How can I call out the program with the flag? ""C:\Program Files\Capture One\CaptureOne.exe" /SetAsCaptureFolder"
- How can I get LR to provide the entire path string?
Thanks!
chris
0 -
Okay,
This was interesting. Here is the code I used:
local LrApplication = import 'LrApplication'
local LrTasks = import 'LrTasks'
local LrShell = import 'LrShell'
local catalog = LrApplication.activeCatalog()
local LrShell = import 'LrShell'local function openWithExternalProgram()
local programPath = '"C:\\Program Files\\Capture One\\CaptureOne.exe"'
local photo = catalog:getTargetPhoto()
if photo ~= nil then
local photoPath = photo:getRawMetadata('path')
LrTasks.execute(programPath..' /SetAsCaptureFolder'..photoPath)
end
endLrTasks.startAsyncTask(openWithExternalProgram, "openWithExternalProgram")
Allegedly "LrShell.openPathsViaCommandLine( files, appPath, extraArgs )" can be used for this purpose, but I could not make it work. Nothing happened.
This codes opens C1 in a default session and shows only the selected image as an "untitled Album"
0
Post ist für Kommentare geschlossen.
Kommentare
18 Kommentare