Subclavius

I was thinking earlier of just the absolute basics but of course a fully featured SmartCurves would be fantastic. This is partially referenced in thread 76455: where the ability to save and load presets is requested. That would be so handy for alternative processes ...

Hello, I would also like to see this feature implemented for precisely the reasons that mrenters described in the initial post. In the Blend Options panel of a layer it's possible to put in a large number of points and specify the input/output values for each one. It doesn't seem, on the face of it, to be be very difficult to implement this idea for the curves adjustment as well. Please, someone in the know at Serif, would you consider implementing this or putting on the roadmap? Nigel

Thank you for your help. Nigel

Hi Sean, Thanks for the update. Have uploaded the file to the dropbox Nigel

Hi Sean, Thank you. I look forward to the implementation. I regard this thread as closed. Nigel

I have tested a small .tif file which loads into the develop persona (see pic). It is a scan of a USAF target at low res. The software used to create it is SilverFast Ai Studio 8.8. In fact all scans from this software load into the Develop persona. I have opened them with both Lightroom and other software e.g. GIMP and a proprietary TIFF editor and all open correctly without hint of a problem. I have also attached the .tif file in the hope that someone knowledgeable at Serif (or anyone else out there) can shed some light on the matter. Thank you once again for your help Walt. Nigel USAF 0.7mm 600ppi.tif

Thank you Walt for that nugget. I didn't know that. The smaller file (from a lower res scan) is also a .tif file and this also opens in the Develop persona. For what it's worth I changed the file extension to .tiff but that makes no difference. I imagine you're right that AP thinks it's a RAW file and I guess that there's a size limit for RAW files which is being hit. Nigel

Affinity Photo 1.6.4.104/Windows 10 Am trying to load a large TIFF file from the scanner. It is a 16 bit file with dimensions 12163x15348 (see pic from Windows). However, when loaded (apparently without error) into Affinity Photo the file size is drastically reduced to 1090x1375 (see pic from AP). (1) This file loads correctly into Lightroom (2) A smaller version of the TIFF file (4561x5756), also 16 bit, loads correctly into AP. Any help would be much appreciated. Nigel

Hello, When I resize a document in Affinity Photo (1.6.4.104) the zoom is reset to the default for that document, as expected. However, the zoom level is also reset to default for all other open documents and this is particularly annoying when trying to do comparisons. It also happens when the resize operation is undone. I would like to call this a bug but do any knowledgeable people out there have another view or have I missed something? Nigel

Hello Everyone, Thank you all very much for your help. I'm considering this thread closed. Nigel

Hi owenr, Thank you, that was very helpful. That explains the blue box, otherwise I couldn't understand it! However, there is still the issue of reversing the gradient where a bit appears to get left behind. Nigel

First of all, apologies that the pics are uploaded in the wrong order: the last pic is the 1% opacity, the middle pic is opacity set to 0% and the first pic is the reversed gradient. It's probably me not understanding what's happening, but here goes: When the opacity is at 1% everything looks normal. When I set the opacity to 0% the blue box appears which is smaller than the original canvas - I don't know where that's come from or what it means? Then when the gradient is reversed a small bit at the right hand side (black in this case) is left behind. It *looks* to my inexperienced eye as though when the opacity is set to 0% the canvas size for the gradient layer has somehow changed size. I would be grateful for any enlightenment here, especially as I'm still on the (steep) learning curve. Thanks, Nigel

Hello, I'm not sure what's going on here but I have come across this strange behaviour when the gradient fill opacity is set to 0% at one end. To test I used a simple pixel layer filled with uniform colour and then a second pixel layer above it with a gradient fill. The black colour at one end is set to 100%. The white colour at the other is set to 1% in the first pic, then 0% at which point something strange happens to the layer. When the gradient reverse (3rd pic) is applied the strange behaviour is compounded. I noticed this first on a real picture when I tried to set one end of the gradient to transparent. Any adivce gratefully received! Nigel

I have found the issue - it's not a problem in Affinity Photo. It's an issue with the user - I had at some point set the colour opacity slider to 0% for white (see attached)! For me the slider pattern is a little confusing as it always goes from white (0%) to black (100%) independent of the brush colour, and in monochrome documents there are only black and white! I think that's the reason why I must have originally done it. Sorry for disturbing the equilibrium. Nigel

Hi Chris, Thanks for the reply. I have just done some further testing. What I'm interested in doing is adding a sharpening layer (in this case high pass) selectively by inverting the layer and painting in white. I'm not sure exactly what's going on but here's a summary so far. - starting from a tiff file, adding the live filter layer behaves correctly. I can paint white on black or black on white - in the files where I encountered the problem, the high pass filter is the last layer in a stack and that seems to not to work correctly. Even if I deselect every layer in between the base pixel layer and the high pass filter it still doesn't work So, somewhere in between there appears to be a problem. I am trying to localise the issue but am off for a short break tomorrow so don't have time right now. I will do some more testing next week and update this thread. Nigel