The GetDPI Photography Forum

Great to see you here. Join our insightful photographic forum today and start tapping into a huge wealth of photographic knowledge. Completing our simple registration process will allow you to gain access to exclusive content, add your own topics and posts, share your work and connect with other members through your own private inbox! And don’t forget to say hi!

Using C1 with Lightroom

eleanorbrown

New member
I began using C1 with my P25 however eventually switched to Lightroom after viewing Michael's very excellent tutorials, for subsequent use with my P45, then 45+ along with canon RAW files. About 6 months ago i decided to get reacquainted with C1 and to my pleasant surprise I found it superior to Lightroom so I'm back using C1 for all RAW processing. Want to make one additional point and that's i find the sharpening in C1 far superior to the Lightroom sharpening in it's ability to define fine detail in my RAW files. C1 works some magic here! Eleanor
 

jonoslack

Active member
Why not do all your raw conversions with C1? It's browser, ranking and editing functions are at least as fast as LR's, and you have optional "move to" folders within each session.

Bottom line is all that is required to use C1 efficiently is get your arms around its "session" concept. Once you grasp that and begin to use them, its workflow all starts to make sense.

;),
HI There Jack
I think there are two points here -

First Point
If you are actually doing 'sessions' - ie, a wedding, a concert, a PR shoot a holiday, which some pros are doing most of the time, then it works really well.
However, if you're shooting landscape / family or simply revisiting the same school frequently to do student portraits, there is a continuum which really demands efficient keywording and cataloguing. For instance, I've been taking photos of a particular beach in Cornwall for 30 years - sometimes with family members, sometimes with friends, sometimes in winter, sometimes in summer. There is no way of cataloguing this with any kind of folder structure - key words in LR or Aperture make this easy.

Second Point
Converting is old stuff! Seriously, given that you might want to pull together a lot of images for a book / website / brochure / catalogue or whatever, if you've used conversion software and then filed away the original RAW files, but you need to have consistent processing for the 'whatever it is'. Then you're stuck with trawling through your backups finding the old RAW files to reprocess.

Use Aperture or Lightroom, and you don't do the conversion except for outputting to your victim for specific projects. This means that doing the book / website / brochure simply means a keyword search, a new project which holds the virtual 'versions' you want.

Like most people here, I've used C1 on and off for a long time, and I keep considering using it full time . . .but it always comes back to these two points which keeps me with Aperture.
 

jonoslack

Active member
My structure is software independent for the very reason we are discussing now --- what to do when something superior comes along that isn't supported by or won't integrate with your "old" software?
HI Jack
So is my structure - Year / Month / session.
I keep it like that and simply reference the files in Aperture (you can do the same in Lightroom). Hiding them away in the library seems like complete madness.

As you say - it matches very well with the C1 structure - but as I pointed out above, the problem arises when you want to pull together images from many different folders for a particular project . . . one that you weren't aware of when you started shooting.
 

jonoslack

Active member
I know this thread is primarily about using C1 with Lightroom.
I also know that the motivation for LR users is that the C1 conversions are better (I think we all agree).

What I don't quite understand is why there is almost no mention of Aperture - despite the fact that it's conversions are (for many cameras) a great deal better than LR, and often close to C1, and it does have all the DAM advantages of LR?
 

Ben Rubinstein

Active member
Mac only mate, does kind of cut the talk down to mac only users...

As regards Charles post, you can do exactly the same stuff in Bridge, with the advantage of multiple workspaces based on your particular needs at the time, oh and you're working with the real files not a database.
 

jonoslack

Active member
Mac only mate, does kind of cut the talk down to mac only users...

As regards Charles post, you can do exactly the same stuff in Bridge, with the advantage of multiple workspaces based on your particular needs at the time, oh and you're working with the real files not a database.
Hmm - does bridge do versions? Collections? But whatever, you are still stuck with ACR for the conversion.
 

charlesphoto

New member
Mac only mate, does kind of cut the talk down to mac only users...

As regards Charles post, you can do exactly the same stuff in Bridge, with the advantage of multiple workspaces based on your particular needs at the time, oh and you're working with the real files not a database.
Hmmm, not really. Yes, Bridge is good for within individual folders, but LR really comes into it's own when one, as Jono points out, you need to bring together many images from different places into one cohesive body. All depends on the type of work one does I guess.
 

jonoslack

