Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by timlt

  1. +1. Batch tool in AP + macros, pretty powerful. It's certainly true you can't do as much as Adobe "actions" plus scripting options, so if you're expecting that, need to reset your expectations a bit. But you can definitely do a lot more than you may realize at first glance.
  2. I have Paintshop Pro 2020. It's a standalone app not a plugin, but it INCLUDES a few plugins, two of which I've already confirmed worked nicely with Affinity Photo. They are: * Pic-to-Painting (you download this one after installing PSP 2020). I found the plugin file and was able to point to that in Affinity and get it working. * Particleshop. This like a 'dynamic brush engine' that includes really fancy brushes. This one works in many apps: Photoshop, PSP 2020, and Affinity.
  3. Thanks @Patrick Connor, that actually helps. Because if I have metadata created/tagged in other apps (for example, I use Daminion home server now for tagging, searching, etc. all my file assets including images with metadata), at least I can be sure that if I open/edit/save those images in Affinity, the metadata will be persisted not overwritten. For me that's the main thing. The ability to WRITE metadata to all the IPTC extension fields is a 'nice to have', for me personally, I can get by ok without that since I manage my assets in other tools outside of Affinity. Thanks again.
  4. Thanks Patrick. Is it possible at this time to say that Affinity (version Xyz) fully supports all "IPTC core" and "IPTC extension" metadata fields (both specifications are here)? If the team could do that, I think personally, it would put to rest this issue for me and other users who use metadata. Obviously we'd still test, but would be helpful to know if in a current beta release and the intent of the team, all those fields are present and accounted for.
  5. Yep, says it right on their web page. But it crashed in 1.7x, crashes in 1.8x. Calls to their support and issues submitted via their webform go unanswered. Cool app. Terrible customer service.
  6. For those trying to use plugins with 1.8, here's my experience to date with plugins that were designed for Photoshop: Luminar 4.1: works with minor glitches that I'm not sure have any impact on the data. I use even on final quality photos, but with caution, paying attention to the output. Note that Luminar does not promise that this plugin is Affinity compatible. GRFX Studio Pro: Does not work at all...crashes the plugin and Affinity. Advertises that it DOES work with Affinity. AutoFX did not respond to 6 attempts at reaching out through phone calls and their online form for
  7. Posted by @tiffany111 Posted Wednesday at 03:38 AM About plug-in support: Is Luminar 4 a supported plug in ?? I use Luminar 4.1 and the plugin is recognized in Affinity 1.8. I can send photos from Affinity into Luminar, edit, and round-trip back into Affinity. There is some odd behavior suggesting to me that the support is not complete or 100%. For example, some of the editing menus in Luminar that display metadata about the photo (most notable, the filename itself) are garbled. Which suggests that possibly, not all data is being exchanged reliably between the tw
  8. Too late for me--been burned twice on this issue and that's enough. I'm not gonna take any more chances with metadata being lost on my old files.
  9. In case anyone is curious about what fields are in the IPTC Core schema (which I think, IS supported by Affinity), and the Extension schema (which is not), here is the current standards doc at the IPTC site that lists and explains all the metadata fields that are in each schema: https://www.iptc.org/std/photometadata/specification/IPTC-PhotoMetadata-2019.1.html
  10. Agree with the above comments. As I've started a big organizing project with old family photos--over 5000 of them, many of them tagged with various IPTC attributes--I will not be able to let Affinity photo touch those files. That is so disappointing, I wanted to like and use Affinity! So after all the testing of various apps I've done recently, I thought we'd reached a point where I could use Affinity as the photo editor piece, but now I find I still can't trust it with my old files as it may overwrite, omit, or 'lose' some of the metadata. What I'm back to as the fallback plan:
  11. Me too--I tested XMP support and thought it all looked good. Didn't realize that IPTC attributes would be lost (I haven't been using those). Hope this support will be added for full compatibility with other photo editors and management apps. Sadly....this means I'm back to using Photoshop with my Adobe subscription until this is fixed. I was about to start editing and organizing thousands of old family photos, a good number of those have IPTC attributes set on them. I hate to, as I prefer Affinity UI to Photoshop. But I cannot afford to be saving my family photos in non-standard fi
  12. Agree. That should NOT be happening with the latest AP beta, I did some testing, it was carrying through all common metadata field properties on a file. ETA: OK I see in other thread this is talking about certain IPTC properties, I was testing XMP. That is not good--hopefully next beta gets this added.
  13. And we're there. I just stumbled across this thread, but it's worth updating to note that the CR3 support is in and working in the 1.8 Beta. And loving it!
  14. Ah...now THAT makes sense. The thumbnail support for the proprietary file types.....not something I use, but I get why you'd want that. Also I could never figure why so many on this forum in other threads mentioned they used Xnview, this must be "the reason" in most cases, that it supports Affinity filetype thumbnails. Mystery solved! 😎
  15. Interesting--so you think it's a Mac-OS-specific thing? Have you heard that from other Mac users too? FWIW, my machines that it runs well on are all Windows. So I guess that aligns with your experience there.
  16. Can you reproduce the exact same behavior on a second computer configured with similar hardware and operating system? If not, I suspect it's a computer-specific issue. Doesn't make it any less frustrating for you, of course. But may not be a universal issue for all Bridge users. I currently have it installed on 2 PC's at home, 1 at work, not seeing any of those issues. But free admit I haven't tested it with hundreds of thousands of photos or anything at a huge scale, so I don't know how its performance (or the performance of ANY graphics app I use) would perform under those conditions.
  17. Just wondering but....if you have Adobe Bridge for free to use with the Affinity apps, what's the appeal of using XnviewMP at all? I've tried Xnview, I realize it is free anyway, and it has some added functionality that Bridge doesn't have (however, note that Bridge's implementation of IPTC/XMP metadata is more cross-platform standards-compliant than Xnview's is, for those who care). But given that the Affinity products like Photo can handle RAW files, and have a batch processor for things like converting many files at once, I'm not really seeing what Xnview gives you that's useful compared
  18. Agree with you both. Serif are doing outstanding work in offering us a viable solution to the behemoth--Adobe. They've started with the traditional buy-and-own-forever business model for software, which seems like it's still in demand and I think 100% of the people I know, including software developers where I work, prefer that traditional purchasing model to Adobe' 100% rent-forever subscription model. On top of that, Serif's pricing for their apps is very competitive, you get a lot of value for each of those $50 apps. Besides the pricing model, they've built up the three great apps: Ph
  19. The title says it all: I wondered if non-destructive RAW edits that can be SAVED (in a database, in XMP sidecar files, etc., as well as having the history/steps be captured in the history panel as with current normal photo editing) is on the roadmap for Affinity Photo? Either in the app itself, or in a companion RAW processor or DAM application that will handle RAW edits and provide smooth inter-op with Affinity Photo.
  20. Just me--I've tried the Canon DPP as recently as 2 weeks ago, it is a no-go. Not only is the UI clunky and hard to use, the collection and file management features are virtually useless, etc. But on top of that, DPP does not produce as good results with RAW files as I can get with other RAW processors that handle CR3 (including or especially: Adobe camera raw/Lightroom, Skylum Luminar 4, and now, Affinity Photo). And worst of all, DPP is mind-numbingly SLOOOOWWWWWW. Try this experiment: take a batch of 20 good-sized RAW CR3 photos of 20mb each, or more. Convert to 16-bit tif. Time
  21. Wow what a breakthrough. Just installed the Affinity Photo latest beta, available here. For the first time since I got my new Canon camera (which uses .CR3 RAW file format), I can use it with Affinity's raw processor. I've not had a chance yet to test it extensively, to see the quality of the output, and questions like can Affinity handle the compressed ("C-RAW") CR3 format. That's worth checking, as many apps out there which say they work with CR3, will choke on the CR3 compressed C-RAW files and produce bad output (Luminar 4, I'm looking at you). My quick preliminary che
  22. The Unsplash stock photo service--which Affinity Photo makes accessible in the Stock plugin--just acquired major new photo assets which will be publicly accessible. https://www.dpreview.com/news/3125341391/unsplash-partners-with-major-institutions-to-add-modern-and-historical-images-to-its-library
  23. No. The OPTION to use one's OWN cloud storage provider, alongside local storage. Specifically NOT an Affinity managed cloud solution, the lack of flexibility of that approach, and the rigid pricing structure, is already evident with Adobe's current Lightroom "cloudy" subscription, it's turning a lot of people off and away from Adobe. Any DAM solution should be a modern "cloud friendly" solution, meaning you can select your cloud storage provide (dropbox/onedrive/gdrive/other) and use that if desired, with good performance and no 'file corruption' due to the syncing process. But that
  24. With Affinity's strong track record on the individual editor apps and publisher, if they produce an integrated DAM with solid metadata support, syncing files in a cloud-based world and not tied to one PC like the badly outdated Lightroom Classic (with its SQLite database that wants to live on a single computer), I would buy it tomorrow--sight unseen. Seriously. They produce a nicely integrated DAM, then they'd have a killer end-to-end integrated graphics development system that would be hard to beat.
  25. Ah, cool. That's something I haven't tried. How do you first select the eyes so that it will apply color change just to those areas? ETA: never mind, I figured it out. Used the elliptical section tool to select eyes, then the recolor adjustment layer as you said.
  • 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.