timlt

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

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. 

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. 

FYI, I was talking about On1 vs Lightroom.   I don't have any take on C1p, I've never owned or even tried it.  

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 two apps.  But when I make ordinary edits on a photo in Luminar and send it back to Affinity, it appears all the changes are retained.  
I would say that support appears to be promising, but not complete.  As is always the case with plugins, it's not clear whether the lack of compatibility issues lie with Affinity or the company that makes the plugin, and it's ALSO not clear if either company is working on the issue or prioritizing it.   Luminar is clearly prioritizing becoming a standalone application, and they really only promote full compatibility with the Adobe apps.  From one user to another, I'd say use Luminar as an Affinity plugin with caution, and definitely test thoroughly before using with any production quality photos.  

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!
 

Uggghhhh!!! No bueno!
For everyone's sake, I hope this is given greater priority than adding new "gee-whiz" features (which are of course awesome). 
I'm in the process of trying to convince a large company to move away from Adobe and over to the Affinity products for their obvious benefits and the high ROI. But one of the things we absolutely need is to NOT lose full IPTC data during our exports. Even if I'm personally convinced of my enjoyment of the Affinity products, management and other users who deal with images and other media day-to-day will view this as a non-starter as far as switching over to the Affinity suite. 😞 
I'm actually very surprised and more than a little disappointed in this. It will make my task of selling them on this transition much more difficult. It will also negatively impact my own day-to-day tasks. PLEASE ask the developers to move fixing this higher in their priority list. 

I think most Affinity users are waiting for LRkiller, and maybe one third of the users are hoping for TrueDAM. It is very unclear if these two can be combined successfully.

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!
 

Wow what a breakthrough.  Just installed the Affinity Photo latest beta 1.8.0.555, 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 check seems to show that Affinity handles the compressed C-RAW files just fine.  But either way, it's great to see this progress with the Affinity beta.  I'd add to that the ever-improving support for IPTC/XMP metadata handling, there are more of the standard XMP metadata fields supported now and enough that Affinity should be a viable alternative to anybody who extensively tags their files with metadata.  I've tested the compatibility of the metadata support.  Affinity has implemented this 'right' as far as I can tell, by which I mean they've followed the standards and if you tag a given XMP attribute in Affinity, the value will show up correctly if you open the same file in other IPTC/XMP standards-based metadata tools, such as Adobe Bridge or Lightroom.  That is a big win because it means you have better inter-op between Affinity and other photo or file management tools.  For example, you could use Lightroom classic as your photo management/tagging app, and specify Affinity as your photo editor, and all the metadata values will be compatible between the apps.  
For me this makes Affinity once again a live option and a strong competitor to Photoshop.  Thank you and keep up the great work guys!  

Wow what a breakthrough.  Just installed the Affinity Photo latest beta 1.8.0.555, 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 check seems to show that Affinity handles the compressed C-RAW files just fine.  But either way, it's great to see this progress with the Affinity beta.  I'd add to that the ever-improving support for IPTC/XMP metadata handling, there are more of the standard XMP metadata fields supported now and enough that Affinity should be a viable alternative to anybody who extensively tags their files with metadata.  I've tested the compatibility of the metadata support.  Affinity has implemented this 'right' as far as I can tell, by which I mean they've followed the standards and if you tag a given XMP attribute in Affinity, the value will show up correctly if you open the same file in other IPTC/XMP standards-based metadata tools, such as Adobe Bridge or Lightroom.  That is a big win because it means you have better inter-op between Affinity and other photo or file management tools.  For example, you could use Lightroom classic as your photo management/tagging app, and specify Affinity as your photo editor, and all the metadata values will be compatible between the apps.  
For me this makes Affinity once again a live option and a strong competitor to Photoshop.  Thank you and keep up the great work guys!  