Active member
oh and you're working with the real files not a database.
Isn't it working with a database which is the REAL advantage - you can have one RAW file, and as many interpretations as you like - black and white / cropped with a template for a book / over-saturated for the cheap thrills brigade etc. etc. . . . but you still only have the one disc file.

I think you just wrote off the BIG advantage of DAM's in a single line! But I don't think you were right.
:)
 

Jack

Sr. Administrator
Staff member
However, if you're shooting landscape / family or simply revisiting the same school frequently to do student portraits, there is a continuum which really demands efficient keywording and cataloguing.
Hi Jono,

I shoot a lot of landscape and family stuff and don't keyword, and have no issues finding my stuff even from several years back.

Converting is old stuff! Seriously, given that you might want to pull together a lot of images for a book / website / brochure / catalogue or whatever, if you've used conversion software and then filed away the original RAW files, but you need to have consistent processing for the 'whatever it is'. Then you're stuck with trawling through your backups finding the old RAW files to reprocess.
Here I disagree too. If you output a LR image to CS, as a tiff, or as a jpeg for web, your raw has been converted :D. That out of the way, I can pretty easily pull images from any session or non-sessioned folder together and if I need to reprocess, I just output them to a new output location. I can even create a new variant and save it with say a unique name for the project before outputting it, and thus always get to back to any specific conversion for that project.

So in the end, I still don't need LR's specific DAM capabilities. And moreover, don't have to put up with what I view as a lesser conversion tool for my raw files.

Cheers,
 

Ben Rubinstein

Active member
Isn't it working with a database which is the REAL advantage - you can have one RAW file, and as many interpretations as you like - black and white / cropped with a template for a book / over-saturated for the cheap thrills brigade etc. etc. . . . but you still only have the one disc file.

I think you just wrote off the BIG advantage of DAM's in a single line! But I don't think you were right.
:)
It's called 'snapshots' in ACR. You can save as many versions of your processing as you choose and they are saved into the DNG file (or sidecar file) not into a database. I use it the whole time.
 

jonoslack

Active member
Hi Jono,

I shoot a lot of landscape and family stuff and don't keyword, and have no issues finding my stuff even from several years back.
I'm interested - how on earth do you find it if you don't even remember that you've taken it?

Sorry - that sounds sarcastic, I'm interested - and I think that the discussion is useful for others . For example - I took a picture on a beach in cornwall in 2004 of my mate Neil, who I see every year or so.

it's keyworded 'pednevounder' (beach) 'cornwall' 'friends' 'Neil Brockbank' and filed in a folder:

2004/06 June/Cornwall/D2x

I need to find some shots of Neil as he want's stuff for the band website. I don't even remember the day on the beach, let alone that Neil was there or that I took a picture of him. But all I have to do is to bung 'Neil' in the search and it's found (together with a load of other shots I've forgotten).

I'm sure you can do the same - but I'd love to know how?
Your system sounds to me EXACTLY what I used until a couple of years ago - the idea of going back to it fills me with horror! But perhaps I'm missing something fundamental here?

Here I disagree too. If you output a LR image to CS, as a tiff, or as a jpeg for web, your raw has been converted :D.
Absolutely - and it shows as a different version - I'm not disputing it . . . BUT
For web you send it to the relevant web page and delete it - as you would do for output to clients. The actual mods are held in a version, the output files themselves can then be deleted. In each case the versions used for the job can be held in a special 'project' or 'folder' within the DAM - but with no disk files associated with them - on the other hand the disk files can be re-created easily.
That out of the way, I can pretty easily pull images from any session or non-sessioned folder together and if I need to reprocess, I just output them to a new output location.
I can even create a new variant and save it with say a unique name for the project before outputting it, and thus always get to back to any specific conversion for that project.
But then you end up with lots of versions of files - of course, you can always get back to them - but if it's a new project you'll need to see which one best suits your needs, which can be time consuming and certainly takes up lots of space

So in the end, I still don't need LR's specific DAM capabilities. And moreover, don't have to put up with what I view as a lesser conversion tool for my raw files.
Well, quite agree about lightroom's RAW decoding . . . . so - back to my other question - what's wrong with Aperture?
 
Last edited:

jonoslack

Active member
It's called 'snapshots' in ACR. You can save as many versions of your processing as you choose and they are saved into the DNG file (or sidecar file) not into a database. I use it the whole time.
Hi Ben
again - see my note to Jack. I'm interested here. I didn't know about snapshots.
See my description above with respect to pictures of poor old Neil. How would you pick a number of versions shot over the years and pull them together in once place (without creating a new folder with a whole new bunch of files)
 

