Workflow w/PSDs + Catalog Size Questions
Hi all,
I am currently a LR6 user, but my goal is to migrate completely over to Capture One which I just purchased today. I've spent some time going through tutorials / this forum, but I still have a couple of questions which I'm hoping people might be able to offer some guidance on.
First up, I do a lot of retouch work in Photoshop CC, in my current workflow in LR, I simply export the raw file in to PS, save the finished file as a psd and it automatically repopulates back in to LR. I've read that Capture One has recently introduced the ability to do something similar, but only when working with tiff files. For someone that wants to stick with psds, what are my options? I really was hoping to ditch LR, purely from a simplicity point of view, but I'm starting to think that might not be possible. Do people literally just create a catalog of Photoshop files in LR? Any pointers would be really appreciated.
Next up, I like having one master catalog for the ability to quickly search / browse through all my work. In LR, this works fine, but I'm slightly nervous about doing the same in Capture One as I've read it gets sluggish very quickly when working with large catalogs. By large, I mean 10,000+ photos, so by a lot of measures, actually quite small... My plan is to use sessions when shooting tethered for a client, then when the job is ready to archive, I would import that session in to my master catalog. Does anyone else use a similar DAM setup / run a large catalog?
Thanks,
Nick
P.S. - Not sure what the deal is with my username!
I am currently a LR6 user, but my goal is to migrate completely over to Capture One which I just purchased today. I've spent some time going through tutorials / this forum, but I still have a couple of questions which I'm hoping people might be able to offer some guidance on.
First up, I do a lot of retouch work in Photoshop CC, in my current workflow in LR, I simply export the raw file in to PS, save the finished file as a psd and it automatically repopulates back in to LR. I've read that Capture One has recently introduced the ability to do something similar, but only when working with tiff files. For someone that wants to stick with psds, what are my options? I really was hoping to ditch LR, purely from a simplicity point of view, but I'm starting to think that might not be possible. Do people literally just create a catalog of Photoshop files in LR? Any pointers would be really appreciated.
Next up, I like having one master catalog for the ability to quickly search / browse through all my work. In LR, this works fine, but I'm slightly nervous about doing the same in Capture One as I've read it gets sluggish very quickly when working with large catalogs. By large, I mean 10,000+ photos, so by a lot of measures, actually quite small... My plan is to use sessions when shooting tethered for a client, then when the job is ready to archive, I would import that session in to my master catalog. Does anyone else use a similar DAM setup / run a large catalog?
Thanks,
Nick
P.S. - Not sure what the deal is with my username!
0
-
About the PSD issue, consider TIFF instead. I think you lose nothing and gain a lot. 0 -
Hi Paul,
Thanks for responding. I must admit, I am not particularly familiar with the tiff format, except for using it to print from as a flattered file. Out of curiosity, I just created a file with a few layers and adjustment layers and saved it out two times, once as a psd and once as a tif with zero compression. The psd file is ~172mb, the tif is ~217mb. That's a pretty big increase on what is quite a simple file. I guess I could live with that, if there's literally no other down side with the format.0 -
You still have the problem with TIFF if they are not flattened that CO8 will not render them. So if you leave your PSD's currently with layers, moving to TIFFs will not gain you anything.
Robert0 -
Oh really? I didn't know that. That's kind of disappointing. So in that case there really isn't a way for CO to handle the outputted files.
Could anyone chip in on catalog size? In terms of whether it's advisable or not with regards to slowdown etc.0 -
As stated many times it fine to use catalog for archiving , and I constantly have catalogs created that are larger then 10K for processing without any issue, not if having larger catalog the only problem is startup time so on 24K catalog C1 on my machines start around 2-3 mins, So I chunk them on per client basics. Hope that helps 0
Post ist für Kommentare geschlossen.
Kommentare
5 Kommentare