GFS

Members
  • Content count

    186
  • Joined

  • Last visited

About GFS

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  1. Me too. Trying to move an object very precisely and when you let go, the canvas moves! Would be good to have a toggle for it.
  2. The difference is the noise reduction. It is far more agressive in the AFP vs. Try reducing Luminance noise in AFP and you will see the skin detail increasing significantly. FWIW, I think you can get very close to the same thing with both apps. The difference is essentially in skin tone handling. As an Aperture user, you may want to take a look at a new raw converter being developed by the ex engineering director for Aperture, called Raw Power (produced by Gentlemen Coders). It uses the Apple raw engine (which is excellent) but unlike Aperture, it uses the most recent vs. It is very powerful and easy to use and produces excellent results. Most notable in this context though, is the different skin tone treatment when compared to AFP.
  3. I thought a while back that Aperture had issues with OS upgrades (and it does have a few) but often problems can be fixed very easily. I have no problems with Sierra and I hope High Sierra to be similar, given that it is a largely an under-the-hood upgrade. It will change the file system, which is massive, but really shouldn't cause problems. So if you are having Aperture issues, e.g. the UI not drawing properly, or other strange goings on. Files not being found etc., then a simple, no risk fix, is to Export your project(s) as Libraries. See if they are okay, then Merge these Libraries together to get back to where you were. This can take a little while if the projects are very large, but it should fix everything. Effectively, you are doing a total re-build of your Library/Projects. NB, doing a re-build via Aperture's maintenance UI is NOT the same thing and will not fix these issues. You will probably be surprised to find that the new Library is much smaller too, as space has been saved due to optimisation. Why do I bother? Aperture is just so much better in terms of UI, than Lr will ever be. Here's hoping that Serif can produce something as good.
  4. Hi Stanley, like I said, I just did them as a reminder for myself. Makes sense to me, but maybe it makes more sense to others the other way round. :) Either way ... they hopefully clarify for some, how you can interpret the somewhat opaque (sic) dialog. :)
  5. I did these grabs for myself, to remind me how Blend If works as I transitioned from my old app. They perhaps explain it in photographic terms. Obviously, to do similar for shadows and highlights, you use the left and right of the curve area ... I hope they're useful to someone :
  6. Sort of a stop-gap, but not the real thing.
  7. Opacity is 'missing in action' unfortunately. Also, with Wacom tablets on the Mac, contextual menus in the layers panel do not work correctly (different from when you use a mouse for the same thing). I'm pretty astonished that at this stage Affinity apps are lacking in Wacom support. Seems like it should have been one of the first things to get done and dusted.
  8. Thanks Sima. Wow ... not something you're likely to stumble across by accident. I think Serif need to rethink this a bit. Having 2 different ways of nesting adjustments, which have no difference on their behaviour as a adjustments, but do on their selectioning, is kind of odd. Adjustment layers should really always be added as clipping masks, since being able to select them non-contiguously is useful. Why add unnecessary confusion when life is already confusing enough?
  9. Is there any way to select multiple, non-contiguous, nested (child) adjustment layers, in the same way as they can be selected when they are not nested, i.e. cmd-clicking the layer's name? I don't really see the reasoning behind this behaviour being different when nested, but doubtless there is a reason.
  10. Thanks jhoy. I was hoping I'd be able to quickly clear a mask
  11. Chris_K, I have another focus merge file, that is problematic because there has been some movement. AFPhoto is completely unable to perform a merge. It only uses 4 of the 19 files and if I try working them in batches, it sort of works but really struggles and in the end, it's unusable. I tried with Helicon focus and although there are issues with the movement (which I can repair in AFPhoto) I get a perfectly useable file out of it. (I can supply the files if you want to take a look).
  12. And exactly the same as the one I suggested 3 posts prior, so it must be good. :)
  13. Is there any way to clear (or fill) a brush mask with a keystroke?
  14. I'm currently using AFP a LOT (10 hours per day) having switched from a long time app and currently working on the post for a large book project. I'd still like a DAM. As for AFP and AFD, I am carefully noting all the bugs I find along the way ... AFD I'm using a lot less, but dipping my toes from time to time.
  15. I have to say I agree. I'd like to know if they are actually working on something and to have some kind of timeframe. Choosing a DAM is not like choosing an imaging app. The time investment implications are far greater. As for spreading their resources too thin, on too many apps ... I agree with that as well, but Serif are in business and so they want to make the best profit they can. I can't help feeling that producing the Windows version seriously slowed other development, but more than that ... each decision now has far greater implications as it has to be replicated across 3 platforms and 2 apps + perhaps a DAM and a Page Layout app.