CO creating Settings81 folder containing .icm files
Since applying the new ICC profile created from Christian's colour corrected preset for the 7D2 to a number of my photos, I have noticed that Capture One has been creating corresponding .icm files for each RAW file.
The .icm files are being placed in ..\CaptureOne\Settings81\ folders inside the folder that contains the RAW .CR2 files
e.g.
..\Salisbury\2015-02-09\raw\CaptureOne\Settings81\IMJ_1604.CR2.cbe8dcd8375c453499212642941ade5a.icm
..\Salisbury\2015-02-09\raw\CaptureOne\Settings81\IMJ_1607.CR2.cbe8dcd8375c453499212642941ade5a.icm
Each .icm file is 217610 bytes and comparing a random selection in WinMerge, they are identical files.
This has also happened previously when I changed some of my 40D images to use the EOS-40D Generic V2 profile instead of the default EOS-40D Generic profile.
The .icm files are created when the image is exported. They are created under the source directory, not the destination directory.
There was a somewhat similar post in the Capture One 8.x Software for Mac forum () in which it was stated that the "Settings" folders should only be created for sessions.
However, I only ever use a catalog and always import from "Current Location". I would like to keep the directory structure containing my raw files free from any ancilliary files - I thought that was part of the purpose of using a catalog, that any settings and adjustments would be stored in the catalog, not with the images files.
Is this a bug?
Is it safe to delete the CaptureOne folders and contents?
How can I stop them from appearing?
Regards,
Richard
The .icm files are being placed in ..\CaptureOne\Settings81\ folders inside the folder that contains the RAW .CR2 files
e.g.
..\Salisbury\2015-02-09\raw\CaptureOne\Settings81\IMJ_1604.CR2.cbe8dcd8375c453499212642941ade5a.icm
..\Salisbury\2015-02-09\raw\CaptureOne\Settings81\IMJ_1607.CR2.cbe8dcd8375c453499212642941ade5a.icm
Each .icm file is 217610 bytes and comparing a random selection in WinMerge, they are identical files.
This has also happened previously when I changed some of my 40D images to use the EOS-40D Generic V2 profile instead of the default EOS-40D Generic profile.
The .icm files are created when the image is exported. They are created under the source directory, not the destination directory.
There was a somewhat similar post in the Capture One 8.x Software for Mac forum () in which it was stated that the "Settings" folders should only be created for sessions.
However, I only ever use a catalog and always import from "Current Location". I would like to keep the directory structure containing my raw files free from any ancilliary files - I thought that was part of the purpose of using a catalog, that any settings and adjustments would be stored in the catalog, not with the images files.
Is this a bug?
Is it safe to delete the CaptureOne folders and contents?
How can I stop them from appearing?
Regards,
Richard
0
-
Today I imported 226 Raw 7D2 files which all use the color corrected 7D2 profile by default.
Capture One has again created a CaptureOne\Settings81\ sub-folder which contains:
226 ".Color Corrected.icm" files - one for each raw file
15 ".cbe8dcd8375c453499212642941ade5a.icm" files - one for each of the 15 files I have exported as JPEG (so far).
All the .icm files are 217610 bytes, giving a total of 50MB.
Again I am using a catalog, not a session, so why is it creating all these .icm files?0 -
I also have the CaptureOne\Settings81\ sub-folder created, but mine is empty, I do not use ICC Profiles, nevertheless the folders are annoying to be present on the file system. I also use catalogs and not session.
Any ideea?
Regards,
Istvan0 -
[quote="RichardT" wrote:
Today I imported 226 Raw 7D2 files which all use the color corrected 7D2 profile by default.
Capture One has again created a CaptureOne\Settings81\ sub-folder which contains:
226 ".Color Corrected.icm" files - one for each raw file
15 ".cbe8dcd8375c453499212642941ade5a.icm" files - one for each of the 15 files I have exported as JPEG (so far).
All the .icm files are 217610 bytes, giving a total of 50MB.
Again I am using a catalog, not a session, so why is it creating all these .icm files?
Richard,
My assumption would be that as the colour adjustment based file is not part of the core set (and so controlled and managed as a fixed and known reference both now and through future updates) C1 will treat each occurrence as a user bespoke file since it has no managed central file to refer to.
That would fit with the principles of high end methods, especially related to the Medium Format market, where taking a new profile shot almost before every frame would be thought of as sensible practice.
If you want to be able to go back to re-edit at some time the safest way to ensure you have not lost your bespoke adjustment is to store it close to each and every file no matter how many times that needs to be done.
Now, there is a good case for proposing a new approach to that but whether a valid revision would be viable technically only Phase can assess. Meanwhile we can use an existing and proven approach - perhaps one not originally designed with high volume repeat usage in mind - to make the changes we want. Basically it looks like a trade off. If there is another way to make the personal files part of the central managed repository that would seem very desirable - although I have no idea what the drawbacks might be.
That's the way I see it currently. I could be wrong.
Grant
ETA - actually I think every image that has had a change of profile at some point in its edit history will be represented in the supporting Capture One folder in a Session. (Presumably a catalog too.)0 -
I raised a support case for this issue. Phase One Support are adamant that it should not happen with catalogs and they cannot reproduce it.
They have been advising me on uninstalling/reinstalling Capture One, which I have attempted to do (with a few mis-steps along the way) more times than I care to mention. However, the problem is still occurring.
At least it is no longer creating icm files when when I do an export; only when I do an import. In fact they appear as soon as I set the Import From folder in the Import Images dialog.0 -
[quote="RichardT" wrote:
I raised a support case for this issue. Phase One Support are adamant that it should not happen with catalogs and they cannot reproduce it.
They have been advising me on uninstalling/reinstalling Capture One, which I have attempted to do (with a few mis-steps along the way) more times than I care to mention. However, the problem is still occurring.
At least it is no longer creating icm files when when I do an export; only when I do an import. In fact they appear as soon as I set the Import From folder in the Import Images dialog.
Ah, OK.
I have never spent much time with catalogs.
And yes I see ICM profiles in the Settings81 folders related to my sessions.
Grant0 -
[quote="ifarkas" wrote:
I also have the CaptureOne\Settings81\ sub-folder created, but mine is empty, I do not use ICC Profiles, nevertheless the folders are annoying to be present on the file system. I also use catalogs and not session.
Any ideea?
Regards,
Istvan
Hi Istvan,
Phase One have told me they have now managed to reproduce my problem and are investigating how to fix it.
Hopefully the fix will be available in a future release.
Regards,
Richard0 -
[quote="RichardT" wrote:
Hi Istvan,
Phase One have told me they have now managed to reproduce my problem and are investigating how to fix it.
Hopefully the fix will be available in a future release.
Regards,
Richard
Hi Richard,
Thank you for the update, I just verified, it only creates the ..\CaptureOne\Settings81\ folder when I import to the specific folder (e.q. from a memory stick), but it will not create it when I include a folder with existing pictures into the catalog.
Btw. I am on OS-X, so its not platform specific.
But it is really good news if a fix will come.
Thanks again,
Istvan0 -
Hi all!
- I have the same problem
- I am using sessions
- Furtheron CO does not recognize my camera in the affected sessions
- I opened a support case (175035)
- But the only solution they offered to import my files via copying
(I used Nikon Transfer 2 for that).
Any ideas/help?
Peter0 -
[quote="NN132823UL" wrote:
Hi all!
- I have the same problem
- I am using sessions
If you are using sessions, CO8 will *always* create Settings81 subfolders. These can contain .icm files when you use custom profiles. Is this the case?
I do not understand what you mean with 'does not recognise my camera'. Are you trying to import or tether? If import, cameras are never recognised. Always use a card reader. Connecting is tethering for CO8.0 -
Hi Paul!
1.)
>If you are using sessions, CO8 will *always* create Settings81 subfolders. These can contain .icm files when you use custom >profiles. Is this the case?
- It is clear, that there is always a Seetings81 subfolder
- But normaly you just find one type of files there: <filename>.cos
- In the affected sessions I find a second type of files: <filename>.NEF.NIKOND800-GENERIC.ICM
2.)
>I do not understand what you mean with 'does not recognise my camera'. Are you trying to import or tether? If import,
>cameras are never recognised. Always use a card reader. Connecting is tethering for CO8.
- I am not trying to import or to shoot tethering
- AFTER import I notice in the basis features that the ICC-profil changed from "Nikon D800E" to "Allgemein". That was what I wanted to say with 'does not recognise my camera'
Regards
Peter0 -
Peter,
Are you using CO 8.2? It is a known bug of the previous release, IIRC.0 -
Hi Paul!
- Now I am using 8.2
- It was a bug in 8.1?
- This could be, affected sessions are sessions I work on with 8.1
- Any workaround? Create a new session with 8.2?
Regards
Peter0 -
I believe it was a 8.1 bug. Create a new session in 8.2 and see what happens then. 0 -
Hi Paul!
- Okay, I will do
- But all my settings will get lost?
Regards
peter0 -
Hi Paul!
- Okay, I will do
- But all my settings will get lost?
Regards
peter0
Post is closed for comments.
Comments
15 comments