ultrainfra

If I recall when the last update went out it doesn't display that information in the program itself. At least, it didn't for me. Unless it did and I forgot. My apologies

Thanks! If you happen to remember would you post that it has been fixed whenever that happens? If I recall the Affinity updates don't tell you what features are being fixed, added, etc.

I got a new laptop today, an MSI Creator laptop with Intel Core i7-12700H @ 2.70 GHz CPU, 16 GB of DDR4 3.2 GHz RAM, and Nvidia GeForce 3050 Ti dedicated graphics card. The operating system is Windows 11. All updates have been caught up and the computer restarted after updates. After installing Affinity Photo 2 on this computer it seems that it likes to crash when doing various random things. Some examples of things that have made it crash: Zooming in on a photo Opening a menu (for example the Filters drop-down menu) Activating or deactivating one of the tools in raw develop (for example the exposure panel under the basic menu in raw develop)

I just wish the exporting LUTs with HSV adjustments was fixed in V2. The bug was acknowledged in a post I made ages ago, and it was mentioned that it was logged and hopefully would be fixed soon . Never did get fixed, and carried over to V2. Hopefully the LUT exporting eventually gets spruced up. 😁

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 developed a raw file using affinity, with the output profile in the raw developer being set to a linear profile with 32 bit output enabled in the develop manager options. Upon exporting the 32 bit tiff for opening in another program (tried opening in Gimp, Darktable), the file is blank. I tried disabling the compression in the tiff export to see if that helped. It didn't make a difference. I'm running Affinity Photo version 1.10.5.1342 on Windows 10. Does anyone know what the issue could be and how to fix it? I apologize if this is a duplicate topic. The search function on the forums seems to be having some kind of issue at the time of writing.

Hi Dan, I see you have the staff icon under your name. Do you happen to be one of the developers, or have communication with them? I was wondering if you knew if the issue I first posted about here is going to be fixed.

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.

I insalled the latest update to Affinity recently and it appears this issue still persists. Current version is 1.10.5.1342. Adjustments done with the HSV mode enabled for the HSL adjustments panel still export as if the HSV tickbox were unchecked. Hence, applying the LUT to the same image fails to reproduce the same adjustments as HSV. If any devs see this, do you know if fixing this issue is on the to-do list?

I've found posts here about LUTs not working going back to 2017 so it seems that they haven't really been working properly for almost 5 years now. Or at least, have had issues more than once.

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.

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.

In 1.10.4.1196 Exporting LUTs still has some issues. One is it seems that some adjustment layers aren't compatible with exporting LUTs. Im not sure which ones, I only know that when exporting LUTs from an image with multiple adjustment layers the results don't give the same look. And yes, the adjustment layers are all global effects. Second issue is that if an adjustment layer uses the blend curves feature, these are not taken into account when exporting the LUT. So, if I want to increase vibrance and set the blend curve to a linear increase from shadows (0) to highlights (1), the exported LUT will have vibrance increased equally across all tones. Third issue, which I created a topic for recently, is that adustments with the HSL layer do not acknowledge the HSV box being checked when exporting a LUT. So, if I use HSV mode to create a specific look, the exported LUT ignores this entirely and treats all adjustments as HSL. Since HSL and HSV work differently, the resulting LUT is not remotely like what I created. Fourth issue is that sometimes the exported LUT is just devoid of any adjustments after doing an inferred LUT. Given that this topic was created in 2017, nearly 5 years later it seems that the export LUT function is still buggy. I hope these issues are given some attention by the devs in a future update

Anyone else having this issue?

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.