Ben Rubinstein

Active member
Snapshots are within ACR. You save each version as a 'snapshot' of all the settings but it's all within the DNG or Sidecar file. You don't have multiple copies of the DNG (though you can do that as well using the 'save as DNG' feature in ACR). Basically you have the single file but when you open it in ACR you can view, edit and save all the snapshots you have made. The one that shows up in the preview is the one last viewed. Not sure how it works in LR.

As for collections, you can of course keyword and do a search to locate all files with that keywording just as with LR. Grouping them together in a collection is a feature of database design and isn't relevant to a system where you are working with the files themselves. You can of course create a new folder, search 'cornwall' and then copy all the files into the new folder. I'm a wedding shooter, I don't need collections as a stock shooter might.
 

jonoslack

Active member
Snapshots are within ACR. You save each version as a 'snapshot' of all the settings but it's all within the DNG or Sidecar file. You don't have multiple copies of the DNG (though you can do that as well using the 'save as DNG' feature in ACR). Basically you have the single file but when you open it in ACR you can view, edit and save all the snapshots you have made. The one that shows up in the preview is the one last viewed. Not sure how it works in LR.

As for collections, you can of course keyword and do a search to locate all files with that keywording just as with LR. Grouping them together in a collection is a feature of database design and isn't relevant to a system where you are working with the files themselves. You can of course create a new folder, search 'cornwall' and then copy all the files into the new folder. I'm a wedding shooter, I don't need collections as a stock shooter might.

Thanks Ben
I understand about snapshots - clearly an analogy for 'versions' in LR and Aperture.

Collections - I understand you don't need it - pretty much as I suggested in my original comments - if your work consists of discrete events then it isn't important, but it's one of those things which is fantastic when you get used to it.

However - saying that it 'isn't relevant if you're working with the files themselves' is , I think, a matter of opinion. If you want to use a file multiple times in different contexts, then it's very relevant. Remember too that just because you have a database doesn't mean you aren't working with the files themselves.
 

Ben Rubinstein

Active member
I meant 'not relevant' in that it would be impossible to implement outside of a database system. Not that it's not relevant to users.
 

jonoslack

Active member
I meant 'not relevant' in that it would be impossible to implement outside of a database system. Not that it's not relevant to users.
Hi Ben
Thanks for that.
Perhaps these posts should have been in another thread entitled "To be Dammed or not to be Dammed" or something like that.
I think that there are some important concepts around which aren't necessarily well understood - at least as far as they relate to different workflow and software. Mind you, maybe nobody cares either :ROTFL:
 

Jack

Sr. Administrator
Staff member
I'm interested - how on earth do you find it if you don't even remember that you've taken it?
SNIP
it's keyworded 'pednevounder' (beach) 'cornwall' 'friends' 'Neil Brockbank' and filed in a folder: 2004/06 June/Cornwall/D2x
Well first off, if you took it in 2004, it wasn't keyworded by LR then because LR wasn't even a product yet. You had to at some point go back, spend an enormous amount of time and energy to get ALL(?) of your images into LR's library and keyworded, no?

In my case, I simply look in 2002, 03, 04, 05 and 05 for the "June Cornwall" folders and browse images for my buddy Neil. (And I guarantee you that took me less time than you spent keywording all those old files when you imported them into LR the first time!) When I find them, I edit them saving the variant as "Neil's Website" and output them all to a dedicated project folder. Note that the variant is not a separate file, just a sidecar set of adjustments like ACR's snapshot, though the new project folder contains processed files.

Absolutely - and it shows as a different version - I'm not disputing it . . . BUT
For web you send it to the relevant web page and delete it - as you would do for output to clients. The actual mods are held in a version, the output files themselves can then be deleted. In each case the versions used for the job can be held in a special 'project' or 'folder' within the DAM - but with no disk files associated with them - on the other hand the disk files can be re-created easily.
and
But then you end up with lots of versions of files - of course, you can always get back to them - but if it's a new project you'll need to see which one best suits your needs, which can be time consuming and certainly takes up lots of space
I can do the same with C1 under variants, although I prefer to keep the actual processed versions in their dedicated project or subfolders. I repeat, for my uses, storage space is cheap, so I do not worry a bit about having to add hard drives to my array or even having differing versions of the same file in different project folders.

