Conrad Hoffman Posted January 29, 2023 Posted January 29, 2023 In a previous thread the issue with the picker not adjusting the tint was said to be fixed in the upcoming 2.0.4. Alas, this does not seem to be the case. Unless I'm doing something wrong. Disappointing, as I use this a lot. Quote
walt.farrell Posted January 29, 2023 Posted January 29, 2023 There were several issues with white Balance, and they fixed the one that was causing a crash, but have not fixed a couple of others yet. There was some confusion as, I think, all were mentioned in the same bug report internally. 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.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Conrad Hoffman Posted January 29, 2023 Author Posted January 29, 2023 Well, I'll admit that crashes have to take priority. Updates tend to be infrequent, so I was hoping for a bit more this time around. Quote
Ron P. Posted January 29, 2023 Posted January 29, 2023 1 hour ago, Conrad Hoffman said: Well, I'll admit that crashes have to take priority. Updates tend to be infrequent, so I was hoping for a bit more this time around. Perhaps so, but they just released 2.0.4 last Friday. I guess they're suppose to release patches everyday? Quote Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
walt.farrell Posted January 29, 2023 Posted January 29, 2023 47 minutes ago, Ron P. said: Perhaps so, but they just released 2.0.4 last Friday. I guess they're suppose to release patches everyday? I think Conrad was saying that since the next update is likely to be awhile from now, they were hoping that 2.0.4 would fix this one. But from what Patrick Connor has mentioned a couple of times, it sounds like a new beta should arrive fairly soon with a bunch of fixes in it. We won't know what they are until we see that beta, of course, but there's hope for this one being included 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.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Conrad Hoffman Posted January 29, 2023 Author Posted January 29, 2023 Yes, that was my point. FWIW, I do have several software packages where minor updates are more frequent. Doing white balance correctly is such a basic thing that I'd expect it to have high priority. After all, Affinity Photo does some much more complicated stuff far better than most. Quote
Conrad Hoffman Posted February 26, 2023 Author Posted February 26, 2023 Joined the beta program and see that the white balance issue still exists. I thought it worked correctly in the develop persona, but that now seems amiss as well. To recap, for any reasonable off-white tone, using the picker, or using the develop white balance tool, the result after white balance is that the RGB values should be exactly equal. Quote
Ron P. Posted March 1, 2023 Posted March 1, 2023 @Conrad Hoffman, update the Beta to 1714. It seems that have the issues with White Balance fixed. Conrad Hoffman 1 Quote Affinity Photo 2.5..; Affinity Designer 2.5..; Affinity Publisher 2.5..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD
Conrad Hoffman Posted March 2, 2023 Author Posted March 2, 2023 I've tried 1714 and see no difference. If I load a Nikon RAW file, the white balance tool there works as expected. If I load a jpg, the operation is no different than the current release. Interestingly, if I go to the develop persona with the jpg file, the white balance tool there, that worked with an actual RAW file before, doesn't work with the jpg. I can't imagine that this is something specific to my machine or setup. Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz 4.01 GHz Asus Z170A MB Nvidia K1200 video card (same results on two similar systems, one Kaby Lake) 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.