C1 as a raw develloper only
Hi
I'm using IdImager Supreme V3 as the DAM tool for my images and trialing C1 8 right now. I want to see how the highlight recovery is compared to Canon DPP4 and DxO9.
However I "struggle" with basic opening of single files (Canon CR2). I don't want C1 to make additional databases or it's like, just make the "perfect" raw conversion, save it back to it's original folder as jpg/tif and thats it.
I get this feeling that C1 wants to make new session/imports/capture folder/catalogs/databases/new subfolders/etc all the time, not just open a file and I'm afraid that if I click or forget to click somewhere i might "pollute" my filesystem with lots of additional files...
So my question, is it possible to send/open a file directely in C1, adjust and save it back to the original folder??
Regards
Rune
(This post got initially placed in the wrong forum (Mac), which I deleted and reposted here - sorry)
I'm using IdImager Supreme V3 as the DAM tool for my images and trialing C1 8 right now. I want to see how the highlight recovery is compared to Canon DPP4 and DxO9.
However I "struggle" with basic opening of single files (Canon CR2). I don't want C1 to make additional databases or it's like, just make the "perfect" raw conversion, save it back to it's original folder as jpg/tif and thats it.
I get this feeling that C1 wants to make new session/imports/capture folder/catalogs/databases/new subfolders/etc all the time, not just open a file and I'm afraid that if I click or forget to click somewhere i might "pollute" my filesystem with lots of additional files...
So my question, is it possible to send/open a file directely in C1, adjust and save it back to the original folder??
Regards
Rune
(This post got initially placed in the wrong forum (Mac), which I deleted and reposted here - sorry)
0
-
Your best bet is to use sessions. Just start with the default unnamed session (as you are going to use this one session for everything ever after no real need to name it). Ignore the odds and ends of sessions proper and just go straight to the directory structure and open the directory with the picture you want to edit in it. Carry out your editing of the RAW file, COne will generate a sidecar sub-directory with your edits and pre-views in the same directory, this sub-directory contains the edits for the RAW files you edited and thumbnails for all the RAW files in that particular directory. If you want to output TIFF or jpeg then you can identify where you want those stored as part of the output recipe.
This way of working means that if you have RAW files in hundreds of different directories they are all available from COne but COne data is only stored for those you actually open in COne. This is different than working with catalogues where everything is catalogued and your edits are stored in one this one hugh catalogue.
If you don`t want to keep the COne edits it is just an extra step to delete the CaptureOne directory that was generated in the directory holding the RAW file you edited. This will not affect your originals or the tiff or jpeg you outputed.0 -
Untitled Session is what i use with C1, i just browse to the directory with the RAW files i want to edit and let C1 generate the previews and when done, export to where i want in the process recipe. 0 -
Thank You for taking Your time.
C1 feels quite overwhelming when starting up by select this and name that especially since I have no intentions of using any of it's cataloging capabilities.
Also, I don't feel overly happy about it adding a new subfolder assosiated with every file it develops instead of one common db file - well anyway thats how they do it and I'll give it a try for about 60days then I'll see
Rune 😊0 -
[quote="Rune2" wrote:
Thank You for taking Your time.
C1 feels quite overwhelming when starting up by select this and name that especially since I have no intentions of using any of it's cataloging capabilities.
Also, I don't feel overly happy about it adding a new subfolder assosiated with every file it develops instead of one common db file - well anyway thats how they do it and I'll give it a try for about 60days then I'll see
Rune 😊
Just to be clear if you have a folder with say 20 RAW files in it then only one sub-folder is created in that folder whether you edit one file or all 20. This is different than using Bridge and Photoshop where one .xmp file is generated for every RAW file edited.0 -
Hello Rune2
Your reaction to C1 is very similar to mine, when I first tried to get to grips with the Phase use of sessions and catalogues.
After some experimentation and forum exchanges I realised I can bypass all that official stuff and go direct to the raw files in the Windows system folders. Then, after opening and processing the image file at least I feel I know what I am doing and how the software will deal with my outputs which are automatically saved to the original raw folder. Very tidy.
Peter0 -
Same here,
curious to your findings0 -
Hi
I haven't been into the forum for some time now.
After a week I got tired of C1 always having to read/scan through my folders building thumbs for all files (even though I only sent one or two raw files to it) instead of just open the raw - lots of waisted time.
Also I had some occasions with some kind of malformed exif/xmp info written to the outcome file (jpg/tiff) which I suspected C1 of, so I just got tired and uninstalled C1.
I'll continue to use Canon DPP4/DxO9 or 10 if I upgrade, maybe I'll look into the Ninja - though Lightzone is out there too...
I'd just wish Phase One would release a version of C1 that worked as a raw converter only.
A version that would take only the raw files it was feed, develop them as ordered, name them and put them where the user wanted them to be. Easy peasy0 -
Hi Rune
But your ideal workflow already exists in C1?! Just use the Windows system folders as your base, process the raws and convert to tifs with an auto-customised appended name and save back in the original folder.
In v8 I can even click on a raw file and open it directly in C1 (previously I had to open C1 first).
Hope this helps.
Peter0 -
[quote="Rune2" wrote:
I'd just wish Phase One would release a version of C1 that worked as a raw converter only.
They had one - Express - but they unceremoniously pulled the plug on it with release 8 (after we had to drag a version out of Phase One, kicking and screaming, when they initially dropped it in release 7); but as Peter says, you can do what you want to do in 8 anyway.0 -
Hi Peter
I could do that, but why would I dismiss using my brilliant DAM software that has been my hub for everything photorelated since 2007.
IDi Supreme is possibly one of the best DAM tools for organizing, cataloging and managing ones pictures and I fear that doing lots of file work outside the DAM will kind of put my database out of sync making things complicated, better to keep my work inside it.
IDi Supreme downloads my files, renames them, sends them to culling (FastPictureViewer), tag them, search them, sends the best to my raw converter, version them, sends them to Qimage, to FB, to Zenfolio to mail to whatever - Basically I just wanted a very good raw converter (C1 if You wondered 😊 to fit into that flow.
Maybe it's my loss, but as of now C1 v8 doesn't fit into that bill - Maybe they'll release a light/express version again and I might be back. I did use v3 and 4 a long time ago...
regards
Rune 😊0 -
Actually i use combination of Capture One and Photo Supreme. It works just fine, v3 of photo supreme brought support for capture one 8 sidecars and rough support for its corrections.
I basically use C1 in single session, so when i want to open file from photo supreme, capture one goes straight to that file. After finishing edits in capture one just export (export can be put to original raws folder or it's subfolder automaticly) and then just verify edited folders in photo supreme to import prosessed images.
You do get that capture ones folder to each folder that you have photos edited with C1. I don't see it that bad, it means that i can move files around and don't have to worry about C1 databases as edits are in sidecars.0 -
I've been using Photo Mechanic 5 for ingesting and organising files from the camera cards. Then I open C1 and import the files in the same location, work on them, send them over to PS if there's need, and when all is done I go back to Photo Mechanic for the keywording and IPTC data and the final export. It's a bit of a pain, because C1 doesn't work with Photo Mechanic very well (i.e. the 'Send to RAW processor' feature in PM doesn't automatically open C1 and the files you send, as it does with Lightroom), but I have more control of the naming of folders and general organisation that way. The cataloging features in C1 really suck. 0 -
Suppose I have a folder with RAW files already opened and edited in Lightroom. If I then begin a C1 session on those RAW files, does C1 take any notice of the sidecar files generated by LR? And would C1 create new sidecar files that might interfere with LR? 0 -
[quote="NN635520603147723096UL" wrote:
Suppose I have a folder with RAW files already opened and edited in Lightroom. If I then begin a C1 session on those RAW files, does C1 take any notice of the sidecar files generated by LR? And would C1 create new sidecar files that might interfere with LR?
CO8 will read the metadata settings (like rating, keywords) you created with Lr on opening of the raw image. The sidecar file CO8 creates when working with a session do not interfere with Lr.0
Post is closed for comments.
Comments
14 comments