Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by GFS

  1. I'm lost with code, but would like to know if I can configure AFD's export SVG settings (More) so that my exported SVGs match the settings in this example file?  (FWIW, this example works perfectly with Filemaker).  Here's the code (opening the SVG in a text editor) and I attach the sample file as well.

    Does anyone know if/how an SVG can be output from AFD to match these settings?


    <?xml version="1.0" encoding="utf-8"?> 
    <svg version="1.2" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" 
    	 x="0px" y="0px" width="50px" height="50px" viewBox="0 0 52.33 52.33"> 
    <path d="M19.833,0L32.5,0 32.5,19.833999 52.334,19.833999 52.334,32.500999 32.5,32.500999 32.5,52.333 19.833,52.333 19.833,32.500999 0,32.500999 0,19.833999 19.833,19.833999z"/> 



  2. 16 hours ago, davidg2020 said:

    Whilst some of the digital assets I am managing are image files - RAW, JPEG, Photoshop and the like - these are not the only files that qualify as digital assets.

    I currently use Bridge to view these files plus InDesign, Illustrator and PDF documents, which is does quite well showing document previews for quick and easy visual identification of each file.


    You might want to dig deeper into the Finder.  It is a very powerful database and gives you most of the tools that you are after. 

    For file management organisation: I barely use Folders, because they are totally opposite to what computers do so well.  I use Smart Folders (searches), Tags and Comments (keywords).  With these three things you have an extremely powerful organisational/management tool. For example ... all of my RAW files just get dumped into Root folders.  No traditional Folder organisation whatsoever.  Of course, I never ever look at the files this way, because in practical terms,  although my files are in a single place, they are equally in multiple places simultaneously... as many as I want in fact, thanks to Smart Folders.

    Tags:  You can make as many Tags as you want and you can give the standard ones keystrokes too so these can be used for rapid rating etc. (You can also rename them). They're also available in all standard Mac dialogs (Serif... who knows why... don't use standard Mac windows, so you can't add Tags via the filename in any Affinity window).

    Comments:  You can batch manage Comments, which perform in exactly the same way as keywords in photo apps, except with the advantage that they do it throughout the entire system instead of just your app.

    Smart Folders:  These are REALLY powerful.  They have built-in boolean functions (and/or) and can be used to dig down into some incredibly detailed criteria.  They can be visible in every Finder window, or you can put them where you want anywhere on your system.

    If you combine these 3 things with:

    Gallery view: which gives you thumbnail/large view and essential EXIF, Rotate and Markup etc.  You can zoom into any image preview, even beyond 100%, with 2-finger spread.

    QuickLook: (Spacebar) which can zoom in and out of images with + - keys.   Will scroll PDFs as a single page... just like a webpage and which gives you direct access to Markup, Rotate and video Trim etc.  will play and Trim video files, without having to open any app.

    SlideShow: Access via QuickLook or Contextual Menu (using Option-Key).  Full-screen images on dark background... single and multiple.  Navigate via keys.  Ideal for quick presentations.

    (QuickLook/SlideShow.. cannot Tag/Comment individually via keyboard... it's applied to all because they are all 'selected')

    Automator: which is the 'glue' for rapid automation, e.g. batch keywording via Comments, keyboard-command Tagging, Image conversion, Colour-space conversion, Resizing, Sharing, uploading etc. etc. etc. etc. etc.  You can add all off these things to the Services menu (2-finger-tap on file/folder/anything) and even give them their own keyboard commands.  What you can do with Automator is pretty much limitless, as it can include AppleScript, Terminal commands and SQL, but there is quite a learning curve when you go beyond the basics, although there is a very active online community too. As an example, I have an Automator Service, which will take a folder of images, resize them, convert to sRGB, remove accented characters from their names (I'm in France) and zip them *as individual files* which I can then upload to my ftp server.

    You can of course, do all of the above in full-screen ... even Dark Mode now, which is better for images and the Finder gives you a wide range of Sort options + the Arrange menu.

    I've really only touched on the aspects that the majority of users are probably not very familiar with, but there is obviously a lot more to commend this approach, not least the fact that if you are in the Mac environment, then ALL of this stuff is retained across Macs and via iCloud too.  It would require a changed mindset for most users, but in my experience, it takes about a month, maybe two, to get used to new ways of working, e.g. using certain Trackpad gestures instead of old habits, or ... I'm currently having another go at Spaces in Catalina, which I haven't tried for a long time ... and I have to say... they're not too bad.  (FWIW... I use all the gestures! :12_slight_smile::13_upside_down:).  A dedicated DAM like Aperture, will obviously be slicker, but conversely cannot handle any and every file type.

    I should add that if you move files onto Windows disks, they will loose their Comments (keywords) as the Windows file format doesn't support them.

  3. I wonder if this isn't a decision about speed by Serif.  I expect that AFP has a pyramid of internal jpegs for display and adjusts on the fly for in-betweens.  Blur is slow to calculate and can bring AFP to it's knees in processing ... although this has improved significantly with 1.7x.  Perhaps it would be enough to simply offer a checkbox to use 'accurate' previews, when desired.  My old favourite imaging app had this waaaayyy back in the mid90s.  A simple toggle between speed and accuracy.

  4. Thanks Walt.

    You're correct.. and there I was thinking that zoom to 100% to see if, e.g. banding is really there, days we're over.  Ho hum.


    This remains an issue.  I need to be able to see my entire image on-screen, in order to judge how much blur I want to apply.  Zooming in to 100% on a ~100 megapixel image is completely unworkable in this regard.

    So at the moment, in order to see how much blur I want, I have to make a guess in AFP, Export to tiff, look at that, go back, adjust, Export to tiff, look at that, go back adjust, Export to tiff, look at that ... I think we call this a problem.  The AFP preview (on-screen image)  needs to be accurate.

  5. Just now, MEB said:

    Hi GFS,
    This mask issue was caused by a bug introduced in the latest app update. It's now fixed in the latest Beta and the fix will be include in the next retail update. Apologies for all the trouble this has caused you.

    Hi MEB,

    thanks for the reply.  I couldn't find a Mac beta to use instead, so I had to workaround ... neither of the above 'fixes' actually fixed it for me.

  6. I don't think Serif realise how bad this is ...

    I stopped using AFP because of the several serious masking issues I reported 2-3 years back. Nothing was done until 1.7, which fixed some of them, but even then, not fully.

    Yesterday morning I had a client asking for some variations on some images, from back then and I've just spent an hour trying to work out what the heck is going on.

    I realise that most amateurs don't get into much compositing, but it's crucial to many pros and this is definitely NOT what I would call a professional approach.  When I suggested a couple of years back, to one of Serif's forum guys, that he was talking crap, when he said it's normal that a Preview doesn't reflect the result, he reported me for bad behaviour, which I guess was an unfortunate pointer and it doesn't look like anything has improved.

    I'm fairly annoyed right now, which doesn't seem like the attitude you want to be encouraging.

    Serif really really really needs to address ALL of these masking issues as quickly as possible.

  7. 8 minutes ago, tnargs said:

    @GFS that's great, but is there any means today, or possibility in the future, for a Lightroom user to go over to Photos without losing everything? At least keeping keywords/tags and star ratings? I appreciate that keeping Collections is probably a bridge too far.



    I think this will depend on whoever and whatever apps, if any, take advantage of MacOS 10.15 giving developers access to the Photos database.  We just don't know yet.  It hasn't even shipped. (Another month?)  Obviously it would be in the interests of any developer to make a transition to their system as simple as possible.  I would imagine that Catalogs and Collections would be easy as they're essentially a database question.  Adjustments may be harder.


  8. It looks like he's proceeding with the DAM aspects.

    As for using Managed Libraries in Aperture ... most users didn't understand what this involved, or that Aperture offers the choice of both Managed and Referenced, with a fast and easy way of moving files from one to the other.  As any database developer would tell you, the golden rule is to have everything managed, otherwise the risk of damage/loss from things being messed up by human beings remains very real.  Aperture's Managed database is very good (and can be read in the Finder if you really want) and continues to be used with Photos.  Since the changes to the MacOS file system, with 10.14, all of these assets are much safer, because they are constantly tracked.  If Nik Bhatt's RAW Power can tap into the Photos database, as he believes he can, then he should be able to quite feasibly recreate the vital DAM aspects of Aperture.  The added bonus, is that Apple's RAW engine is very very good.


    (Of course, Serif will also be aware of the changes to the OS coming with 10.15, so they too could quite easily produce a DAM front-end for Affinity ... but it would only be for Mac)

  9. 8 hours ago, davidg2020 said:

    I am longing for a true digital asset management application - one that manages files regardless of their source.


    It should also be able to handle (and show previews for) Illustrator and InDesign files (because, like it or not, I have thousands of these files in my archives), video and audio files, HTML files, Word and Excel files and so on. In short, all types of digital assets.


    On the Mac, this is called the Finder, although most people wouldn't be aware of how powerful it is.




  10. On 6/20/2019 at 10:46 AM, Tazintosh said:

    Apple have officially dropped 32bits apps, and Aperture (which still has some 32bits code), can't work on Catalina.
    As professionals, we need to know were to go, how and when to invest. Please answer us guys.

    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 ...




  11. 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.

  12. 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.

  13. 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.


    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.

  14. On 4/1/2019 at 3:05 AM, daws.gragg said:

    Still having trouble please help 


    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


    (This may fix some other weird stuff too)

  15. 45 minutes ago, dave2017 said:

    In the meantime Serif seem to be putting effort into Publisher and other products.

    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.

  16. 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:




  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.