Jump to content

Amosjl

Members
  • Content count

    7
  • Joined

  • Last visited

  1. Hi, Having recently upgraded to a Lumix G9 camera and seeing the it is on the anticipated compatibility list for your new Affinity Phot 1.7 as DC-G9 I have just downloaded the beta app. I have barely begun using it yet but have noticed that it is unable to deal with any photos taken in the G9's High Resolution mode which uses pixel shift to create an 80mp file using the 20mp sensor. The screenshot below demonstrates the result of trying. is this an issue you are already aware of? I know pixel shift is common technology on other camera platforms too. Regards, John.
  2. Interesting. I’ve never used DXO other than for their Affinity plugin collection but whatever they do in their software seems to avoid the bug/inconsistency that Affiity has on this histogram issue. At least it reassures me that someone else has the exact same thing happening to them.
  3. Thanks Wikinger and owner for taking the time to reply, much appreciated. Hopefully someone from Affinity will provide a steer as to when a fix for this is due and if they have any solutions in the short term. I’m using the clipping warnings to avoid losing tonal range in Develop persona for now but not ideal.
  4. Just a quick update to this topic....more of a warning. Only edit one at a time using the extensions. I've noticed that if for any reason you drop out of an ongoing edit through the extension process mentioned above and do not save, then when you return to apple photos screen the image you began editing with will be replaced by the one you successfully edited before that (if you've been doing a few). If you click 'cancel' on the apple photos screen then no problem, but if you click 'save changes' then the original file you were working on has been replaced by the successful edit previously completed. If you don't realise whats going on (like I did the first time) then when you click back to the thumbnails screen in photos you'll notice all is not quite as you left it with files being overwritten left right and centre. If you notice the error early enough you can rescue the by going back to the file that has been accidentally overwritten in apple photos (the one that never got to the point of being saved in affinity) and click 'revert to original'. Then click 'done' and order is restored and all is right with the world again. If you notice this a little late in the game after many edits then the only way to check which files have been overwritten and which haven't is to go through each one by one in apple phots, selecting 'edit' and click on the before/after button (to the left of 'revert to original) to see if there is actually a completely different file underneath. One to be aware of. Hope this saves someone the headache I had!!!
  5. Hi, A quick question regards histogram compression that I notice when developing RAW files in the develop persona. I know this has been an issue for a while and I believe the work around is to 'develop' the image to take it through to the photo persona and then return to the develop persona again to be greeted by an accurate histogram. Please see below for before and after screen shots of the histogram and file data during this process and notice the change in the toolbar from 'RAW' to 'RGB' and just below that in the file date a change from 'RGBA/32' to 'RGBA/16'. Can somebody from affinity please confirm if this workaround is still leaving me with a RAW file to work with (ie after the workaround as per the bottom screenshot) or if the only actual workaround is to not bother with this and do all RAW editing in the Develop persona without actually having an accurate histogram for reference? Regards, John. Incorrect histogram upon first opening file in develop persona (using apple photos 'edit in affinity photo' extension').... Then after clicking develop, briefly entering Photo persona and returning back to the Develop persona straight afterwards....
  6. Hi, I’m trying to figure out the most streamlined way of editing my imac stored photos with Affinity. I prefer apple Photos as my main catalogue software but Affinity as my main editor and therefore want to save my edits back to the same position in the Photos library on completion. I’ve found the Affinity extensions in the editing options of Photos but have two questions. When using the Develop, Liquify, Retouch etc extensions I can click ‘Save Changes’ upon completion and the edited file will be updated in Photos. This is great but the toolset in these extensions isn’t as comprehensive as the main Affinity suite. I can access the full power of Affinity by selecting ‘Edit in Affinity Photo’ instead but then the option to ‘Save Changes’ back to Photos has disappeared and the only option is a tedious export of each edit from Affinity. My questions are: 1- Is a ‘Save Changes’ option ever likely to be added to the full ‘Edit in Affinity Photo’ extension as with the others (Develop, Liquify, Retouch etc) or is this just asking too much of the software? 2 - If the above isn’t possible is there a way of replicating what I want to achieve by somehow (and simply) exporting the completed Affinity Photo edit back to Apple Photos to update its original? Saving edits from affinity software by exporting to another file system (in documents or pictures etc) is fine if saving edits files for prints, web etc but I’m struggling to see how the FULL power of affinity can still be used to simply edit and save files from Photos back to where they came from. The editing suite within Photos is ok but I’d much prefer io use Affinity. Am I missing something? Regards from a new by, John.
×