Travelling Man

Agreed Depa, Apple Photos is so lacking. It is aimed at the happy phone snappers and sharers, and it does that well. Will never be a LR replacement and yet LR at times seems overkill to me. But LR is up there with the best as a raw developer. Actually Apple Photos handles raw well quite well, if you can do without selective editing. I tried a workflow that was raw to Apple Photos, process in Apple and then convert to tiff for further editing or not in AP as the case may be. That kinda worked but I really hate all that memories rubbish in Apple and the fact that I cannot collapse the views so that I am only looking at photos relevant to a specific date.

I think it will be a while before we see the Affinity DAM. I could be wrong (hope so) but somehow I doubt it. That said, the beta seems to play well enough (for me) with LR so I am happy enough with that.

Thanks Callum, Good call - that fixed it. Nice to see the Affinity layers being preserved in LR :)

When I open an image in AP from LR it is always version 1.4 that opens, not the beta. It matters not of I open from LR using Edit in Affinity Pro or Edit in Affinity Photo. Is there a reason for this? Thanks Colin

Not easy, Jef, is it? What I will say is that I think for basic raw editing Apple Photo is better than AP at the moment. The only advantage AP has is overlays but if you can edit a well balanced raw in Apple Photos there is no need to round trip to AP anyway. It is the same with LR, very few of my images have to go beyond that to Photoshop for editing - in fact if I need to tweak further I find the Macphun plugins do the job in most cases.

What I have found is that if you start off with a Tiff, AP (1.5 beta anyway) will return a Tiff to Apple Photo. Perhaps a workflow is edit raw in Apple Photo then export a tiff, keeping it in Apple Photo and then edit the tiff in AP. If you want to keep the raw safe you can always hide it. Just wish there was a way to collapse the views in Apple Photos - I cannot understand why headings (dates) cannot be collapsed so the pics are not visible.

Know what you mean. I have been playing with Nikons Capture NX-D and it probably does all I need, except it does not play easily with outside editors. Adobe Bridge works ok and that is free, I believe! Can't get to like iCloud. I hate that whatever it does it wants to retain a copy of the file on my Mac when I just want to use it as a drive in the sky! Maybe I should try Amazon.

But does C1 offer decent DAM? I have not tried it for ages but when I did LR was well ahead of C1 in that area? But I am off topic, this is an Affinity forum so I will stick with my current workflow and await the Affinity DAM or a DAM that can bridge that gap.

If you did that Jef I would like to know how :). The word on the street is that cannot be done due to constraints imposed by Apple. I have noticed instances where Apple says it is RAW but when you look at the file info it is actually a jpg. To be honest, I have tried to like Apple Photos if for no other reason than it is a way to move away from Adobe CC. The fact remains however that LR is a far superior DAM and a far superior RAW editor. Things will hopefully change when Affinity DAM is with us but until then I will stick with LR (and therefore PS due to its integration), using AP for one off jobs whilst I get to know it well. Apple Photos is, imho, there for camera snappers and in that respect it does work quite well.

Not sure if it can be done in the develop persona by using more than one gradient overlay - you can only have one gradient per overlay. Being over to use multiple gradients is what I like about LR and Camera Raw.

I believe AP returns a jpg to Apple Photos but Apple Photos retains an original so you can aways revert to the original state.

Using latest beta with Apple Photos. When editing raw in the develop persona using the gradient overlay, setting the reach of the gradient is difficult as the line does not always behave as expected - it is difficult to control and is not responsive. Sometimes I can drag on the node and nothing happens or it lags well behind my pointer. Is this a known issue? Thanks

Should have said, I am using a Nikon 5300

Thanks MEB. Still a way to go then but getting there :-)

Would the above be better place in the 1.5 beta thread? I am surprised there has been no feed back on the issues raised in the above post. Thanks

Update: Changed the raw development engine in AP from Apple to Serif. Now able to open raw (nef) files from Apple Photos ok. Still has the annoying habit of opening portrait as landscape - where I have turned the camera to portrait orientation to shoot a tower, AP loads the photo in landscape whilst Apple Photos and LR get it right. There seems to be no way to correct this in AP? Also, by using the Serif engine is AP not recognising any raw editing previously undertaken in Apple Photos?

Opening JPEGS from Apple Photo works a treat. The problem is opening RAW (nef) files - AP crashes each and every time. Opening a nef outside of Apple Photos works well enough, although AP does not seem to retain the orientation - portrait orientated nefs are open in landscape.

Am I the only one experiencing this?

Try to edit a photo held in Apple Photos in Affinity Photo 1.5 beta 4 using the "Edit in Affinity Photo" extension. AP opens and then crashes. Happens every time. I am running Sierra which I now is a beta but it is the latest beta and I would have though AP 1.5 would have been tested against it. Is anybody else seeing this behaviour? Tks Colin

If I try to open a PSD in AP beta via LR the AP 1.4.2 tries to open but I get a bouncing icon and nothing else. The beta stays resolutely closed. I'm using Sierra beta 6.

Update - suddenly the extension is showing in Apple Photos but when activated it says that AP Beta 3 cannot be launched. No change re LR. Should say I am running on Mac Sierra.

Beta 3 is not showing up as an extension in Apple Photos or as an "edit in" in LR. Am I missing a trick here? Thanks Colin

The beta seems to play much nicer with LR and indeed Apple Photos, although there are still some rough edges re the latter when handing off a file for editing.

Well that has shot the credibility of the article to bits :-)

Thanks MEB