F_WRLCK

I'm also having this problem.

You can also use the "External Editors" plugin to round trip through Affinity, which will let you save your .afphoto file. This isn't ideal, but it gets the job done. It would be nice if there were a slimmer file format that just records the adjustments applied or the filesystem location of the .ahphoto file for the plugin, but I'm guessing that's enough of a niche use case that we're not likely to see it. I've also considered just doing image selection outside Photos and only importing finished photos, but that kind of defeats the "edit anywhere" thing that I have now, so I'm reluctant.

FWIW, if you're on OSX, you can use Apple's RAW engine in Affinity photo and get the embedded lens profiles applied that way.

Maybe, but how many computers do you think MS office has sold? At the end of the day, applications are what drive hardware sales and the iPad really suffers from lack of killer apps to drive sales and development of further killer apps.

Yeah, that's pretty in-depth. For now I'm just focused on getting a print that matches what I have on screen.

Thanks Lee! I did try using the Soft Proofing adjustment, but, even after watching the tutorial, I am confused by the parameters to that layer. I understand more or less what the various parameters do, but it seems like there is only one set of parameters that will be right for a given printer, and I don't know what those parameters are. If I set rendering intent to "Absolute Chromatic", how do I know that's how the printer is going to render my file vs. one of the other options? This is probably a really basic question, but I'm super-new to making prints and I have a mental block around this.

I'm pretty new to making prints from my photos. I'm trying to create files to send to Costco for printing. I've installed the appropriate ICC profile and I can see it in the relevant menus (Convert ICC Profile, Assign ICC Profile, Soft Proof Adjustment). Given that I have an image file how I like it in sRGB, what is the recommended workflow to generate an exported file (TIFF, JPEG) that will print like what I see on screen? I have watched tutorial videos/searched google and tried a couple of things, but I have one image that always prints the shadows darker than I expect and seems to have a some purple that goes out of gamut.

...but this thread is titled "Apple Script". Which is one of the OSX automation languages. The OP specifically asked about Apple Script and then this thread filled with people talking about Python, which was, to say the least, confusing. If you want access to internal APIs for building your own Affinity plugins or whatnot, that's great, but what OP was talking about is an automation tool with which, presumably, he or she would like to automate some task.

Yeah, but that's just not how the application automation frameworks work for either Windows or OSX. The application implements the events that it responds to and the OS mediates the exchange. The whole thing is language agnostic.

Tying the scripting infrastructure to a particular language is dumb. Every platform has its own application scripting infrastructure so hopefully the Affinity team is on the ball enough to just use the native mechanism for the platform. Failure to do so would be pretty inconvenient since a big use case for application scripting is to provide adhoc integrations between applications.

AppleScript support really just means that the application has a set of App Events that is has implemented. The scripting itself can be done in either AppleScript or JavaScript. It's also fairly trivial to call these scripts from Python using the osascript utility. In theory, you can implement OSA bindings directly in Python, but all the implementations that I'm aware of are outdated and unsupported.

That's interesting, I hadn't thought of that. That could be useful for people who don't like or don't want to pay for the External Editors plugin. Maybe, but without knowing more we're just theorycrafting. I kind of doubt this is the case because external programs can crash and it would be pretty horrifying if doing so could corrupt your Photos database.

For the record, this does not work. The "Save As..." dialog is greyed out when editing through the extension. Without the ability to save an afphoto file, I'm not sure why you bothered with this extension.

Yeah, I tried out the "Edit in Affinity Photo" plugin that came with v1.5, but it doesn't really provide a useful workflow. You can't save your layered file, which means I'm not going to spend time doing any detailed edits using that plugin. I just use the External Editors plugin. If I'm just editing a couple of files, I'll use it directly. Otherwise, I export the RAW files for my picks and then use EE to replace the jpeg after I'm done editing. Edit: didn't see your last question. If you want to export RAW, you need to have "Use RAW as original" selected for jpeg/raw pairs. Additionally, you can't have any edits on the file because of course that causes the RAW to get developed.

As mentioned, once you develop an image, you can no longer edit it as raw. If you want to start over, you can go back to your original raw in Photos. You can also save a layered document in Affinity and go back to that later. You can't use the Affinity plugin for that though, but there's another plugin called External Editors in the App Store for $3 that is totally worthwhile and will allow you to update the jpeg for any image in your library.

I was really excited about the new Photos.app extension because I'm cheap and use Photos as my DAM and the External Editors plugin is a bit clunky. I was disappointed to learn that there's no way to re-edit a photo that has been sent back to Photos. I can save the .aphoto file off to the side if I want, but there's really no way I can see to re-open this and have it send that rendered image back to Photos without using the External Editors plugin, which kind of defeats the purpose of having your own plugin. I guess your plugin works well enough if I nail the edits the first time, but I'm really not that good, so I'd like another option.

Correct, my ORFs are about 16MB to begin with and yeah, my Affinity photo files are massive. I just assumed that what was being sent back to photos was just a set of masks and layer settings and not the whole affinity file. As it is, this extension is always going to flatten the file and so won't be amazingly useful next to something like the External Editors plugin, where you can reopen the modified file and make further edits as needed.

So far, this has been every photo I've tried. Just develop and add levels/curves layers. Is that expected?

"16MB change limit exceeded -- document will be flattened" What does this mean? I notice that, if I re-edit a file using the Photos extension, I have to start over in Develop. Is there a way to save my layered document off to the side? Affinity documents are quite large, I can't imagine one less than 16MB.

Do you mean that Apple Photos doesn't support XMP sidecars?

In Affinity Photo 1.4.x, you can select which RAW engine to use by clicking on the assistant and setting the Raw Engine to "Apple". Unfortunately, you have to reload the RAW file and you can't set this value without a RAW file in Develop, but it appears to persist between runs. This seems like the way to go for M43 files because M43 lenses lean pretty heavily on their embedded corrections, which aren't honored by the Affinity Photo engine.

I use Affinity + External Editors with ORFs, they are supported. Make sure you have the RAW selected as original. Right click --> Use RAW as original while in edit mode. Oh, cool. External Editors works fine, but having a dedicated path is even better.

Okay, but just to be clear, this isn't a request for Serif to develop a database of lens profiles. In the case of Micro 4/3s, the lens corrections required are embedded in the RAW file itself, they just need to be applied. Many MFT lenses lean pretty heavily on this being the case.

It seems like the answer is no. I notice quite a bit more distortion in Affinity on my ORF files than I do in other RAW converters. I can only assume this is because Affinity is not applying the embedded adjustments. For Serif: Is this a planned feature?

Right, but there're a variety of posts in various places on the Internet stating that once a RAW image has been edited with an extension, the RAW is developed into a JPEG and any edits on top of those done by the extension will be done on that JPEG. For example: RAW photo in Photos Edit using the Affinity Photo extension Edit using extension B From your response, it sounds like the Affinity Photo extension in step (2) will be operating on a RAW file, but what does extension 'B' see in step (3)? Will it still be RAW? Will it be some other lossless format? Or is it, as some fear, just a JPEG created from the output of step (2)?