Grant Robertson

Thanks for providing this link in this thread. I have downloaded your book. Though, I haven't had time to read it yet. It looks pretty nice so far.

I would like to have a separate conversation with you, in a separate thread about this. I am intent on using a separate RAW processor as well (probably RawTherapee). I am currently researching what would be the best file format for passing the image from RawTherapee to Affinity Photo. But I hadn't even considered the possibility of being able to round-trip that data. I was just cruising my fingers, hoping to find a totally successful one-way transfer.

Does this double the size of the file? Or do both layers simply reference the original raw data from the Develop persona?

Although I have now installed the .msi version of all the Affinity software, this will come in handy for many other things. Thanks.

It's not a bug. It's a Feature! 😭🤦

It sounds as if Serif has some really long, long range radar. We're into version 2.1 now, and we're still waiting.

That's part of the problem. "Profile" can mean any collection of one or more settings for literally anything. And software developers and marketers abuse the hell out of it. My office chair is set to the "Chair Profile" named "Grant's Profile," because that's the collection of adjustments that I like best.

Oh, I've given EXTENSIVE list of reasons why providing a .PDF file is far superior to an online help file. Not least of which is that one can never be sure that one has seen every page of the documentation in a web-based help file. There will always be some page that you can only get to if you happen to find that one link buried in a paragraph that you thought you didn't need to read. I don't like Dungeons and Dragons. I don't want to have to play it to find all of the pages of the documentation. My suspicion is that companies don't like .PDF documentation because A) They want to be able to change the documentation without anyone noticing, and B) They don't want to pay for the additional utility that would generate the .PDF file from the base-source of the documentation.

Well, Walt was just guessing. @lepr was the one who truly answered my question with facts. @lepr also made it clear that it was the Develop Persona that could not refused to use any user supplied profiles. As a TIFF file is not a RAW file, Affinity Photo will edit that file in the Edit Persona and use whatever profile is embedded within that file. So, while Walt and others were claiming that "Affinity Photo" would ignore any embedded profiles, they were not being specific. It is only the Develop Persona that ignores those profiles. The Edit Persona does not. Please re-read my original post. I have added a conclusion that summarizes everything.

You are WAY more hard core that I prefer to be. Let me guess, you toss in a little awk and grep as well? 😜

Yeah. It seems odd (yet not surprising) that a program as expensive and popular as Capture One would have bugs/inconsistencies like that.

OK, be that way! 😁 No, actually, thanks for the warning. This is very disappointing. So disappointing that I will be forced to attempt to prove you wrong. Wish me luck. Although, I do suspect that you are correct. In this clip from the video posted by @v_kyr, you can see how the "presenter" uses Capture One to automatically generate a color corrected TIFF file from a color corrected RAW file and automatically passes that to Affinity Photo for what he calls "pixel-based editing." (Note: This would be after the RAW files had had the Calibrite-generated ICC profile applied to them in Capture One.) He is able to use the full power of Affinity Photo to edit the image. He just skips over Affinity Photo's "Develop Persona" altogether. I am sure that I can figure out some workflow using IMatch (my favorite DAM utility, from photools.com), ImageMagick, as suggested by @v_kyr, and RAWTherapee (a free and open source RAW file processor) to get everything I need done. It will just require more "hacking" and script writing than I had hoped to get there. But, I'm a former network manager with a degree in computer science, so I'm sure I can figure it all out. When I do, I'll make a post here for everyone else.

This is what I have concluded. I'm now going to just use ImageMagick from within a script in IMatch to automatically generate the necessary uncorrected TIFF files from within IMatch. I'll have to check and see if there is a way for me to now mark this discussion as closed.

It seems that ImageMagick is on par with ExifTool in regards to its power for manipulating image files (just with a different focus). My favorite DAM utility (Photools IMatch) has scripting features that would allow me to set up easy to use scripts to use ImageMagick to do everything I am asking for. I could just select all the images with the Calibrite ColorChecker in it then, in a few clicks, have all the TIFF files automatically generated. I had just been hoping that it was doable from within Affinity Photo. You know, just because..... In the end, using ImageMagick with IMatch, will actually be faster and easier (after it is all set up. Thank you.

This is a question that you should be asking the people at Calibrite. It is my current impression (after watching this bit of a video suggested above) that you set the ICC profile to "No Color Correction" in the first step of exporting the TIFF from Capture One so that there will be no color conversion when the TIFF is exported. Then you embed that same "No Color Correction" profile into the TIFF file so that the Calibrite software knows for sure that no color correction was applied, or to make sure that no color correction gets accidentally applied anywhere between exporting the TIFF from Capture One and importing it into the Calibrite software. In my original post, I had not noticed that bit of that video and the instructions from Calibrite were not clear on the reason for embedding that "No Color Profile" profile. I will correct my original post right after I submit this reply.