Recipe Processing creates .cos files !?
hi there. i'm in a hurry and mildly annoyed by capture one. why the heck is CO creating a "CaptureOne" folder with the .cos files when im using a processing recipe? i don't need that, i don't want that... anybody else hat this strange behaviour? as far as i can tell CO does not provide an "include adjustments" checkbox in the recipes.... thanks....t.
0
-
That's the way Capture One works. Any folder that you look at images in within Capture One (even images that have been created without using Capture One - like images downloaded from the internet) gets a Capture One subfolder with stuff in it that enables C1 to do things like display thumbnails, display previews, and yes, record adjustments you might make.
Ian0 -
[quote="Tim Hufnagl" wrote:
hi there. i'm in a hurry and mildly annoyed by capture one. why the heck is CO creating a "CaptureOne" folder with the .cos files when im using a processing recipe? i don't need that, i don't want that... anybody else hat this strange behaviour? as far as i can tell CO does not provide an "include adjustments" checkbox in the recipes.... thanks....t.
Try the Export "Originals" option if you are just shipping out the images with no interest in doing anything with them in C1.
There are tickboxes for what to include and not include. Adjustments is one of the tick box options. I have no idea whether Export might still need to create a .cos file (Capture One Settings) since they are not only for adjustment information.
HTH.
Grant0 -
[quote="Ian3" wrote:
That's the way Capture One works. Any folder that you look at images in within Capture One (even images that have been created without using Capture One - like images downloaded from the internet) gets a Capture One subfolder with stuff in it that enables C1 to do things like display thumbnails, display previews, and yes, record adjustments you might make.
Ian
That's not my experience. I use 'referenced' catalogs. As a test, I just imported some new files from a new directory. I converted one of the images to B&W and then exited Capture One. When I checked the directory, there is no '.cos' file or subfolder with Capture One information. I also tried 'export variants' and didn't get a '.cos' file.
However, when I set-up a session, there is a folder called 'CaptureOne' inside the session directory tree. This folder contains '.cos' files. But, they are not in the directory containing my original images. Exporting still did not create '.cos' files.
Maybe I am missing something, or have a different catalog set-up then you are using.
I thought that, at least with a reference catalog, things like thumbnails and previews were stored inside the catalog file, not in separate sidecar files.0 -
[quote="nbirkett" wrote:
[quote="Ian3" wrote:
That's the way Capture One works. Any folder that you look at images in within Capture One (even images that have been created without using Capture One - like images downloaded from the internet) gets a Capture One subfolder with stuff in it that enables C1 to do things like display thumbnails, display previews, and yes, record adjustments you might make.
Ian
That's not my experience. I use 'referenced' catalogs. As a test, I just imported some new files from a new directory. I converted one of the images to B&W and then exited Capture One. When I checked the directory, there is no '.cos' file or subfolder with Capture One information. I also tried 'export variants' and didn't get a '.cos' file.
Maybe I am missing something, or have a different catalog set-up then you are using.
I thought that, at least with a reference catalog, things like thumbnails and previews were stored inside the catalog file, not in separate sidecar files.
Ah. I'm using Sessions - perhaps the OP is too?
Ian0 -
[quote="SFA" wrote:
[quote="Tim Hufnagl" wrote:
hi there. i'm in a hurry and mildly annoyed by capture one. why the heck is CO creating a "CaptureOne" folder with the .cos files when im using a processing recipe? i don't need that, i don't want that... anybody else hat this strange behaviour? as far as i can tell CO does not provide an "include adjustments" checkbox in the recipes.... thanks....t.
Try the Export "Originals" option if you are just shipping out the images with no interest in doing anything with them in C1.
There are tickboxes for what to include and not include. Adjustments is one of the tick box options. I have no idea whether Export might still need to create a .cos file (Capture One Settings) since they are not only for adjustment information.
HTH.
Grant
But if you export originals, by definition you don't include adjustments...
Ian0 -
[quote="Ian3" wrote:
Ah. I'm using Sessions - perhaps the OP is too?
Ian
Oops. My edit and your post over-lapped 😊 I tested out sessions and did find the folder with '.cos' files but that is inside the session directory tree and are not in the same directory/folder as the images, either the original or the exported edited files.
Some more testing (I am still learning a lot about Capture One): when you export images from a Session, CaptureOne exports the edited image according to the recipe. But, in the output foled you select, is also creates a 'CaptureOne' folder with '.cos' files (this is likely what the OP is seeing). But, you don't need to use the '.cos' files to see the edited image (I moved the images to another directory with no ill effects).0 -
It is in the session directory structure, but if you open any folder with images in it via the System folders in the C1 library tab (such as your Documents folder where there might be an image) you will find C1 will create a Capture One subfolder there and a sub-subfolder with the .cos files etc.
Ian0 -
[quote="Ian3" wrote:
It is in the session directory structure, but if you open any folder with images in it via the System folders in the C1 library tab (such as your Documents folder where there might be an image) you will find C1 will create a Capture One subfolder there and a sub-subfolder with the .cos files etc.
Ian
I think that this behaviour only applies within Sessions. I see that happen when I have a session open. But, not when I work with a referenced catalog. And, the '.cos' files are not needed to correctly view exported images.0 -
[quote="nbirkett" wrote:
[quote="Ian3" wrote:
It is in the session directory structure, but if you open any folder with images in it via the System folders in the C1 library tab (such as your Documents folder where there might be an image) you will find C1 will create a Capture One subfolder there and a sub-subfolder with the .cos files etc.
Ian
I think that this behaviour only applies within Sessions. I see that happen when I have a session open. But, not when I work with a referenced catalog. And, the '.cos' files are not needed to correctly view exported images.
No they aren't needed, I suppose, until you do something to an exported image, such as crop it, etc.
Ian0 -
[quote="Ian3" wrote:
[
No they aren't needed, I suppose, until you do something to an exported image, such as crop it, etc.
Ian
If your goal is to export an image that can be re-imported into CaptureOne on a different computer, then i agree - the exported images are 'frozen' and you can not go back and undo edits like cropping. You can, however, apply new edits. But, I thought that the intent of 'exporting was to create a file with the editing fixed in the file?
Is the OP tying to transfer images so that editing can be continued in another version of CaptureOne? If so, why not just copy the 'capture' folder from the session to the new computer? Then, you can import the image files into a referenced (or managed) catalog on the new computer. The adjustments are stored in the CaptureOne folder inside the Capture folder and, if you check the 'apply adjustments', the edits from the session are applied to the image after import. The changes are then stored in the catalog and you can deleted the CaptureOne folder if you want. This lets you change any of the edits applied during your Session work, as well as apply new ones.0 -
Ian,
I think your reading of the description of the problem was more complete than mine.
An exported (via Process) folder re-read into C1 will indeed be treated as some new files that can potentially be edited. It's not exactly how I read the description of the problem first time around.
And in terms of the discussion about sending the adjustments with the export the official answer would of course be to create EIP files. But that is an export concept rather than a process as it might be most widely understood.
HTH.
Grant0 -
wow, thanks for all your feedback and comments. me, the OP, is using process recipes to do exactly this: print (render) my final delivery formats to my customers. i'm exporting directly to final location and am 100% sure in the past (using sessions for ages) there was no additional .cos files created as a result of rendering final assets from the processing recipes, esp since i'm using multiple recipes at the same time for different formats, resolutions and colour spaces.
yes, using "export originals" with the "include adjustments" checkbox ticked does exactly this: RAW + .cos (+ masks). also the "reimport after export" is not checked, so CO would NOT look at the files in the first place. BTW: CO does only create the adjustments in case there were adjustments made. if you don't touch any of the faders, no adjustment files will be created. again, pls. mind i'm using sessions for easy archiving and exchange, where adjustments are store with the RAW file as sidecar files..
maybe some phase one team member could clarify this behaviour, which seems new (and odd) to me.
thx,
t0 -
It only creates the CaptureOne folder, .cos files and so on when the output folder itself is viewed/used within CO.
As long as I don't open the output folder in CO, I don't have them.
Saving the output folder as a session favorite may have some effect, too. I didn't check that.
Regards,
Hans0 -
Tim,
What do you mean by "final location"? Somewhere in your web server? Or on a remote storage service like Dropbox?
Like you, I have never previously seen a cos file in a folder unless I have browsed it from within C1. (Other than eip exports which I have never used other than experimenting.)
Are we looking at V10.2 here?
Grant0 -
[quote="HansB" wrote:
It only creates the CaptureOne folder, .cos files and so on when the output folder itself is viewed/used within CO.
As long as I don't open the output folder in CO, I don't have them.
Saving the output folder as a session favorite may have some effect, too. I didn't check that.
Regards,
Hans
I created a new session. Copied some files into the 'capture' directory. I opened the session in Capture One, accessed a file in the 'capture' folder and converted one file to B&W. When I checked the 'Capture' directory using 'finder', there is a 'CaptureOne' folder with .cos'.
I then used process output to export a dng file into 'output'. As soon as it was processed, I exited Capture One (I did not look at the image in the Output folder). When I checked the 'output' directory in finder, there was a CaptureOne folder with .cos file. Since I neither viewed nor used the output folder within Capture One, this seems to raise questions with the above statement.0 -
I didn't process the images into the session's 'Output' folder because this a folder which is definitely used by CO's session.
I defined a separate path in 'Process Recipe' - 'File' - 'Root Folder', pointing to a totally different location. And after processing some more images to jpg and tiff, I still don't have any sidecars there. CO closed and re-opened.
Regards,
Hans0 -
[quote="nbirkett" wrote:
[quote="HansB" wrote:
It only creates the CaptureOne folder, .cos files and so on when the output folder itself is viewed/used within CO.
As long as I don't open the output folder in CO, I don't have them.
Saving the output folder as a session favorite may have some effect, too. I didn't check that.
Regards,
Hans
I created a new session. Copied some files into the 'capture' directory. I opened the session in Capture One, accessed a file in the 'capture' folder and converted one file to B&W. When I checked the 'Capture' directory using 'finder', there is a 'CaptureOne' folder with .cos'.
I then used process output to export a dng file into 'output'. As soon as it was processed, I exited Capture One (I did not look at the image in the Output folder). When I checked the 'output' directory in finder, there was a CaptureOne folder with .cos file. Since I neither viewed nor used the output folder within Capture One, this seems to raise questions with the above statement.
I have never seen anything like that. However I am using Windows 7 and it is possible, I guess, after the last round of OS updates, that something "under the hood" has changed and under certain conditions a cos file is written unexpectedly.
Time to raise a Support Case?
Grant0 -
[quote="SFA" wrote:
[quote="nbirkett" wrote:
[quote="HansB" wrote:
It only creates the CaptureOne folder, .cos files and so on when the output folder itself is viewed/used within CO.
As long as I don't open the output folder in CO, I don't have them.
Saving the output folder as a session favorite may have some effect, too. I didn't check that.
Regards,
Hans
I created a new session. Copied some files into the 'capture' directory. I opened the session in Capture One, accessed a file in the 'capture' folder and converted one file to B&W. When I checked the 'Capture' directory using 'finder', there is a 'CaptureOne' folder with .cos'.
I then used process output to export a dng file into 'output'. As soon as it was processed, I exited Capture One (I did not look at the image in the Output folder). When I checked the 'output' directory in finder, there was a CaptureOne folder with .cos file. Since I neither viewed nor used the output folder within Capture One, this seems to raise questions with the above statement.
I have never seen anything like that. However I am using Windows 7 and it is possible, I guess, after the last round of OS updates, that something "under the hood" has changed and under certain conditions a cos file is written unexpectedly.
Time to raise a Support Case?
Grant
Yeah, I checked here and it doesn't create the Capture One folder until I go back and select the Output folder.
Windows 10 Pro 1703 build 15063.674
Edit: It doesn't sound like much of an issue, although it could be a clue to some other inconsistency; so worth raising to support...0 -
[quote="gusferlizi" wrote:
[quote="SFA" wrote:
Yeah, I checked here and it doesn't create the Capture One folder until I go back and select the Output folder.
Windows 10 Pro 1703 build 15063.674
Edit: It doesn't sound like much of an issue, although it could be a clue to some other inconsistency; so worth raising to support...
Interesting. I using an iMac with Sierra. Could it be a Mac/Windows difference?0 -
[quote="gusferlizi" wrote:
Edit: It doesn't sound like much of an issue, although it could be a clue to some other inconsistency; so worth raising to support...
Exactly my thoughts too after the recent issues with Windows 10 creators update and the subsequent discovery of temporary cos files that were left lying around during editing activity.
Developers can never be too careful when dealing with OS system "updates" these days!
Grant0
Post is closed for comments.
Comments
20 comments