AndrewRodney

I'm also driving the SpectraView using a MBP. NEC is profiled with SpectraView. So on the NEC the preview is off or on the MBP display, profiled with i1P? You're running both displays at the same time and showing what on each? IOW, I have the main app running on the NEC and all is fine. The MacBook is the 2nd display (doesn't have menu bar) so no images appear there of course. When I drag the window from NEC to Macbook, so it's the 'main' display and showing both image and all menu items, it previews correctly (it doesn't nor do I expect it to match the NEC!). In i1Profiler, make sure you don't build a V4 profile. I suspect the profile there is the issue. Might trash it and just use the 'default' profile (EDID) and see if the issue goes away. IF SO, it's the ICC profile for your Macbook.

I'm running a dual display system, no issues. The image I've checked, in ProPhoto RGB and tagged as such, previews correctly and matches what I see in other ICC aware app's like Photoshop exactly! http://digitaldog.net/files/PSvsAffinity.jpg Photoshop left, Affinity Photo 1.4.1 right. Not sure what you mean by "the non color managed second display"

All I can say is that AP, Photoshop, Lightroom etc, all match and work with various working spaces as expected. No issues. Could be user error. Could be an issue with the display profile. Does AP engineering know if their product plays nice with ICC V4 display profiles? No reason to build them, but people do, expecting it's better, only to find, it's hosed their previews due to some bug.

What I do is make the screen capture using SnapzPro. That IS in the display color space (one MUST tag that image with the display profile for proper preview). Then just convert to sRGB! I'm using a wide gamut, PA272W so the screen capture is actually closer to Adobe RGB (1998) but that doesn't matter. It has to be tagged with the display profile (it's untagged from SnapzPro and I'd assume virtually every other such utility). Previews correctly with the right embedded ICC profile. Now convert to sRGB, done. I setup a script in a product called Hazel which automatically tags all screen captures with my display profile from one folder. Then copies that to another folder and automatically converts to sRGB. Easy to do with an Automator script.

Toggling blend modes from layers updates a preview on the fly, where as in Photoshop, you have to select the blend mode and wait for an update. I think how Affinity updates as you move from blend mode to blend mode is better.

It's actually Lightness, not luminance FWIW. Luminance (Luminosity) is a measure of the total radiant energy from a body. It has nothing to do with what a human perceives.

Speaking of Lab output values, I wonder which approach is 'correct' and make sense in terms of clipping to -128. Case in point is Green 255 in ProPhoto RGB. It is an 'illegal' imaginary color. In both Photoshop and Affinity Photo, it's shown as an aStar of -128. In Adobe's Lightroom, it's not clipped, it is shown as -187.7 (the decimal values CAN be useful, more later if you so desire). Which is correct and more useful to the end user? I personally prefer how Lightroom provides a value that doesn't clip to the +/- 128 value, it tells us this isn't a color!

I think you're using hue when you mean saturation. https://en.wikipedia.org/wiki/Clipping_(photography): Clipping in some color channels may occur when an image is rendered to a different color space, when the image contains colors that fall outside the target color space. Such colors are referred to as out-of-gamut.

Coming into this late, but playing with the version I purchased today. I'm assuming and I hope that Show Clipped Tones is showing us out of gamut clipping based on the raw data and whatever RGB color space is selected. I say this because when I select sRGB, I see 'clipped tones' but not when I toggle to ProPhoto RGB. This is exactly the same behavior one would see in Adobe Camera Raw in both the histogram (individual clipped color channels meaning saturation clipping) and overlay. Can someone from the company verify that this is indeed the case? It would allow users to select an appropriate encoding color space for raw data conversions. Which begs the question you folks may not wish to answer, can you give us some idea of the processing color space gamut used on raw data? It would appear it's quite large, at least as large as ProPhoto as no saturation clipping is seen. If so, like ACR, I'd probably just always load ProPhoto RGB in the Profile area from now on. No reason to clip colors...

Will these be ICC profiles, DNG profiles, both? TIA. I see support for DNG (THANK YOU!), be nice if I could use DNG profiles I built using the X-rite Passport software.

I see the same missing profiles which begs a question: does this product support DNG camera profiles? I'm opening DNG's and have said profiles built, it would be nice to use them here.

First post, just download trial, very impressive. I see I can open PSD's from Photoshop with their layers (AMAZING)! I can't seem to do the same with layered TIFFs which should be 'easier'? Is this a limitation or am I missing something? I save all my Photoshop generated files with Layers as TIFF instead of PSD. While I have your attention, it sure would be nice if your Convert to Profile command allowed the selection of a rendering intent instead of relying on the preferences. I prefer to toggle RI's and view a soft proof then convert in one operation. Please consider adding this within the Convert Dialog in the future. I'm impressed! Very very nice product. TIA Andrew Rodney