dmstraker

Nice! A few notes on the New dialogue. Go to Templates. Cancel out. File/New again. Starts in Templates. Click on Presets. No top menu visible ('My presets' etc). Have to cancel out from within Presets and restart New dialogue. Templates, folder that has a decimal point in it, nothing is shown from the decimal point onwards (I had a folder called 'Affinity Photo 1.8' and it just showed 'Affinity Photo 1' Doesn't seem to be a way to remove template other than in Windows (good that you give option to use Explorer -- this a fix for Windows issue?) Devices are pretty heavily Apple oriented. Surface Pro 2? I've got a Surface Pro 4 and that's old! Could do common display monitor sizes here, eg. 1920x1080, 4K, ... Would be good to be able to edit default setup eg. to kick out things never used or just reorder so my common ones are at the top. Still, My Presets is splendid inclusion!

Not desperately myself, but I do see the need for a professional workflow. Most useful for me is full-screen review and detail zoom (can't beat seeing it up-close). I've used both bog-standard Windows and FastRawViewer with comfort.

It would be great if variables/custom inputs in Procedural Texture were selectable in macros, rather than just Opacity. Thanks!

...and of course the corollary, to include a slider where there is now just a value box. So: Add value boxes to 0-1 and -1 to 1 range variables, and sliders to real numbers and integers. Thanks!!

Well, kind of. I'll be there, on Tuesday 17th. If you'd care to say hello, message me (envelope at top of screen) or reply below and we can figure where/when to catch up. Most of the day I'll be cruising around, probably dribbling a bit, here and there. InAffinity is my YouTube channel on Affinity Photo. Now over 400 videos and counting. For everyone from beginners to advanced. https://www.youtube.com/channel/UCOnLUmyPHr2rayOHVHWsHVw

A Value box would be good to go along with sliders in Procedural Texture. So we can type in the number or use the slider.

Thanks, Cecil, and great persistence!

A part of the puzzle is how overall luminosity is calculated -- seems possible that it is 0.3*Red + 0.59*Green + 0.11*Blue. True? Universally?

Apologies -- forgotten this -- recent confusion came about from another conversation. Will revisit previous postings.

When you hit Reset on Blend Ranges, it only resets the current graph. This includes channels, so for example if you change R, G and B, then hit Reset it will only reset the visible graph, which can be rather confusing. A 'Reset All' button would be nice. Tx

Start with a colour wheel image, add HSL adjustment, then turn saturation half-way down and luminosity half-way up. Now add Blend Ranges and pull down left node of right-hand chart. Colours like yellow are strongly affected but blue and red are hardly affected at all. Why is this happening? My guess is that lightness conversion in Blend Ranges uses luminosity perception, where yellow is seen as a brighter colour and blue a darker colour. However HSL luminosity is value-based and so shows the same amount of greyness. Hence we have a conflict in the treatment of luminosity. I don't know if it is a bug, but it is certainly bugging me as it clogs an effect I was trying to create. At the very least it is a usability defect as it easily causes confusion. Maybe one way to address it is with a checkbox on Blend Ranges that switches between perceptual (as current) and value-based luminosity variation. Thank you for your kind consideration and have a nice day.

Tx. In macro it won't let you at fill colour.

I didn't get an assistant message. Certainly should be there, pretty please? Fingers are crossed for decent competitor to PS actions in v2...

Macro record. Draw shape (picks up current fill). Try to change fill colour. Flashes of hope then frustration of being pulled back to original colour.

Gosh, well done! I did cut and paste but it stayed red. A couple of questions. I'm not sure how DR evaluated in the equation? As Destination Red it would seem to be a result and suggests recursion. roundup(0.5-0.3*SR-0.59*SB-0.11*SB) Should that be 0.59*SG? Merci!

There does seem to be a general performance thing. I've a Chillblast I9 special and Apply Image tranformations aren't much quicker than my I5 Microsoft Surface Pro IV. How well does APh use multiple cores?

Wow! Good work there. Hope your efforts are appreciated. You may know my InAffinity YouTube channel: https://www.youtube.com/channel/UCOnLUmyPHr2rayOHVHWsHVw

Duplicate layer and set top blend mode to Contrast Negate. The result looks suspiciously like a straight invert. I've tried this on 1.7.1 and 1.7.3, same result. See also here (is contrast negate as decribed?)

Nice, though I'm still confused. My Contrast Negate doesn't work like this (in fact, strangely, it looks rather like a straight invert). I've tried it on 1.7.1 and 1.7.3. Which version of Affinity Photo are you using. The macro loads ok but only results in an invert layer. There's a whole bunch of Deletes at the bottom, are you deleting one too many or missing a Merge Image? Just trying to do what you're doing in Filters/Apply Image (click Use Current Layer as Source, then Equations), try this: DR=(roundup(0.5-(0.3*SR+0.59*SG+0.11*SB))*SR)+(roundup((0.3*SR+0.59*SG+0.11*SB)-0.5)*(1-SR)) DG=(roundup(0.5-(0.3*SR+0.59*SG+0.11*SB))*SG)+(roundup((0.3*SR+0.59*SG+0.11*SB)-0.5)*(1-SG)) DB=(roundup(0.5-(0.3*SR+0.59*SG+0.11*SB))*SB)+(roundup((0.3*SR+0.59*SG+0.11*SB)-0.5)*(1-SB)) The 0.5 subtraction throws half below zero which rounds up to zero. Otherwise it rounds up to 1. In other words, the subtraction and roundup are used as a conditional operator. Does this work in the same way?

Wondering if this can be done with a single Apply Image...

Much appreciated, @ch22. Ran the macro -- similar but different results - see attached. Am I using it as expected? contrast_negate_test.afphoto

My experience as a user and a one-time coder is indeed users often know what they want and also 'it's complicated'. The worst development approach is probably to focus first on the loudest users. Better to listen and think before saying yes. It can be good to have a stream of work delivering easy solutions, yet this should be constrained lest all you deliver is a can of little fixes without some bigger rocks to wow the crowds. In other words, listen widely and prioritise based on customer priorities and effort required. Also pursue competitor-busting innovations that customers haven't thought of yet and which will drive stepwise sales. Check out also Kano needs: https://en.wikipedia.org/wiki/Kano_model

A few: Separate colour selection tool based on the system used in HSL Live Apply Image (so I can go back and fix formulae) Better use of multi-core processors, especially in image transformation (I've an I9 and things like Apply Image are still slow) Click the 'x' in Develop Persona to kill image rather than having to use 'Cancel'. This confuses noobs and irritates the forgetful experienced. Scripting to compete with Photoshop Actions Plug-in 3rd party personas ability (or option to show Plugins this way) Smaller .afphoto files (better compression?) HSL as native colour model alternative to RGB, CMYK, etc.

When working with macros, especially on a touchscreen it's really to accidentally set off a macro when you only intended to move the cursor or scroll the macros. This is a real pain, especially when the macros do a whole bunch of processing that takes a while. Not wanting to be a party pooper for those who like one-touch, so would be really nice if you could set a preference to double-check macro execution with an 'are you sure?' dialogue. This would also catch the double-jeopardy of accidentally touching more than one macro so setting off a chain of them! Thanks!

I know it's picky but it would seem to make sense for PC/Mac/iPad to harmonise where it is feasible (understanding the different interfaces, of course). I'm an old coder and quality engineer and sometimes unnecessary little things just get to me. I have PC and iPad versions and here are just a few of the niggles in the shape menu: Sequence is different, top to bottom. Sequence is illogical on iPad (more sensible on PC), eg. with the infrequently used square star near the top. Double star is missing from iPad. PC spelling is Donut but iPad is Doughnut (I'm in the UK, btw). Hopefully not too difficult to sort out in a future release. It would make an old moaner very happy.