Jump to content


  • Content Count

  • Joined

  • Last visited

About mike21

  • Rank

Recent Profile Visitors

721 profile views
  1. In processing a RAW image in Affinity Photo Develop there is the ability to adjust apparent exposure; in the light of this is it worth bracketing exposures – is an exposure “error” of one or two stops adjusted in Affinity as good as one that is “correct” in the first place. Similarly, is it worth taking three images at different exposures of a high contrast subject for merging into HDR, when just one image can be processed with three separate apparently different exposures.
  2. Thank you everyone - the post from V-KYR has provided the information. The Photoplus magazine has articles and videos describing certain tasks in either Photoshop, Elements, DP4 or Affinity. It is usually fairly straightforward to "translate" procedures into Affinity but I was stuck with the rubylith overlay in Elements.
  3. The method in the article is simple - use HSL saturation to produce a black and white image, use paintbrush tool in black to reveal underlying colour or white to remove overpainting. This works fine in Affinity but the article also showed the "rubylith layer which showed in red the areas missed or overpainted - accessed in Elements using a "\" shortcut. That shortcut has no effect in Affinity whereas the other shortcuts given do.. I seem to remember seeing an Affinity video showing such a facility - it is that which I should like to know.
  4. The latest issue of Photoplus has an article showing how to change an image to black and white and then reveal part in its original colour, such as a red pillar box. The article gives the method in Adobe Elements. It is easily transferable to Affinity except for one thing - it refers to activating the rubylith layer to reveal areas missed or overpainted; this name does not appear in Affinity help, how do I activate the Affinity equivalent.
  5. Sometimes on an image there are some areas in the background that are over bright and out of focus, which distract from the main subject. At the moment I reduce the brightness by using the inpainting brush at a low transparency level, but I am sure there must be a better, none destructive, way. What would you do?
  6. I use the clarity live filter a lot, but with the latest incarnations of Affinity Photo the time taken to Export after using clarity is unacceptably long. With the export save time was insignificant but with 1.7 it stretched up to between 20 and 70 seconds, but with the newly released upgrade it is now at least 60 seconds but sometimes in the mid 70s. I have tried timing with other live filters but all are reasonable – the problem being confined to Clarity. Clarity can be applied destructively through Filters but it is not as good. Please can the Export time problem be sorted.
  7. I took lots of photos at an air display and put the images in separate folders, one for each airplane. I processed each image saving as afphoto and exporting as jpeg. The afphoto files appeared in the folder from which the original image was obtained but the jpegs appeared in the folder of the previous set of images. The destination folder for the jpegs can be corrected each time if remembered. As with the previous version, when a number of images are loaded, the file numbers appear at the top of the screen in random order rather than file number order as loaded. Windows 10 Home ver. 1809, Affinity
  8. Thank you. I will try that. It seems that this situation is something that needs correcting in the new version 1.7 - it was not a problem in 1.6.5 so should be quite easy for the coders to do.
  9. Tried with clarity through filter rather than a live filter layer, and export time is 4 - 5 seconds. The effect is the same but unfortunately it is destructive and cannot be reversed.
  10. I have tried again with another photo. It has had no processing at all, apart from clarity attached to the base layer as a child. It took around 32 seconds to process as an exported jpg. I tried several times with the same result each time. afphoto file attached. IMG_4943 test.afphoto
  11. I was about to try without the clarity filter but I looked for a reply first, so it seems as if that is the cause. There does seem to be a sort of a bug with live filter layer/clarity in that I apply that last and it appears beside the last adjustment layer, say vibrance, and has no effect until I move it up to its own layer. With the previous version I just dragged the clarity "icon" up but with this version that will not work, so I have to click on the arrow which puts clarity as a child - which still not work - but then I can drag it up to its own layer. I would have thought it should automatically go on a separate layer. It was very quick with the 1.6.5 version, between 0 and 3 seconds. I have 444 images from the air show so the additional time is quite significant. Thank you for your help.
  12. There seems no rhyme or reason about how long an individual file will take to Export. I have just processed one and this unfortunately was good at about 20 seconds (attached Sea Fury.afphoto ) - an hour ago I had one that took 73 seconds, when I was about to give up. I have been processing many dozens from an air show and it is taking ages.
  13. I "Save As" to produce an afphoto file then "Export" to produce an 85% jpg file. With the previous version this was either instant or just a few seconds, but now it is up to 64 seconds with most exports taking between 20 and 30 seconds, although just a few will take about 5 seconds. These are not complex files - just a few adjustment layers. I cannot revert to the previous version as it will not recognise the latest afphoto format, or at least the beta version would not. Am I doing something wrong?
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.