Jump to content
You must now use your email address to sign in [click for more info] ×


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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
  2. 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.
  3. 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)
  4. 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. 😁
  5. 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.
  6. 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 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.
  7. 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.
  8. 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.
  9. I insalled the latest update to Affinity recently and it appears this issue still persists. Current version is 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?
  10. 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.
  11. 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.
  12. 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.
  13. In 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
  14. 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.
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.