Wow what a breakthrough.  Just installed the Affinity Photo latest beta 1.8.0.555, 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 check seems to show that Affinity handles the compressed C-RAW files just fine.  But either way, it's great to see this progress with the Affinity beta.  I'd add to that the ever-improving support for IPTC/XMP metadata handling, there are more of the standard XMP metadata fields supported now and enough that Affinity should be a viable alternative to anybody who extensively tags their files with metadata.  I've tested the compatibility of the metadata support.  Affinity has implemented this 'right' as far as I can tell, by which I mean they've followed the standards and if you tag a given XMP attribute in Affinity, the value will show up correctly if you open the same file in other IPTC/XMP standards-based metadata tools, such as Adobe Bridge or Lightroom.  That is a big win because it means you have better inter-op between Affinity and other photo or file management tools.  For example, you could use Lightroom classic as your photo management/tagging app, and specify Affinity as your photo editor, and all the metadata values will be compatible between the apps.  
For me this makes Affinity once again a live option and a strong competitor to Photoshop.  Thank you and keep up the great work guys!  

Wow what a breakthrough.  Just installed the Affinity Photo latest beta 1.8.0.555, 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 check seems to show that Affinity handles the compressed C-RAW files just fine.  But either way, it's great to see this progress with the Affinity beta.  I'd add to that the ever-improving support for IPTC/XMP metadata handling, there are more of the standard XMP metadata fields supported now and enough that Affinity should be a viable alternative to anybody who extensively tags their files with metadata.  I've tested the compatibility of the metadata support.  Affinity has implemented this 'right' as far as I can tell, by which I mean they've followed the standards and if you tag a given XMP attribute in Affinity, the value will show up correctly if you open the same file in other IPTC/XMP standards-based metadata tools, such as Adobe Bridge or Lightroom.  That is a big win because it means you have better inter-op between Affinity and other photo or file management tools.  For example, you could use Lightroom classic as your photo management/tagging app, and specify Affinity as your photo editor, and all the metadata values will be compatible between the apps.  
For me this makes Affinity once again a live option and a strong competitor to Photoshop.  Thank you and keep up the great work guys!  

Wow what a breakthrough.  Just installed the Affinity Photo latest beta 1.8.0.555, 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 check seems to show that Affinity handles the compressed C-RAW files just fine.  But either way, it's great to see this progress with the Affinity beta.  I'd add to that the ever-improving support for IPTC/XMP metadata handling, there are more of the standard XMP metadata fields supported now and enough that Affinity should be a viable alternative to anybody who extensively tags their files with metadata.  I've tested the compatibility of the metadata support.  Affinity has implemented this 'right' as far as I can tell, by which I mean they've followed the standards and if you tag a given XMP attribute in Affinity, the value will show up correctly if you open the same file in other IPTC/XMP standards-based metadata tools, such as Adobe Bridge or Lightroom.  That is a big win because it means you have better inter-op between Affinity and other photo or file management tools.  For example, you could use Lightroom classic as your photo management/tagging app, and specify Affinity as your photo editor, and all the metadata values will be compatible between the apps.  
For me this makes Affinity once again a live option and a strong competitor to Photoshop.  Thank you and keep up the great work guys!  

Wow what a breakthrough.  Just installed the Affinity Photo latest beta 1.8.0.555, 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 check seems to show that Affinity handles the compressed C-RAW files just fine.  But either way, it's great to see this progress with the Affinity beta.  I'd add to that the ever-improving support for IPTC/XMP metadata handling, there are more of the standard XMP metadata fields supported now and enough that Affinity should be a viable alternative to anybody who extensively tags their files with metadata.  I've tested the compatibility of the metadata support.  Affinity has implemented this 'right' as far as I can tell, by which I mean they've followed the standards and if you tag a given XMP attribute in Affinity, the value will show up correctly if you open the same file in other IPTC/XMP standards-based metadata tools, such as Adobe Bridge or Lightroom.  That is a big win because it means you have better inter-op between Affinity and other photo or file management tools.  For example, you could use Lightroom classic as your photo management/tagging app, and specify Affinity as your photo editor, and all the metadata values will be compatible between the apps.  
For me this makes Affinity once again a live option and a strong competitor to Photoshop.  Thank you and keep up the great work guys!  

