Free third-party styles based on .icc files?
I'm having trouble with Capture One becoming unresponsive the first time I hover over a style from RNI, which include both .costyle and .icc files – though this only happens when using larger catalogues. In order to check if this is a general issue with styles that include .icc files, I've been looking for other such styles but haven't been able to find any. Does anyone know of any free styles – e.g. trial or demo sets – based on .icc files? The quality of the styles is unimportant as it's just for testing.
-
Which version of Capture One do you see this issue with, 16.2 or 16.3? I'm still on 16.2 and use small sessions, so I might not experience the same issue. Both RNI 4 & 5 work for me in my configuration.
You could download some free styles from https://luts.iwltbap.com/. Scroll all the way down to the section called "Free stuff" where you can download 6 LUTS/Styles. Once you pick one, you again have to scroll down to the section "Download", not "Download full pack of unique LUTs".
1 -
Thanks. The issue appears to be independent of version – I have it with 16.3 and have had it with the previous versions too. Though only with larger catalogues, with small catalogues I see no unresponsiveness.
I'll see how it works with the styles you refer to.
1 -
Apparently using the .icc files on their own doesn't work, only the .costyle files work in Capture One. And Capture One does not become unresponsive with the styles I've downloaded from luts.iwltbap.com.
I just tried duplicating a folder of RNI styles and deleting the .icc files, and the .costyle files alone still cause Capture One to become unresponsive. So the issue appears to be something other than .icc files.
0 -
Right, Capture One only reads the .costyle file which internally refers to the .icc file. At least, it does in RNI5. RNI4 doesn't use .icc files.
Is it possibly a pathing issue? Have you stored the .icc file at the same level as the .costyle file? You can open the .costyle file in a regular text editor to see where it looks for the .icc file. It's possible that if the .icc file is not in the expected location, Capture One might search other system folders where .icc files are located, like in the monitor profiles. It could potentially cause a lag but I don't see how it would be tied to the catalog size. I would expect that search to only happen on a per-image basis once you roll over a style.
1 -
Thanks for the explanation. I wasn't aware that that's how it worked – that .costyle files refers to .icc files.
I also realized that step two – installing the .icc files – is missing from the online description of how to manually install the styles. I just found it in the included pdf.
After having installed the styles correctly, I see that Capture One also becomes unresponsive the first time I hover over these styles. So it's not an issue with RNI styles but with styles that rely on .icc files.
0 -
Hmm, that's odd. I can't imagine how this would be connected to the size of the catalog. Maybe support can shed some light on this.
0 -
I've contacted support but haven't heard from them yet.
I'm not the only user who has had this issue (see this post which is about RNI styles too). In my experience, Capture One generally has issues with larger catalogues. When I use small catalogues, I see no unresponsiveness, but with larger catalogues all sorts of things cause Capture One to become unresponsive, so I assume it's doing something in the background that takes longer with more images.
0 -
Ah yes, Capture One was never made for catalogs, it was always meant for Sessions. Catalogs were an afterthought and to this day, they haven't improved on that. There are way too many issues associated with catalogs larger than 10K, so I only use Sessions. Once Peakto can handle C1P previews, this will be a replacement for having a large catalog in C1P.
0 -
I use Peakto already because of Capture One's poor performance with larger catalogues. But I still add and edit metadata in Capture One as two-way synchronization between Peakto and Capture One would only make Capture One even more sluggish. This is far from ideal, though, as you have to maintain several keyword libraries, smart albums, etc.
0 -
I see, for me, Peakto isn't yet viable without the full-size previews but I hope it's coming. As for metadata, I handle all GPS tagging in HoudahGeo and keywording in GraphicConverter. I know it's odd to use GC for that but C1P tends to crash when editing keywords, so yeah. It would be nice not to have to use various tools but that just seems to be the only stable option.
0 -
At least Peakto is useful for finding images (I mostly avoid searching in Capture One as it always becomes unresponsive for quite a while). For ingesting and adding GPS metadata I use Photo Mechanic Plus. I tried to use Photo Mechanic for adding keywords, but and it handles keywords differently and made a mess of the keywording I use in Capture One, so I quickly stopped.
0 -
Right, searching is another issue in Capture One. I have tried Photo Mechanic in the past but it had some issues with Fuji files, so I had to abandon that approach.
0 -
I bought the Plus version of Photo Mechanic as I thought I would be able to use it for cataloging, but as it doesn't show variants (which, of course, I knew when I got it) this didn't really work very well. Another thing is that synchronizing/reading metadata in extremely slow. So all in all I don't find very useful except for ingesting, renaming files and editing GPS metadata.
0
Post is closed for comments.
Comments
13 comments