Running Affinity Photo version 1.10.4.1198 on Windows 10.. In the HSL adjustments panel there is a tickbox labeled "HSV" which switches the adjustments to HSV mode. Keeping all the numbers the same, switching to HSV mode will look different since HSV has different properties. However, when you go to export a LUT , the LUT will look like HSL regardless. There are other little bugs with the lut export I've come across but this one is the most problematic for me (and I dont recall the others at the moment) because it means a LUT I try to design using HSV is unable to be saved as a LUT. I attached the LUTs exported using HSL and HSV modes respectively below. To reproduce this: 1. Make the following adjustments with the HSL adjustment layer: Yellow : Luminosity 15% Green: Saturation -40% ; Luminosity 70% Cyan: Hue -10% ; Saturation -35%; Luminosity -20% Blue: Saturation -5%; Luminosity 30% 2. Leave HSV checkbox unticked. Export a LUT and name it HSL. 3. Re open the adjustment layer, and tick the HSV box. Re-export a LUT named HSV. 4. Disable the adjument layer, and create a new LUT adjustment layer. Load the HSV lut. Notice that the results appear as if the HSL mode was used. Load the HSL lut and note that it is no different in appearance. HSL.cube HSV.cube

I am also having a similar experience. I am inferring a LUT from an adjusted image using the LUT adjustment layer. Works fine. The inferred lut does a good job. However, I can't export it. If I export a LUT, the LUT contains no adjustments. It just ends up being an identity LUT. I have tried merging the LUT adjustment layer as well as leaving it as its own layer, but in both cases, the exported LUT is just the identity LUT.

Thanks for sharing the knowledge. It's always good to know more than one way to do things.

Not sure how that happened considering I hadn't copied the URL for the post that was not yet submitted, but I fixed it.

Technically speaking the only raw color changes done are the white balance multipliers, after that, the image is demosaiced and it's a 16 or 32 bit image (depending on the raw developer) held in memory or as a temp file on the hard disk that the adjustments in a raw developer operate on. Camera color profiles are ICC or DNG profiles applied to that demosaiced image. No reason it can't be a LUT file so long as the values in that LUT are suited to the color space the image is in. The advantage of using ICC profiles is that the values are stored as Lab or XYZ (or can also be a simple matrix profile). It's possible to convert an ICC lut to a .cube lut (or whatever lut format) so long as the software you apply it with accepts values below zero and above one. I'm not sure how affinity handles that, might be interesting to go check later. Nevertheless the point is, despite your personal preference, a great many people expect this feature in a raw converter. The forum is full of people who have asked for this to be (re)implemented so it meets the majority of people's minimum expectations for a raw developer , but the Affinity Photo programmers seem to be consistently silent on this. I don't know why, all they really need to do is incorporate lcms2 into their code to do it. Shouldn't be very difficult for a programmer

Are you addressing me or the OP? If me, I'd hardly call it being fussy. Lch is objectively a better color model. Though personally I don't care if it's in the develop persona, since I don't use it anyway given that the raw developer in affinity lacks the ability to use input profiles. So, I typically convert to tiffs with dcraw, maybe sometimes use darktable or rawtherapee, and do anything else in AP 😁

What I mean is replacing HSL with CIE Lch , which can be based either on CIELAB or CIELUV. It would operate just as the HSL panel currently does, but the advantage is perceptual lightness and saturation are more stable when doing hue rotations. To see this, go to this HSL slider online, leave saturation and lightness at a fixed value. Slide the hue. Notice how as the hue changes, the apparent lightness and saturation alters despite the L and S values remaining fixed. Now go here to the CIELch slider and do the same. Notice how much more stable the brightness and saturation are when leaving the values fixed and adjusting only hue When using the CIELch model, it is easy to see that colors with the same lightness value are equally perceptually light, and any colors with the same chroma are equally perceptually saturated. So, when using an Lch color panel adjustments can be made to an image with much smoother gradients. So yes LCh can be just a transformation of the lab color model but it gives an interface with the ability to focus on particular hues etc just like HSL

Hi February 2016! Here it is November 2021, and still cannot put in a custom camera profile

Forget HSL, what Affinity Photo really ought to do is implement the HCLab or HCLuv color models based on CIE Lab or CIE Luv respectively. HSL and HSV are kludgy hacks from times when CIE color spaces were too slow to calculate. HSL and HSV have horrible perceptual uniformity! If any devs who work on the color adjustments module happen to see this post, check out this page for some information