Well, quite agree about lightroom's RAW decoding . . . . so - back to my other question - what's wrong with Aperture?
I don't know, I've never tried it. Bottom line is C1 works so well, I don't look anywhere else -- EXCEPT I do continue to use ACR for files not supported by C1, like the G1's for example.

Again, not saying my system is the best, only that it works for me and I do not care one iota about LR's DAM features -- especially because it is not universal, but also the time required getting the files all keyworded. I get all the keywording I need by proper naming of my session folders to begin with :)D). Moreover, I find a basic ability to search by metadata probably more valuable when in conjunction with the session and that is somewhat universal.

Cheers,
 

jonoslack

Active member
Well first off, if you took it in 2004, it wasn't keyworded by LR then because LR wasn't even a product yet. You had to at some point go back, spend an enormous amount of time and energy to get ALL(?) of your images into LR's library and keyworded, no?
HI there Jack - well, you could have keyworded in metadata before lightroom, but that's not the point.

Yes - I went back and spent a lot of time and energy keywording old files (in Aperture). I used to do a month a session, which took about an hour (for around 1000 shots), so, I guess that means 12 hours a year (if you see what I mean). Not an enormous amount of energy, and of course, nowadays when 'importing' images into lighroom or aperture (wrong word as I always leave them in their original position) you can apply generalised keywords to the shoot, and then specifics if relevant.

If you shoot any stock, or, indeed, if you want to produce a book of your sister's grandchildren for their Christmas present, then it's a huge and wonderful resource.

Of course, keywords can be exported and saved in metadata, so if you change software then you don't have to repeat the procedure.

In my case, I simply look in 2002, 03, 04, 05 and 05 for the "June Cornwall" folders and browse images for my buddy Neil. (And I guarantee you that took me less time than you spent keywording all those old files when you imported them into LR the first time!)
But you have to remember that such a file exists - it means that to be sure of finding them, you have to 'know' every file in your library. If you don't atually remember what pictures you have of Neil, then you're going to have to look through your entire library, folder by folder.

But even if you do remember the file - what if there are 20 more you need, you'll have to remember all of those as well, and perform the same sort of search.

I'll accept that finding one picture of Neil will be quicker than keywording all those pictures - but if you add in the time for finding pictures of Venice, Aunt Cynthia and Joey Bogdavitch's jewellery, then I'm going to start gaining on you!:)
When I find them, I edit them saving the variant as "Neil's Website" and output them all to a dedicated project folder. Note that the variant is not a separate file, just a sidecar set of adjustments like ACR's snapshot, though the new project folder contains processed files.


and

I can do the same with C1 under variants, although I prefer to keep the actual processed versions in their dedicated project or subfolders. I repeat, for my uses, storage space is cheap, so I do not worry a bit about having to add hard drives to my array or even having differing versions of the same file in different project folders.
I think that the 'variants' concept is well covered by quite a lot of programs now, My point having got my 256 (already rated) pictures of Neil, I can simply drag them to a web album and output them complete to a folder to ftp to whatever website. . . . then delete the output files leaving the web album with Aperture, which takes up virtually no disk space (although I recognise that isn't so important).

What's more, my Aperture library (and it's the same for LR) is on a small external hard drive which I can take with me, or take from one computer to another. All the files are referenced there with full screen thumbnails, so that if I'm away from home / office, I can still do a quick search and bring up a slide show or gallery - of course, Aperture and Lightroom are not alone in this ability - but there aren't other options which do everything.[/QUOTE]

I don't know, I've never tried it. Bottom line is C1 works so well, I don't look anywhere else -- EXCEPT I do continue to use ACR for files not supported by C1, like the G1's for example.

Again, not saying my system is the best, only that it works for me and I do not care one iota about LR's DAM features -- especially because it is not universal, but also the time required getting the files all keyworded. I get all the keywording I need by proper naming of my session folders to begin with :)D). Moreover, I find a basic ability to search by metadata probably more valuable when in conjunction with the session and that is somewhat universal.

Cheers,
Well, the proper naming of session folders is important to me as well - in fact, I use your method as far as that goes, but the keywording is universal if it's stored in the ITPC data.

Whilst I'll agree that keywording is a pain, I can't agree that you can find pictures you've forgotten without it.

'I do not care one iota about LR's DAM features' sounds awfully like 'I have absolutely no need for autofocus'!

Whatever - Jack - I'm continuing this discussion because I think that it's relevant for people who haven't tried LR or Aperture to understand that there is a level that you can't go to with C1 or CS4 and ACR on their own.

