aaturner

I am using AP 1.9.0.820 Beta on Windows 10 Pro Version 10.0.19042 Build 19042. I have GPU acceleration enabled although the problem also arises without acceleration enabled. I have a Geforce GTX 1660 graphics card with 6Gb and an Asus Z97-AR motherboard with 16Gb ram. System is on a 1Tb SSD (Samsung). Problem arises when I develop an image in 16 bit with a tone curve applied, or 32 bit with no tone curve applied, and a camera and lens profile also applied. From there I enter the tone mapping persona. Having made some adjustments I click on the Apply button at which point AP simply shuts down - no warning, no error message. Exact same steps in AP 1.8 work just fine. Choice of image seems immaterial, but fyg the ones I have tried are 36Mb .nef images from a Nikon D810. Any guidance you can offer will be welcome. Many thanks. Andrew Turner

Thanks for your response, Lee D. I'm attaching the errant file that (at least on my PC) does not open on APUB 1.8 - it was originally created on 1.7. Any guidance as to what might be wrong will be very welcome. Thanks Cameracraft.afpub

I'm trying to open a document prepared in Affinity Publisher 1.7 with Publisher 1.8. The app seems to start correctly but after a few seconds it just shuts down. Publisher 1.8 does start correctly if starting a document from scratch. Could someone please advise me what I might be doing wrong, or must I resign myself to a) reinstalling 1.7 or b) losing the document? Many thanks Andrew Turner

Yes, that works. Thank you, Aammppaa for your clarification. Truth be told I had not even thought of clicking on the thumbnail; I was busily clicking on the main image much as I would when using a selection tool! Not particularly intuitive; however, that's another splinter avoided as I slide down the banisters of life. Thanks again.

Good evening all; I am on a Windows 10 platform with the latest upgrades installed. I have installed the latest release version of Affinity Photo 1.7.0.367 (full release, not a Beta version). I am trying to create luminosity masks using CTRL+SHIFT+LEFT CLICK and/or CTRL+ALT+LEFT CLICK to select luminosity values in an image. No selection is made using the mentioned keystrokes. I have tried on a photo in both 8 bit and 16 bit format as well as on a blank rectangle with a random colour applied; none work.They used to work in earlier versions of AP. Others report that the keystrokes work for them, but if I recall correctly they are on a Mac system. Is this seemingly anomalous behaviour a bug or am I doing something wrong? Many thanks. Andrew Turner.

Yup, tried that with no success, so I shall follow your good advice and report the behaviour (or lack of) as a bug.

Thanks FDK for your very swift response. Unfortunately no combination of Ctrl+Shift or Ctrl+Alt or even Ctrl+Shift+Alt while clicking works for me for selecting luminosity pixels above (or below) 50%. However, if I am using the selection brush I can select multiple points via Ctrl+Shift.

Hi all, To re-open this topic,neither of the alternatives mentioned work on my version of 1.7.0.367. Have tried with both 16 bit and 8 bit images; same (lack of) result. Is there something I am missing? (Windows 10 64 bit) Thanks.

Following earlier comment above and after further testing, it seems that the luminance anomaly arises when processing 32 bit images. When in 16 bit mode processing appears normal, with luminance slider performing as expected. 1.7.0.209 - NEF files.

Agree with all above. Saturation slider has no effect in Develop persona when working in 32 bit; seems to work correctly in 16 bit. (1.7.0.209). Files are Nikon NEF.

I concur with Scott and others in their conclusions that the luminosity slider in the HSL filter seems to be acting as the saturation slide, except for the fact that it de-saturates an image at each extreme of the range. That surely cannot be what the coders intended. If it is, why? Happy holidays to all!

I would like to request that AP have the original file's location as the default place to save images once they have been developed/processed. At present AP save defaults to the last used location rather than the folder where the original (RAW?) file is stored. This would be particularly useful when using a DAM programme to round trip between the DAM for cataloguing and Affinity Photo for processing, and potentially avoid a bunch of searching and clicking when the location of the original file is buried deep within a catalogue filing system. Thanks for considering this possibility.

I use Photo Supreme 3 as my DAM software, and it connects easily and simply with AP 1.5.0 release. However, when saving a developed file, AP does not default to the file's original location for saving. This means that to round trip a processed image from DAM to AP and back I have to plough through my file directory searching for the original folder in order to save, save as or even to export. Am I missing a trick or is there a simple way to make AP save files in their original locations by default? Many thanks.

Thanks for clarification. Using the toolbar at top the buttons work as expected. Regarding adding a selection, the hint at the bottom isn't very clear; "Drag + Rightmouse" adds a selection but deletes the original, previously drawn selection when the right mouse button is released. The only way I got the hint to work (i.e. add a new selection) was to "Drag + Right Button + Left Button" and then release the left button before releasing the right one. A bit cumbersome; is that the way it is supposed to operate?

I am trying to make multiple selections on an image using the elliptical marquee tool [M]. I thought that I had to press the control key to achieve this, but it does not work - nor does any combination of keys allow me to make multiple selections. Is this a bug, or am I doing something wrong? Thanks

Brilliant; high five; that seems to be the solution. I have been turning on the tablet AFTER opening the app. Be nice if I could turn on the tablet at any old time, but in the meantime you have given me a workaround. Thanks

If I recall correctly, the Wacom pointer in the earlier release was the correct "brush" circle. TBH, it's only now that I have noticed the brush pointer as an arrow. It is a circle if I use the mouse.

Am using Wacom Intuos pro. Dodging and burning with mouse works ok, although a bit laggy and jerky. However, if trying to use tablet, cursor shows arrow rather than brush and although it "paints", it does so very slowly and with significant lag. Scrolling and panning with the tablet is also hit and miss and occasionally just does not respond. Same action with the mouse works fine.

The shadows slider still not working as expected in the Develop Persona. The equivalent slider in the Photo Persona works very well; can the same tone curve algorithm be applied in the Develop Persona? Happy to see the White Balance sliders now both revert to a default of 0%. Great job! Thank you

The "Shadows" slider in the Develop persona has a very narrow/steep response curve so that only a very restricted range of dark tones are affected. This makes it impractical to use the slider to its full extent, unlike the equivalent one in Lightroom, as the images just go flat and muddy. The "Highlights" slider offers a wider operating range, and is similar to the Lightroom equivalent. The "Temperature" and "Tint" sliders in the "White balance" section operate as expected except for the double clicking of the slider button. On double clicking the tint slider it defaults to 0, but the temperature one defaults to 2000K. Would it be possible to make them default to the "As shot" condition? I know there is a reset button, but this changes both sliders simultaneously. It would be nice if one could revert to as shot singly.

Regarding colour profile pass through from AP v.39, I'm having the same problem (washed out colours) using Viveza 2 and Colorefex Pro. My images are in ProPhoto RGB edited on a wide gamut calibrated monitor. The images on the plug-in window appear more washed out than even sRGB. I have changed the profile of my screen to sRGB, but the same washed out colours persist. :(