Jump to content
You must now use your email address to sign in [click for more info] ×

MacGB

Members
  • Posts

    61
  • Joined

  • Last visited

Posts posted by MacGB

  1. @ 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..."

     

     

  2. 16 hours ago, SteveB523 said:

    What is supposed to happen? Should the RAW file get replaced with a new Raw file? Or should it replace the Raw file with a JPEG with the changes made? I'm confused now.

     

    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/

  3. @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 ;)

     

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

  5. 7 hours ago, SteveB523 said:

    At a minimum, I would expect a DAM to permit me to define my own folder structure and my own keyword tag hierarchy. I would prefer the keyword tags be written to the individual picture’s metadata (EXIF data), but I might live with an external database. Apple Photos, for all of its pluses, meet none of those requirements.  For that matter, one can’t even generally determine either the name that the photo is stored under or where it is stored.

    So in my mind what a few of you are saying is that you’ve decided to use Apple Photos as something that it’s not really designed to be..

    you can either accept that in good humor OR you can find a different product. But please, do everyone else a favor and pick one of those two options. Stop with the constant bellyaching and idle threats.

    Happy new year, everyone!

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

     

     

     

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

  7. @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 :10_wink:, and wait for more to come.

    By the way bug reports would help I guess.

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

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

     

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

     

    Screenshot 2019-07-13 at 16.04.42.png

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

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

    1700652746_Schermafbeelding2019-02-18om16_34_40.thumb.png.c9cd1121510f3f93444e88f4d7c8e925.png

×
×
  • Create New...

Important Information

Terms of Use | 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.