Mariusz_F Posted February 11, 2023 Posted February 11, 2023 macOS Ventura v.13.2 Hardware acceleration ON Problem description: After exporting LUT and then importing it back o the image, the image outlook is not the same, eg. very low contrast. Size of the LUT do not influence the result. The same problem appear in Affinity Photo V1. Quote
walt.farrell Posted February 11, 2023 Posted February 11, 2023 15 minutes ago, Mariusz_F said: After exporting LUT and then importing it back o the image Can you explain your workflow a but more, please? How did you get a LUT to export? If it was already in the image, then wouldn't adding it a second time have to change the results? Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4
Mariusz_F Posted February 11, 2023 Author Posted February 11, 2023 Workflow is typical I think: 1. I make adjustment to the image eg. white balance, curves, etc. 2. I export the LUT 3. I open the same original image, with no adjustments 4. I import LUT what was exported in step 2. And the final result is like on the images attached, that the new image has a different look, no contrast, etc. walt.farrell 1 Quote
walt.farrell Posted February 11, 2023 Posted February 11, 2023 Thanks. The two images you've included look almost identical to me. Perhaps you could provide the original .afphoto file including the adjustment layers, the .cube file you exported (and a screenshot of that export dialog), and the new .afphoto with the LUT applied? Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4
Dan C Posted February 13, 2023 Posted February 13, 2023 Hi @Mariusz_F, Thanks for your report! I can confirm this issue is logged with our developers as a bug, I will be sure to 'bump' this with our team now to bring it to their attention once again. I hope this helps walt.farrell and Mariusz_F 2 Quote
Dan C Posted February 21, 2023 Posted February 21, 2023 Hi @RalphMara, Welcome to the Affinity Forums Unfortunately this issue is still logged with our development team to be resolved at this time - I will be sure to 'bump' this with your post for you now. I hope this clears things up! Quote
Thomasdelange Posted March 12, 2023 Posted March 12, 2023 (edited) Hi @Dan CI have the same issue, which is unfortunate since I was planning on using these LUTs for batch processing my vacation images. It seems that exporting Luts works better when the adjustments are not embedded in a group in the layers panel. Edited March 12, 2023 by Thomasdelange Quote
Dan C Posted March 13, 2023 Posted March 13, 2023 Thanks for letting me know @Thomasdelange and I'm certainly sorry to hear this - I will be sure to 'bump' this with our team to bring it to their attention once more, and include the information above. I hope this helps! Quote
Staff Affinity Info Bot Posted May 23, 2023 Staff Posted May 23, 2023 The issue "LUT does not apply the same effect after it has been exported" (REF: AFP-4767) has been fixed by the developers in build "2.1.0.1806". This fix is in the current customer release. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us Quote
Maxdanger Posted June 23, 2023 Posted June 23, 2023 @Serif Info Bot I've encountered this bug when editing in a 32 bit workflow. Confirm it has been fixed for 16 bit but it still exists for 32 bit. Here's a video I recorded LUT bug AFP-4767.mov Using latest version Affinity Photo v2.1.1.1847 Quote 2024 14 inch MacBook Pro M4 Max, 128 GB RAM 2024 M4 iPad Pro 11 inch Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 | Current Beta versions.
Dan C Posted June 26, 2023 Posted June 26, 2023 Many thanks for updating us here @Maxdanger, I can confirm that I'm seeing the same behaviour and I have therefore reopened the issue with the development team. I hope this helps Quote
Maxdanger Posted June 26, 2023 Posted June 26, 2023 2 minutes ago, Dan C said: Many thanks for updating us here @Maxdanger, I can confirm that I'm seeing the same behaviour and I have therefore reopened the issue with the development team. I hope this helps Awesome - cheers for the quick reply around Dan Quote 2024 14 inch MacBook Pro M4 Max, 128 GB RAM 2024 M4 iPad Pro 11 inch Affinity Designer 2.6.3 | Affinity Photo 2.6.3 | Affinity Publisher 2.6.3 | Current Beta versions.
lucy dawlish Posted April 2, 2024 Posted April 2, 2024 (edited) Spent a while colour grading and saved the grade as a lut, but all the lut did when I imported it back in was increase the luminosity and saturate the reds, it subtle. As you can see from the 3 images the grade is not subtle at all lol. Before grading After grading not subtle at all with the Teal and orange / pink with just the adjustment layers turned on. This is with the adjustment layers turned off and just the Lut turned on. So just to make sure it was not me I opened up another photo with plenty of blue similar sky [actually photo taken on the same day] and red to check the LUT obviously the blee should have gone teal in colour and the orange-reds more pink. but as you can see it has just not done the job at all.. Before applying the Lut After applying the LUT, reds and oranges have become a little more saturated, and obviusly the sky and water have not turned teal in colour. I am using the Mac M1 Sonama 14.3.1 affinity photo2 build 2.4.1 Edited April 2, 2024 by lucy dawlish added a photo Quote
Dan C Posted April 2, 2024 Posted April 2, 2024 Welcome to the Forums @lucy dawlish! Sorry to see you're having trouble - as above our team are aware of issues with exported LUTs retaining the same colour adjustments, as present in the file before exporting. This is logged with our development team and I'll be sure to 'bump' this with them now, including the information provided in your screenshots above. I hope this helps Quote
lucy dawlish Posted April 2, 2024 Posted April 2, 2024 @Dan C thanks for your reply, I could see that the issue was there in June 2023 but as it was April 2024 thought it OK to just bump this to the team. Asd I could not see anywhere the the issue had been resolved or not. Anyways thank you again for your quick reply I hope there is a resolution to this issue soon as it would help with workflow immensely for me. Kind regards LucyD Dan C 1 Quote
AP- Posted November 8, 2024 Posted November 8, 2024 This bug is still present in 2.5.5 on Sequoia 15.0.1. How to reproduce: 1. Open 8-bit JPEG (or develop a 16-bit image from RAW). 2. HSL adjustment layer, curve adjustment layer and selective colour adjustment layer. 3. Export LUT. 4. Import the saved LUT and click the panel button or create a LUT layer and load the file. It does not apply. An interesting behaviour noted: It works fine if you add a white balance adjustment. The fix for me is to add a 1% white balance adjustment with 1% change in both sliders. Another interesting fact: Delete all the adjustment layers. Repeat steps 1-4 above. The exported LUT is the last one saved with a white balance adjustment layer rather than the current one you try to save. Quote
walt.farrell Posted November 8, 2024 Posted November 8, 2024 8 minutes ago, AP- said: This bug is still present in 2.5.5 on Sequoia 15.0.1. The issue is still open (unfixed), which we can tell because the Affinity Info Bot has not posted to say that it has been fixed. Your other points are interesting; thanks for noticing and mentioning them. That may provide additional info for the Serif team to help resolve this. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4
AP- Posted November 9, 2024 Posted November 9, 2024 Yieesss. I do have a question though. Does the Export LUT only export the bare adjustment translations or does it include say, a live mask applied to the adjustment layer? I'm thinking a use case here of targeting specific luminosity ranges with the luminosity mask. Quote
walt.farrell Posted November 9, 2024 Posted November 9, 2024 3 hours ago, AP- said: Does the Export LUT only export the bare adjustment translations or does it include say, a live mask applied to the adjustment layer? I'm thinking a use case here of targeting specific luminosity ranges with the luminosity mask. I can't think of any way that a LUT could incorporate a mask. It's just a table of input vs output numbers for colors, as I understand them. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.4
AP- Posted November 9, 2024 Posted November 9, 2024 That's what I initially thought, but upon consideration, the luminosity mask is just another way to manipulate the same data, hence the question. It's a bit like which part of the curve one would be editing, so should in theory be possible to map. Also, the fact that the .look extension specifies LUT only implies the other two formats are able to export other things. I was sort of thinking, what, though? Quote
X-Raym Posted March 1 Posted March 1 Hi, Affinity 2.6.0, Win 10x64 I still confirm that exported conversion table (LUT, Cube etc), aren't reimported back properly. Here is Demo with .cube export https://cloud.extremraym.com/sharex/Photo_o6rIHrbyV8.mp4 Same problem with .look export (in this case, it just do nothing) I would love to see this fixed. I need to apply the same profile on 35 document (some kind of color correction for scanners) and having the correction stored as external file (a LUT for eg) is the only way to have the correction dynamically applied over all the document (handy if it need to be adjusted). Can you take a look ? @AP- I also noticed luminosity max produced black and white output in the Export table preview window. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.