ultrainfra

I think at best V2 should have been a free update to V1. The introduced features are mostly things that should have been there to begin with. 
I'm disappointed that input ICC profiles are STILL unsupported in the raw developer. It's a basic feature of pretty much every third party raw development program I know of, and if a raw developer doesn't support ICC it will usually support DCP (DNG Color profiles, ie, as used in Lightroom, Luminar). I also really would have liked to see an easy method of straightening a photo by using a measure tool. GIMP has such a feature. You can use the measure tool to form a line segment on an edge, and have it adjust the image so that it becomes even. 

I too have found it to easily crash. Have not noticed a pattern yet as to what triggers it. Sometimes it's something as simple as zooming in or out. Sometimes it's calling a plugin. Sometimes it's moving a slider on one of the filters. 

So, so far it's basically the same as Affinity Photo V1 with a couple new features that should have been part of a free update given how relatively minor they are, a less appealing set of buttons (though this is just my aesthetic opinion), and lacking things that should be there. Not sure if to get a refund or just keep the new version in case it is improved. However considering exporting LUTs with HSV adjustments (by checking the HSV box on the HSL filter) was never fixed, my hopes aren't incredibly high. I say all this in the spirit of providing feedback to improve the product. Obviously if I bought V2 there are more things that I like than dislike and always like to support eating into Adobe's profits.
 

I think at best V2 should have been a free update to V1. The introduced features are mostly things that should have been there to begin with. 
I'm disappointed that input ICC profiles are STILL unsupported in the raw developer. It's a basic feature of pretty much every third party raw development program I know of, and if a raw developer doesn't support ICC it will usually support DCP (DNG Color profiles, ie, as used in Lightroom, Luminar). I also really would have liked to see an easy method of straightening a photo by using a measure tool. GIMP has such a feature. You can use the measure tool to form a line segment on an edge, and have it adjust the image so that it becomes even. 

I too have found it to easily crash. Have not noticed a pattern yet as to what triggers it. Sometimes it's something as simple as zooming in or out. Sometimes it's calling a plugin. Sometimes it's moving a slider on one of the filters. 

So, so far it's basically the same as Affinity Photo V1 with a couple new features that should have been part of a free update given how relatively minor they are, a less appealing set of buttons (though this is just my aesthetic opinion), and lacking things that should be there. Not sure if to get a refund or just keep the new version in case it is improved. However considering exporting LUTs with HSV adjustments (by checking the HSV box on the HSL filter) was never fixed, my hopes aren't incredibly high. I say all this in the spirit of providing feedback to improve the product. Obviously if I bought V2 there are more things that I like than dislike and always like to support eating into Adobe's profits.
 

That's odd. I haven't noticed anything like that. What dimensions are your luts? 

If you use the small 17 * 17 * 17 cube size that's the default, it might take a longer time because there's more interpolation to be done between the points defined by the LUT. Alternatively, if you are using a very large size, that would mean the program applying the LUT has a larger file to load into memory. Good LUT sizes are 33*33*33 or 64*64*64. Most LUTs you'd download from the web are one of these two sizes. 

It's also possible that the exported LUT contains out of gamut values (less than zero or more than one). I can't recall at the moment if these values are clipped when exporting LUTs. Sometimes that "upsets" programs that apply LUTs.

Otherwise, I'm not really sure why that would happen to you. 

 

Interesting, the HSL adjustments are captured for me. It's just that the HSV tickbox is ignored when exporting the lut. 

If you load the luts I attached into grossgrade you can see that they are captured, and that the HSV adjustments are identical. I'll screenshot the cube representation of the luts from grossgrade, in case you don't have that installed. 

The lightness affecting saturation is part of how HSL works, so it's working properly. It's just a crappy model of color. The polar transformations of CIELUV and CIELAB, known as HCL or LCH (usually with ab or uv written afterwards to indicate which CIE color model is used as the basis) are far better at separating lightness and chroma (not saturation). HSV and HSL don't even separate luminosity and saturation from the hue well, and the same lightness/value for different hues corresponds to different lightness when measured with a device independent color space like CIELAB. HCLuv/ab is also independent of the particular working color space, being based on such device independent color models.

 

https://bottosson.github.io/posts/oklab/
https://bottosson.github.io/posts/colorpicker/
You are talking about what I am familiar. I am an expert user.

The lightness affecting saturation is part of how HSL works, so it's working properly. It's just a crappy model of color. The polar transformations of CIELUV and CIELAB, known as HCL or LCH (usually with ab or uv written afterwards to indicate which CIE color model is used as the basis) are far better at separating lightness and chroma (not saturation). HSV and HSL don't even separate luminosity and saturation from the hue well, and the same lightness/value for different hues corresponds to different lightness when measured with a device independent color space like CIELAB. HCLuv/ab is also independent of the particular working color space, being based on such device independent color models.

 

HSL and HSV are different, and should behave differently as a result. 

From Wikipedia...

So, with HSL the saturation is supposed to decrease with an increase in luminosity. It also decreases with a decrease in luminosity. 

In HSV increasing the value doesn't affect the saturation as much. If Adobe Photoshop is calling something HSL and it behaves like HSV, then they are utterly incorrect in their labeling and need to learn some basic terminology before peddling their overpriced subscription software. 😒

Either way, I wish Affinity implemented the superior HCL color models based on either CIELAB or CIELUV. They are more perceptually uniform and do a better job of decomposing colors into three orthogonal components. 

 

Serif
 
Yeah, there wasn't any other recently installed software. That's why I thought perhaps the Affinity installer had been infected. I figured it was very improbable for that to be the case, but there were no other recent downloads, installations, or visits to websites outside the usual , so I thought I should bring it up here just in case a hacker had gotten to your site.

I was able to get it removed, though, so all is well.