I'm not saying that my system is best either - and, with a nod back to the original title, I use C1 for some files not supported by Aperture (notably the D-lux4) - I output them as tiff files and import those into Aperture, it works fine, but it's an extra step and an extra file.
 

Diane B

New member
I'm going to stick my nose in again--at risk of having it snapped off LOL--but I just remembered 2 things that might be of relevance to some--for LR and I'm guessing for Aperture (I happen to be one of those awful 'PC folks').

I just had interest in seeing all the shots I've ever made with my Canon 85 f/1.8. My library is always available with all folders from 2000 shown--just as you two do them--year/month/date-event. I've organized them like that for quite some time--don't remember how long, but when I switched to that organization, I went back and set the earlier folders up like that (I had always organized by month/year so it was easy to reorganize). I used to use Imatch similarly to the LR library module.

For a little background--when I initially imported my folders, I imported from the original sources (my HDs are set up by years--each one has a separate drive except for 2000 and 01 and I also choose to import and copy to these drives also) so my library reflects exactly (on the left) what my Bridge/tree directory looks like (IF I had all drives connected--or my one very large backup drive which is kept offsite). BUT--for one simple thing. When I don't have the other HDs connected (years prior to 2009--my current drive), then I have nothing shown in Bridge. However, full size thumbs for my entire library are always present and available to be searched. My library is backed up on another small drive so easy to carry with me as Jono says.

So--to make a long story short about the 85 f/1.8--I simply went to metadata search, chose all dates, all cameras, 85 f/1.8 and I got every shot every taken with that lens. The metadata search is one reason why I like LR--though I am keyworded--sometimes just generically (when I import) and often more deliberately.

I sort of ran the 2 points together--so---
1) my entire organized library is always shown exactly as organized and is available to do many things with--collections, searches, etc.--whereas it is not using Bridge (or C1, DPP, etc.) because I have only my current 2009 drive connected (others may have their entire library/folders always connected though);
2) there are other ways to search besides using keywords though they probably wouldn't help find Jono's friend Neil unless he remembered the year/month or perhaps the camera/lens without a longer search--but if it was important enough, I suspect I could find substantial number of files by some of the metadata info without keywords.

Now, I'll back out of here and just watch from the side. I've used many many RCs from the beginning--and when I was shooting textiles I chose C1 for use with my Canons (reds in particular were an issue with other RCs). Now I choose LR primarily because of the library and printing modules--but also very much like the develop (RC) module in 2.3. It also allows me to process all my cameras--other RCs don't. I think this is such a personal decision that I wouldn't come down on any side--I've worked with several workflows over the past 9 years but right now LR suits me best with occasional forays to one or 2 of my other RCs--very occasionally--and easy roundtrips to PS if I need.

So--back to the more knowledgable group here.

Diane
 
Last edited:

Guy Mancuso

Administrator, Instructor
Nice post Diane and sure if the library solution is what works than it is always a good thing. LR and Aperture certainly have the advantage of there library system. I never use this type of system myself so for me and others like me that develop there own library setup these two programs mean very little to us, since we don't take advantage of that part of the software. From a purely RC point of view than things get different in regard. Now you touched on Canon Red. LOL man did you hit a sore spot with me on that one. Canon always stank it up with regard to RED and it's true color. Now things maybe different not sure but back in the day C1 was the only one that rendered RED in those files. In my experience with all the camera's that have hit my hands which is frankly way to many and all the RC out there my bottom line is I always had less tweaking to do with C1 and achieved much better results coming out of the can into C1 without a lot of work and rendered color and detail better and not too mention noise levels. LR was horrible at noise with many of the camera's now that may have changed in recent times but I am still a firm believer in learning one RC and REALLY learning it to maximize the file and your workflow. Some folks like to jump around and that is fine but it seems to me counter productive on your learning abilities and just too much to take in and not become a expert at one of them. Since software changes often it seems to learn one and know it well than on updates you can adapt much easier. But that is me and others see some advantage too using more than one. If i can't get what I need out of C1 than I will turn to PS to finish it but this really is rare when I am running production images. When I want to really work something than I will finish in PS. But for me I do things differently for certain types of work load and most folks don't have to deal with that. It does come down to personal choice and no true right or wrong RC but some are better than others in the quality of file and some are easier on the workload issue. My motto on this is pick your poison and stick with it, learn so much about it that you can almost write the program. LOL
 
Top