Hello: My apologies for the lengthy initial post. I thought it would be enjoyable to explain to everyone how I’ve successfully (for me) integrated Capture One with Phocus. I could go on regarding my file management protocol so if anyone has questions/thoughts, feel free.
Love, love the x2d100C and my first 2 lenses, the P25, and 75. I’ve been a Capture One guy for well over a decade. I’m aware of numerous pro shooters that would buy into the x2d system, IF the system functioned with C1Pro. I know why they don’t play well together, but the politics of that are for another thread.
Here’s my software workaround that I find easily workable.
My workflow for jobs centers around the C1Pro session infrastructure. Being a contained package of 4 subfolders and the c1 database, I can move a session anywhere I want and continue a job. I have a job number system, which is embedded in the name of the session folder. The capture name includes part of the job number. Easy to archive and find any image I want. I also have sessions for my portfolios and family activities. I don’t care for LR primarily because I don’t have any need for its files management integration. For file management, I use Excire, along with client name, sequential job number by year. Very simple, and quite easy to retrieve any image quickly.
Initially, I started shooting the x2d, completely forgetting the session mindset when attempting Phocus. Big mistake, because as fantastic as the x2d camera menu system is, I find it weird that the same software team has developed such a counter-intuitive system in Phocus. (Mobile is marginally better IMO). Just my opinion.
I use Phocus only to the point of grading the raws to allow me to export a Phocus raw to a tiff. I add another folder into my C1Pro session called x2d RAWS. That’ where the exported tiffs end up in my job. Doesn’t matter that the Phocus raws can’t communicate with the C1Pro software. The Tiffs do and if processed properly, the files reproduce well! Another big plus, tethering using Phocus for the Mac is super simple, with a naming convention even easier than C1Pro. Wherever the job session moves, the Phocus raws for that session are included. When I archive a job, the entire package is archived.
Thanks for the time!
Love, love the x2d100C and my first 2 lenses, the P25, and 75. I’ve been a Capture One guy for well over a decade. I’m aware of numerous pro shooters that would buy into the x2d system, IF the system functioned with C1Pro. I know why they don’t play well together, but the politics of that are for another thread.
Here’s my software workaround that I find easily workable.
My workflow for jobs centers around the C1Pro session infrastructure. Being a contained package of 4 subfolders and the c1 database, I can move a session anywhere I want and continue a job. I have a job number system, which is embedded in the name of the session folder. The capture name includes part of the job number. Easy to archive and find any image I want. I also have sessions for my portfolios and family activities. I don’t care for LR primarily because I don’t have any need for its files management integration. For file management, I use Excire, along with client name, sequential job number by year. Very simple, and quite easy to retrieve any image quickly.
Initially, I started shooting the x2d, completely forgetting the session mindset when attempting Phocus. Big mistake, because as fantastic as the x2d camera menu system is, I find it weird that the same software team has developed such a counter-intuitive system in Phocus. (Mobile is marginally better IMO). Just my opinion.
I use Phocus only to the point of grading the raws to allow me to export a Phocus raw to a tiff. I add another folder into my C1Pro session called x2d RAWS. That’ where the exported tiffs end up in my job. Doesn’t matter that the Phocus raws can’t communicate with the C1Pro software. The Tiffs do and if processed properly, the files reproduce well! Another big plus, tethering using Phocus for the Mac is super simple, with a naming convention even easier than C1Pro. Wherever the job session moves, the Phocus raws for that session are included. When I archive a job, the entire package is archived.
Thanks for the time!