MacGB

Well Andy, To be honest, the develop extension does not do much more or even less then Photo's can do by its-self (that is at least my opinion). So If you like to do profound edits in RAW you are better off using the extension "edit in Affinity Photo" as you wil have much more possibilities, using the full power of Affinity. And that extension works great now.

@ henryb Well... not quite. The extension "edith in Affinity Photo" works fine for as-well jpeg /tiff and RAW. Great ! One "pity" though. After saving a RAW back to Photo's, you cannot re-open to continue with the edits. It will always start with the original RAW. The extension "Develop" works for jpeg, but still not for RAW. When I open a RAW and want to save the edits I still get the message "unable to edit with Affinity..."

Well on the positive side: It works for RAW, which it didn’t, the extension develop works for jpeg. That’s an improvement also. It’s still a beta release for which Affinity indicates they are still working on a solution because it hasn’t been fixed in this beta. so I keep my hopes up.

As far as I understand from the API from Photo's The RAW wil be replaced as a jpeg with the changes. I am not sure about the history though. When I re-open with Affinity extension, it always opens the original RAW, without adjustments. There are extensions that keep the history (depends though, it's a rather complex story).So they start with the adjusted photo. This might be of interest to understand how Apple Photo's can interact. https://tidbits.com/2019/06/14/the-ins-and-outs-of-non-destructive-editing-in-photos-for-mac-and-ios/

@SteveB523 Thanks for your response. Well I did try that to no avail, However I took another jpeg made one adjustment, and that went fine after Flatten. So I experimented a little more, making more than one adjustment to that same jpeg , resulting in being not able to save back. Took a different jpeg (from another camera) did the same: multiple edits, not able to save back. So I did another experiment. Open a RAW make multiple adjustments in Develop mode. Followed by multiple adjustments in the Photo Persona that went ok. So still in beta and some work to do for the team I guess

After installing the 1.8.0.163 beta I can report following: Extension "Develop" works for jpeg, but not for RAW to save changes to Apple Photos Extension "Edit in Affinity Photo" works for RAW but not for jpeg to save changes back to Apple Photo's. I didn't test the other extensions as they where fine in version 1.7.3. (Will try those perhaps another time). Cheers

So sorry, you are quite right. I was mistaken with some other app's. They don't all handle this as good as you do. My apologies .

ON1 Photo RAW does. Does Pixelmator edit RAW's and keeps history of the edits when saved back to Photo's ? In the past they only worked with 8 bit jpeg's ?

@fatihayoglu and Cecil. Be aware that when you use the "Right-click edit with" option in Photos it will always sent a 8bit jpeg to the editor. So for RAW-edits this is not an ideal route to go. That is not a fault of Affinity, but a limitation in Apple Photos. When I have some extra time next few days I will instal the Beta 1.8 and see what I can find using the extensions from Affinity.

@ SteveB523 In general I can agree your observations, except for your opinion about Apple Photo's. You can define an own folder structure, you can ad Keywords to your own like, The metadata is exported as exif- and iptc-data (which is rather as it should be).But I guess you figured that out already. I can see though that Apple photo's is not designed for or targeted at professional photography or for everybody depending on their needs or likes. Apple Photo's is designed to work with external extensions..(with some limitations). Even Affinity proves that , next to a number of other professional editors, as 5 of their 7 extension work fine today, and certainly the retouch extension has a wealth of possibilities. All 7 worked in previous versions. So yes, I believe strongly that they will solve the issue (as other vendors already did). In the mean time I can use the majority of their extensions, and when I change my workflow a bit, also the "edit in Affinity Photo" and use that to its full extend. (At the same time a bit more speed to solve the issue would have been nice -;)). My 2 cents, and yes: Happy new year to you too (and all the others of course).

@ henryb, Did I misspell or don’t I understand what you are writing (English is not my native language) ? Because that is what I wrote in my replay to Brantc.

@ Brantc It’s definitely not Apples fault. I am running at least 4 other apps with extensions that didn’t and don’t have this problem. @ Mille 19, I understand what you are after. It has worked in the past, so I still hope Affinity will sort this out. And there are other Apps that you could use as DAM, the way lightroom does. I am not going to mention them in this thread, but I am sure you will find them, but with some patience Affinity might solve the issue.

