Jon Mac

Hi hi...
Ok, so I have had a look round for any suggestions and found that I can move closer to parity if I download the Affinity Photo Beta.
I am now running OSX El Capitan 10:11 with a beta build of Affinity Photo 1.3.5.3.
I can now work backward from either photos or Aperture. For instance I can bring a photo up in Aperture and select an option to edit in Affinity and I can also now bring a photo up in Photos and use an Affinity plug in to carry out an edit.
Step forward !!! :)
However, the issue of not being able to open Aperture or Photos from media browser in an external drive still holds.
I can however look into the systems (on board) copy of Photos and see photos.
Using the on board Photos library isn't an option as space on my MacBook Pro is at a premium, hence using external drives.
You can download the beta from the link found here.... https://forum.affinity.serif.com/index.php?/topic/13346-affinity-photo-customer-beta-1353/ 
https://forum.affinity.serif.com/index.php?/topic/13346-affinity-photo-customer-beta-1353/
 
So ABC.
Thanks once more for working on this conundrum.
If you find any more info on this subject I'd be very pleased to read it.
Jon Mac.

This is replicating what happens with MB and images in the Aperture library.  When accessed in Aperture from MB they open as jpegs (or not at all ...) but if you place them in Apple's Picture folder (and use that as a referenced Aperture library), they open as RAWs (NEFs or whatever camera is appropriate). 
 
Guess it's an Apple thing ...  I had similar issues when trying out other Aperture replacements and gave up.

I wonder if there is a way for the developers to work closely with Apple on this? Even though the products are made by different companies Affinity could really use an app for navigating photos and Apple could use a Photoshop like app to work with it. I know Yosemite will have extensions will that make it easy for the two programs to work together?

One of the things that really bugged me about my PS / LR workflow is the way that Photos would get passed back and forth between the two apps. With a typical workflow you start with a Photo in LR and then need to send it to PS to do something that LR can't do. LR makes a copy of the photo so when you are done editing it you now have two similar photos in your library. If you decide you want to edit the photo again you now have three copies and then four etc.
 
The way this operation should really work is you make an adjustment in Apple's upcoming Photos app, say move the brightness to 27, and then when you export the file to Affinity Photo it uses the same photo instead of a copy of the photo. You should then see your brightness adjustment of 27 in Affinity Photo and then be able to make an adjustment to the brightness again to 15 which should then show up in the settings to Apple's app as you return back to it.
 
I can understand some of the reasons why Adobe's workflow was clumsy, they were trying to get a 17 year old app to work with a brand new app after all. But now that both Apple and Affinity are both starting out at version 1 and at essentially the exact same time let's try and get the way this works under control.  I disagree with many people on this forum that Adobe's photo solution works pretty well I think there is a huge opportunity for taking on Adobe in this area.

Hi photofriend,
 
Affinity Photo is still in its second Beta (it was launched just a week ago). This means it is a development version, not a finished product, and subject to change considerably during this phase. Creating tutorials/documentation now isn't a priority since they may become irrelevant because of all the changes being made. As soon as we come closer to the final 1.0 version, we will begin releasing more tutorials.

I've created a quick list of references/tutorials for both Affinity Designer and Photo beta here.

thank you, Tony. As a professional photographer the lack metadata is a deal-breaker. 

All up and running, the Mac is a breeze to use and I like the new darker interface of the Affinity. Now on the learning curve :)

Hi all. I'm Dave Harris and I'm another of the Affinity developers. I have been mostly responsible for text, printing and some of the vector import and export formats.

Hi, I'm Tony Brightman. I head the SerifLabs team that have been developing the new Affinity range of applications. We have been deep in research for 4 years but it's now time to show the world.

 

TonyB

Hello all, I'm Andy Tang and I'm also a Affinity developers. I will also try to help out when I can and I look forward to seeing your feedback and work created using our product. :)

Hi, I'm Matt Priestley and I'm one of the Affinity developers. I'll try to help out on any topic, but particularly anything relating to tools, views and document drawing as they're the bits I'm mostly responsible for writing.
 
Feel free to join me and introduce yourself, too! :)

Currently, there seems to be no support for metadata for any image type and, more worryingly, any existing metadata is stripped out of a raw file completely on export. If this is to be a serious contender to existing applications, metadata support needs to be added, imho.

Thanks for the feedback. I will have a look at adding more capability to the EXIF panel.