Wow what a breakthrough.  Just installed the Affinity Photo latest beta 1.8.0.555, 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 check seems to show that Affinity handles the compressed C-RAW files just fine.  But either way, it's great to see this progress with the Affinity beta.  I'd add to that the ever-improving support for IPTC/XMP metadata handling, there are more of the standard XMP metadata fields supported now and enough that Affinity should be a viable alternative to anybody who extensively tags their files with metadata.  I've tested the compatibility of the metadata support.  Affinity has implemented this 'right' as far as I can tell, by which I mean they've followed the standards and if you tag a given XMP attribute in Affinity, the value will show up correctly if you open the same file in other IPTC/XMP standards-based metadata tools, such as Adobe Bridge or Lightroom.  That is a big win because it means you have better inter-op between Affinity and other photo or file management tools.  For example, you could use Lightroom classic as your photo management/tagging app, and specify Affinity as your photo editor, and all the metadata values will be compatible between the apps.  
For me this makes Affinity once again a live option and a strong competitor to Photoshop.  Thank you and keep up the great work guys!  

Wow what a breakthrough.  Just installed the Affinity Photo latest beta 1.8.0.555, 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 check seems to show that Affinity handles the compressed C-RAW files just fine.  But either way, it's great to see this progress with the Affinity beta.  I'd add to that the ever-improving support for IPTC/XMP metadata handling, there are more of the standard XMP metadata fields supported now and enough that Affinity should be a viable alternative to anybody who extensively tags their files with metadata.  I've tested the compatibility of the metadata support.  Affinity has implemented this 'right' as far as I can tell, by which I mean they've followed the standards and if you tag a given XMP attribute in Affinity, the value will show up correctly if you open the same file in other IPTC/XMP standards-based metadata tools, such as Adobe Bridge or Lightroom.  That is a big win because it means you have better inter-op between Affinity and other photo or file management tools.  For example, you could use Lightroom classic as your photo management/tagging app, and specify Affinity as your photo editor, and all the metadata values will be compatible between the apps.  
For me this makes Affinity once again a live option and a strong competitor to Photoshop.  Thank you and keep up the great work guys!  

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
 

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
 

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
 

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
 

That HP is a fantastic laptop--I had a 2017 one which is now with my daughter, both loved it.  Even has a Thunderbolt port so will work with some very hi-speed storage peripherals that will be compatible with your Macbook.  I bet you will you will like that.  My eldest daughter just got the new 2020 model, and it actually ups the ante over the earlier ones.  They are on a roll with that series.  
Honestly don't know if there's some specific issue with the Mac version Bridge.  Probably I'd ping the adobe forums if you haven't already, sorry I can't help much.  

I agree with the previous, esp the bit about sidecar files not being truly compatible across applications.  If you create sidecar files in any app other than Adobe, quick, can you name one other app that can read your app's proprietary sidecar files?  
The only reasons I can see to create sidecar files are (1) To have a portable backup system to the edits/metadata in your app's database, and (2) Makes it easier to have your RAW edits be accessible on different computer systems.  As long as you're able to backup your app's DB somehow, and if you have a way to use it across systems without sidecars, than there's no need to use sidecars.  I in fact stopped using them with Adobe apps because (1) I can backup the catalog, and (2) I can use it across systems by keeping the catalog and preview files on a flashdrive that I simply move to another computer.  Hence, no need for sidecars at all.  
On your last para:  Adobe Bridge does that right?  
 

I agree with the previous, esp the bit about sidecar files not being truly compatible across applications.  If you create sidecar files in any app other than Adobe, quick, can you name one other app that can read your app's proprietary sidecar files?  
The only reasons I can see to create sidecar files are (1) To have a portable backup system to the edits/metadata in your app's database, and (2) Makes it easier to have your RAW edits be accessible on different computer systems.  As long as you're able to backup your app's DB somehow, and if you have a way to use it across systems without sidecars, than there's no need to use sidecars.  I in fact stopped using them with Adobe apps because (1) I can backup the catalog, and (2) I can use it across systems by keeping the catalog and preview files on a flashdrive that I simply move to another computer.  Hence, no need for sidecars at all.  
On your last para:  Adobe Bridge does that right?  
 

@Xavier Roga thanks for the suggestion, but this is rather off-topic.  I did not ask about buying a different product for photo editing to replace Affinity.