@ mille 19 Does LR save directly to Photo’s ? Or can you even fire up LR directly from with in Photo’s (and I mean without the right-click feature in Photo’s but opening RAW directly from Photo's to Affinity). If not you might still be better off with Affinity.

@Richard, (and others) I can partly agree, however this problem was introduced with the release of Affinity Photo 1.7. ... even with Mojave. I reported that already with the Beta of 1.7, but the problem got never solved so far. I am not complaining in every post or thread in this forum. But to me Affinity for sure isn't handling this adequately. It's a great app, however for those who rely on Photo's as a DAM, like me, it's not that suited. The only way present to use, is to change your workflow. So yes you can edit from Apple Photos to Affinity, and then need to export your Pictures elsewhere. Not working for me though. presently this is the only way I can think off, as well for RAW as jpeg edits. Using the app. "external editors" sents of a jpeg or a tiff (depending on the settings within that app.) and saves back a jpeg to photo's. Not happy with that either. There are some app's, that handle that in a perfect way. ( so keeping RAW's including their editing history). I'll stick to those for the time being. Luckily I was able to buy the Affinity app's with a lot of rebates at the time, so I take my losses , and wait for more to come. By the way bug reports would help I guess.

Interesting though that this app. stilll works as developed “ages” ago (I was one of the first time users) and the Affinity team isn’t able sofar to work this out ?. I guess it’s because it’s supposed to save the history of edits as well in stead of creating a ‘baked” in result as the external editors app does. However there are some other app’s that do this very well, like oN1 and RawPower.

The "develop" extension works fine with jpeg, but not RAW, The "edit in Affinity Photo" is not able to save back to Apple photo's, not for RAW and not for jpeg.

Using official Catalina (10.15) since yesterday. Using the extension "edit in Affinity Photo" opens up the file, but upon saving get indeed the message " Unable to Save Changes for “Edit in Affinity Photo”. Dito with the extension Develop (old bug). The other extensions work ok.

I am able to use the extension "edit in Affinity Photo", I can make changes, they are saved back into Photos. However when I reopen with "edit in Affinity" to continue editing, It opens up the original RAW file without the previous edits. So the history isn't saved. (I did not make any changes with Apple Photos or any other extension on the same picture). In the Beta it still has the same bug. I reported this behaviour already in the Beta's. I was assured that it would be solved as from the first release of the official 1.7. Still no change. Very disappointed and quite useless in this way (for my workflow that is). I am running Mojave 10.4.6 and Affinity 1.7.3

First off all I am very happy with Affinity vs 1.7. I noticed that (as in the beta of 1.7) the "Affinity Develop" extension for Apple Photo's is not able to write back RAW-edits to Apple Photo's. (screenshot). At the time of the beta it was assumed it had to do with the sandboxing. However after installing the original 1.7.0 and 1.7.1, the problem still exists. macOS vs 10.14.5 Apple Photos vs 4.0 Affinity Photo vs 1.7.1 This doesn't occur opening jpeg, just with RAW. No big issue as the extension "edit in Affinity Photo" works fine All other extensions work fine.

Thanks Chris. I just wait and see then and won't bother you again with this issue. Cann't wait for the new release

Hello Chris, Still very exited about version 7, however the latest update 1.7.0.116 still doesn't fixe using the "develop" extension with Apple Photo's. it opens fine and I can make adjustments, but it still reports the failure mentioned in my opening post when I try to write back to Apple Photo's. Other extensions seem to work fine. Hope you are able to fix this (but please not at the cost of the extension "edit in Affinity Photo" because that is a big enhancement !) Best Regards Ben

Sorry to report that the latest update 1.7.0.112 still didn't fix this issue.

Hello Chris B, Thanks for the info Some extra info. When I use a jpeg-file, it works fine.Because off that I was thinking it might have something to do with "not-flattening" the image before writing back ? The needed flattening is perfectly handled now with the Affinity extension "Edith in Affinity Photo" in the beta, This is really a joy to work with.

In Apple Photo's Opening up Affinity Develop with the extension "develop" fires-up a Develop module in 1.7. with the RAW-photo from within Apple Photo's. However saving back (with or without adjustments) reports an error saying "Edits with Affinity Develop not possible, an unexpected error has occurred" (see screenshot though that is in Dutch, hence my translation ) The file in question is a RAW file from my Panasonic G80 extension .RW2. When I use the extension "edit in Affinity" it works ok.

Hello Chris, Thanks again. Yes I see both as well (different icons), but they both open the beta version . But then again it is no problem for me. I suppose when I would delete the beta it will work with 1.6.11, but for now I am going to experiment a bit further with the beta.