dmstraker

Curves x and y point values are much appreciated. Thanks. A query: The y-value origin seems to be top left, so increasing y goes downwards. Not the normal mathematical x and y. I wondered why it is done this way. Is this how PS does it?

Hi folks - well done! Great set of improvements. An odd thing happened: Marquee lines were thicker and Ctrl-0 didn't fully restore full size. Later, it worked just fine (without restarting). Shrug.

Cheers, Chris. Confirmed here. So is that a fix or a workaround? Depends I guess if OpenCL is going to be the standard. But then if you can turn it off for whatever reason, the bug is still there.

Thanks, @smadell and great job! Really good demo examples, too. I had a tinker and came up with a couple of thoughts for the 'EdgesLayer' layer development. I don't know how you used the the Black & White conversion after Detect Edges and Invert, but if you turn down the colours in this, the edges get blacker. I tried replacing the Median Blur with a Bilateral Blur, which seemed a slight improvement. It could also be useful to apply a Posterise at some point to reduce the number of colours.

Curious rider: To double check on another machine, I downloaded the jpg image and there was no problem. But the .afphoto still displayed the problem. Is this something to do with file size or rendering? The problem also appears on v1.9. For reference, the problem image is uploaded (suggesting it's not rendering). Edit: Further experiments show that the problem occurs in 16 bit but not 8 bit.

Excellent increment. Well done, folks! I'm planning on doing an InAffinity video on these and would appreciate a little more detail on these so I can demo them: Added more filter support for masks / adjustments / spare channels (Add Noise, Perlin Noise, etc.) Improved Blend modes to work on “alpha only” layers (masks, adjustments, live filters, etc.) Thanks.

(a) Duplicate source image, Blend Mode: Colour Burn. Expected result. (b) Restart. Add adjustment to source image (eg Curves), Blend Mode: Colour Burn. Unexpected result -- It is partially inverted.. Should it not be as in (a)? Source and .afphoto images attached. colour_burn.afphoto

Hi Hans -- I'm really trying to get this to work and understand the difference here between fill (via fx) and opacity, but I cannot produce a difference. I used your macro, grouped and duplicated the result, then set curves opacity to the same as fill, plus set fill to 100. The result seemed the same as using the fill opacity. I suspect I'm doing something wrong and would appreciate guidance. Thanks!

I'm an inveterate tinkerer and would be grateful in the shorter term with just a basic implementation. There does seems to be all kinds of sharpening methods out there, from stacking to use of assorted blend modes. I've played with quite a few though it's tricky to figure out what works best where. Maybe one day there'll be an AI (yes, I know, over-used) sharpening which understands parts of the image and uses different sharpening methods for different parts. You could already do things like avoid sharpening skies and do selective sharpening on different parts of a face. Where we are now, Custom Blur is an interesting sandpit, and would benefit from the ability to set and use presets, plus being made a live filter.

I just had a question on my InAffinity channel as to whether APh uses deconvolution in sharpening algorithms. Apparently Photoshop uses it for its smart sharpening. Deconvolution? I had to look it up. So I though I'd pass it on to you good folks. Any moves in such a direction? Or maybe even more intelligent stuff? Tx

Splendid to see the good Serif people have been hard at work even during the lockdown. Well done folks!!

... though thinking about it, when hr, hg and hb are results of div0 then using them in any further calculation may also throw a div0 error.

You're right, Alfred. How is that div0? Now I'm also puzzled. Edit: There's also the puzzle of the original post, where odd effects are seen.

Thanks, @Chris B. Pardon delay in responding. Also pardon bug in code! I usually add .001 to divisors to avoid div0 errors but got lulled by ifmo variable mono tweak. I do use Excel to develop code, then concatenate and copy to APh TP. Please send my thanks to whoever found this. Watch out for interesting macros coming out in InAffinity channel. I'm currently having fun exploring possibilities with colour.

Here's a funny thing. Load the attached RGB....jpg file. Procedural Texture. Add variable 0..1 called 'xx'. Put the following code (a snippet from some HSL tinkering) into R, G and B channels. var mx=max(R,G,B);var mn=min(R,G,B);var mr=mx-mn;var ms=mx+mn;var ifmo=roundup(mr-.001);var ll1=ifmo*ms/2;var iflo=roundup(.5-ll1);var ss1=ifmo*(iflo*mr/ms+(1-iflo)*mr/(2-ms+.001));var ifrx=1-roundup(mx-R-.001);var ifgx=1-roundup(mx-G-.001);var ifbx=1-roundup(mx-B-.001);var hr=ifrx*(1-ifgx)*(6*roundup(B-G)+(G-B)/mr);var hg=ifgx*(1-ifbx)*(2+(B-R)/mr);var hb=ifbx*(1-ifrx)*(4+(R-G)/mr);var hh1=ifmo*(hr+hg+hb)/6;xx You should see the value which is in the xx variable (0 to 1, black to white) as the rest are vars. But what I'm getting is the variable acting on the colours within the image, but not the mono. Just to confuse things further, if you remove the last var statement (var hh1=ifmo*(hr+hg+hb)/6;) it works as it should. Don't know if its significant, but I created the image using shapes and no (white) background and exported it to jpg. I re-did this export and same effect. I then tried it with another exported file and had a similar effect. Something to do with exporting of files with no background to jpg? Still odd about the PT code effect. EDIT: Hmm. More tinkering. Don't think it's export. Happening also on fresh pixel image.

Select an area (I used elliptical marquee). Quick Mask. Move Tool. Try to move --> Crash with APh shutdown. Happens reliably. Honky Win10 machine with oodles of memory. Only usual Camtasia and Logitec virtual camera app running. take care...

OK, I've got it. No assistant stuff. Useful for such as invert fill layer and paint white to put it back. For example blue fill layer, blend colour burn, invert, paint back 10% opacity over sky to extent blue through clouds. Thanks for the patience and insight!

Might this be something for the Assistant to do? It does rasterise other layers.

Inverting a fill layer seems to make it transparent. I thought the fill colour would invert.

Take an image. Apply Blend Ranges and adjust transparency. Add live Unsharp Mask or High Pass sharpening. The moment the radius leaves zero, all transparency is lost on either and everything gets sharpened. I also tried this on an image with Alpha adjusted via a Procedural Texture algorithm and the same effect happened. What gives?

Helpful. Thanks. I've yet to get properly into oscillators, etc. Mostly doing RGB algebra of late. It would be great if there was more definitive help available on the PT functions.

Holding down space bar invokes view tool with hand cursor icon so you can drag around. You know this. However, when you release the spacebar the cursor icon remains as a hand and does not revert to the previous function, even though clicking invokes the function. This can lead to confusion and unintentional error. Not a biggie, but one for those spare moments

Yes of course. It simply was that I found I could draw the blue node selection area but with nothing to select. At the time I didn't know what it was for so was rather baffled. It's a general usability principle to not allow users to do things that have no immediate function and can end up with strange effects (like the blank Curves panel). So when there are no nodes, do not allow the node selection to take place. It's not a biggie. I was a programmer, then in software QA, so little things bug me. I report what I find, but then it's up to you to decide what to do about it.

Ok - figured how having noded curve that Alt-click/sweep selects nodes. Can't replicate tips with polygon selection with just pixel layer. Hmm. However Alt-clicking around on a simple pixel layer still creates blue selection area (releasing Alt does not escape this), whence Ctrl-M brings up curves layer but without content. Not a biggie, but it would seem that confusing non-functional scenarios should be suppressed, perhaps throwing up an error message rather than ploughing ahead into strangeness. And yes, I'm on a PC. The dark side, and all that.

Select node tool. Tips at bottom of page include Alt-click for polygon selection. Tips then change, now suggesting actions for lasso selection. Playing with this it seems to be a part-complete feature. You can draw, but Return or closing path makes selection disappear. Hitting Ctrl-M when selection visible leads to a curves panel without the curve.