Jump to content


  • Content count

  • Joined

  • Last visited

About GFS

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

789 profile views
  1. On the Mac, this is called the Finder, although most people wouldn't be aware of how powerful it is.
  2. You may be in luck! Nik Bhatt, ex-lead of Aperture, brought out his excellent RAW Power app a while back. It taps into the MacOS built-in RAW decoding, which is used/maintained for Photos. This is what Aperture uses too, although Aperture can no longer use the current decoding. A couple of weeks ago at Apple's WWDC, Apple announced that they are going to allow developers to access to Photos' database in 10.15 Catalina. This means that apps like RAW Power will be able to use the Photos database, which crucially will allow them to share all that metadata and perhaps the adjustments. So I would imagine, that you will be able to import your files into Photos, but then ... not use Photos ... and instead use something else, with more features and a better UI more suited to pros, like RAW Power. The long and short of it is that Nik could build RAW Power into as good a DAM as Aperture AND it will be able to read your Aperture Libraries (because Photos already can). Did I just make your day? Maybe give him some encouragement ... https://twitter.com/gentcoders https://gentlemencoders.com/raw-power-for-macos/
  3. Thanks for the replies. As you said Walt and R C-R, AFP is respecting the metadata, which is great and my problem was coming from the way that Aperture handles files which are lacking a metadata date. In fact, what it does is it displays the Finder date in the exif date field, but if these files are exported *as originals*, that date is not included, presumably because it is not a part of the original file. So that is as it should be. If you export as a version, then the date is applied, which equally, makes sense. On top of this, it turns out that it's trivial to set the date permanently in the originals, within Aperture. So my problems is solved without any headache ... just a lot of fiddling, checking, searching etc. Also good to see that AFP is handling batch conversion in a useful way.
  4. Thanks again and I should have been more specific about which date, but those still don't answer the question. FWIW and not relevant for much longer, Aperture can batch change EXIF date. So I already have this ability. The question is how to batch convert (or retain in AFP when using Batch Job) the original file date, so that the new file's date matches the old (original) file's date. I have many thousands of these images, so doing them one-by-one would be time consuming.
  5. Thank you for the reply. These don't address the issue though. The question is not how to change a file's date, it is how to retain the date of the original file when batch converting (the exif date ... not the Finder date).
  6. Hi, I'm finally preparing to move away from Aperture, which I still use for its DAM, which remains by far the best, as far as I can see. Sigh. I have several thousand old tiff files, that are unsupported in 64bit (you can test this by starting up in 64bit mode on you Mac). Happily, whilst AFP 1.6.7 choked and crashed horribly trying to batch convert these old .tif files to modern versions, via New Batch Job, AFP 1.7beta cruises through them with much appreciated speed and solidity. So far I have made a >2,000 batch conversion. Problem/Question: Obviously the Batch Job is producing a new Tiff LZW file, which has a new date. Is there any way within AFP that I can set the date to the same as the original file (I can't find anything) or does anyone have any suggestions how I can keep the original file date? I suppose it could be done in the Finder via Applescript, but this is beyond my capabilities. Seems like this is something that could be desirable for quite a few people.
  7. There is a bug with inPainting on a pixel layer. I'm not sure what the problem is, but I'm *guessing* it may be to do with having elements of your file (layers) being outside the canvas area. Anyway ... this fixes it for me: •Group your layer •Copy the Group •From File Menu choose - 'New From Clipboard' •Use Transform to get your Group back to correct position and also resize canvas as necessary •UnGroup (This may fix some other weird stuff too)
  8. I stopped using AFPhoto 18 months ago, due to the extensive masking bugs. None fixed to date. I bought but never used AFPhoto iPad, but decided to give it a try out a few days ago, as I had to work on a legacy file. Disappointed to find more masking/brushes bugs and tools which lack functionality compared to the desktop version. When Serif first launched the AFDesigner/Photo betas, the company performance and responsiveness to comments, bug reports and feature requests was phenomenal. I think they've made strategic mistakes in expanding too fast, though obviously they would completely disagree ... it's incredibly hard to build a good reputation, but very easy to loose it. My own view is they need to build bug free apps, before they move onto more (presumably bug filled) apps.
  9. And there I was thinking that the cross between Michael Jackson and Fagin look was so appealing. So why is this even an option?? I have to say though, that after almost 25 years working with a Wacom, it’s kind of strange to be working directly on the screen. Difficult without a circle showing where the brush is though.
  10. I’ve been trying out the iPad vs of AFP (I moved away from AFP Mac 15months ago, due to its numerous masking issues ... still unresolved). However, having to work on some legacy files in the last week or two, I thought I’d give the iPad vs a go. I’d bought, but never used it. I have the 12.9 Pro and Apple Pencil. However! Using the Apple Pencil, I’ve found it really hard to avoid accidental input on the iPad and it can be a nightmare for messing up work. The problem is that your ‘pinky’ can be inputting without you noticing, or even I think, the side of the palm. I’ve even seen it happening in some of the Affinity instructional videos. So ... being old enough to recall darkrooms and the handling of negs and trannies, I happen to have some white cotton gloves lying around. The perfect solution? Not only does it work perfectly, but you have the added bonus of constantly polishing your screen!! Cost? ~2€. No complicated programming or software revisions required, only a pair of sharp scissors. Machine washable. Good for cold winter days. Eco-friendly. ‘It just works’. Maybe Serif could do their own cool designs? Michael Jackson eat your heart out:
  11. 18 months, no comment from Serif? Sigh ...
  12. Hi MEB, thanks for jumping in. The colour picker is indeed the problem, but the bug actually goes beyond that. Obviously, you wouldn’t choose RGB sliders to change the colour from white to grey to black (3 sliders instead of 1). But playing around with them, I find that the HSL sliders are also buggy (which is what I normally use and therefore why I tried another colour model when I found it not working correctly). Sometimes the HSL choice is refusing to paint at all, when white is selected. I switch to black and it’s as expected, back to white ... nothing. In fact, right now, switching around, I can’t get HSL to paint with white.
  13. Any chance of a reply from someone at Serif on this?
  14. OK, here's a couple of grabs ... Mac & iPad. I can't find anything on the iPad that I'm doing wrong. Opacity set to 100% etc. GFS-AFP-iPad-2.mp4 GFS-AFP-iPad.mp4
  15. Bumb on this ... where do I send the screen-recordings?