baoyu

font list bug.mp4

I don't recommand using the HDR function of either one of the display models when dealing with serious composition works. I just don't trust the color accuracy of them under HDR mode. Could you try using ACM with LDR Display P3?

IMO, the HDR capability of LG34WK950U is better to have than none.

Yeah, I knew that and I had tried that with no luck. While with photoshop, it works. BTW, we share the same monitor model except that I calibrated it using xrite display pro @NotMyFault

ACM is already in newest Windows 11. And I find that affinity 2.5.6 still doesn't support it. @DWright See the comparison below. Sorry I have to upload a photo as I'm not aware of which screenshot tool that supports wide gamut. Left: affinity photo 2.5.6; Mid: Photoshop; Right: Photo viewer of Windows. Sample image used:

Can't agree any more! We want a layer system that de-couples from the artboard in designer.

I‘d consider the Scripting system be the BIG CHANGE 😂

Let's hope serif is working on the next major release and the scripting feature will come with it?

Man, I will not stop you from using curve to do so. But I highly suggest you to use the magic wand tool with some threshold to select the exact color and fill whatever color you like. It is the exact tool built for the exact purpose. While the curve tool is designed to perform gradual operation on a tonal range around the desired tone.

8 bit is OK for the camera raw filter. ⬆️ READ THIS AGAIN ⬇️

So how do you accomplish that in PS using curve? To me, I can't find an eaiser way to do the work, no matter what software. I'd appreciate that you could show the method.

I just said that I've been using PS for 15 years. To be honest, in photoshop in terms of white balance, I always do it in ACR which operates in 16bit before the image being brought in PS. If I have to tweak white balance in PS, I just just the camera raw filter instead of using curve. As I said, it's not precise enough in 8 bit as well as it's not a good practice to combine mixed operation in one adjustment layer. Regarding to the 3 eyedroppers in curves of PS, I am sure it's extremely useful when dealing with a badly damaged image. It's rare that we have to such damaged assets. On the other hand, those 3 eyedroppers seams to sample only the one pixel exactly you pick other than averaging neighbouring pixels (I'm not sure about this, but PS have no option changing the sampling radius). So it's hard to deal with noisy/high-frequency-detailed image. Basiclly the function is equally labour-intensive and effective as do it by hand. Well, again the "x,y" is equal to "input/output" in photoshop... Well to accomplish this, manual calculation and type in node values in each channel. 30/69=0.4347, 50/80=0.625, 170/200=0.85, in each chanel, make the top right nodes' x/y or input/output to (1, 0.4347), (1, 0.625), (1, 0.85). So what's the convient way to do this in PS? I guess it's the same as AP.

I've been using PS for work for about 15 years. Not all of your points I'm against. Actually for almost half of your opinions, I feel the same. For this eye dropper function of curve/level adjustment, I am with you, it's a pity for AP not having this. In AP's white balance tool doesn't require you to pick the exact grey, you just need to pick the area where you think it should be neutral. Just consider them as input/output, they're just the same thing with different name. 0.000-1.000 with 3 digits that's 10001 stops of precision, while 0-255 without decimals that's only 256 stops. And in CG industry, people use Nuke/Fusion/Natron/Autodesk Flame etc. They almost always use 0-1 with even more digits than AP. It's not true that RGB uses 0-255. You can just what ever precision you want with RGB. It's 8bit sRGB that uses 0-255, because 2^8=256. And if you want, 0-255 can also be displayed as 0-1 with increment of 0.0039... It's OK to use 0-255, but with 0.000-1.000, you have more precision. So why not?

I am for some of your points while against some. One of the against is For white balance there's a dedicated white balance adjustment layer. It's better to seperate two disdinguish ajustments into their own layers. They possibly interfere with each other when you want tweak one of them. Here's another one "0 to 1" follows CG industry convention. Photoshop is growned up in the earl days for photography, print and graphic and used to work in 8bit precision. AP is born to support 8bit, 16bit int/float point and 32bit float point precision. It's common in the CG industry that "0 to 1" means standard dynamic range and people get more intuition to predict the "dark tone, mid tone and highlight tone" with "0 to 1" other than "0 to 255". Let alone the majority tools of photoshop can't work with 32bit float workflow. AP still sucks in a lot of aspects but not every when it's different from PS should be its wrong.

Thanks for the insight, Hangman! I'd prefer manual control over those settings though.

Can we have customizations of QR Code symbol version (1 - 40) and Error correction level [choices: "L", "M", "Q", "H"]

and in case you staff missed my suggestion, shamelessly pinnnnnnn @Patrick Connor BTW, merry Xmas!

I have an idea that solves all those similiar feature requests like "blend tool", but it will be hard to implement: make a node based tool just like "geometry nodes in blender". It allows users to pack, save and share self-made presets which can be seen as "features" or "plugins". What's more, affinity official could pack some presets along with the app itself. Also if it's possible, we could have a market for users to share/sell their own presets.

Hi @DWright I just confirmed that this is still not fixed V2 series version v2.04.

You don't get the point. If Astute come and make their subscribtion-based plugins, you have the right to not use it. The point is that Affinity haven't implemented the SDK for third party plugin development. If they do, there will be free/affordable plugins.

@rayRyo I doubt Serif would do such stupid thing. It is literally smashing their brand.

That is disappointing!

I can confirm this BUG hasn't been fixed in V2.

@SmilingJ@Intuos5 You may read my use case

It is an independent company what is not tied to Adobe. And Astute in the past just talked in this forum willing to develop plugins for Affinity suites.