john30 Posted November 28, 2022 Share Posted November 28, 2022 I have started to use DNGs from a Galaxy S22 Ultra and the image is opening very dark. They open OK in FastRawViewer and after asking LibRaw support they think “Probably Affinity does not takes 'BaselineExposure' DNG tag into account on rendering” . Can this be corrected as it makes a lot more work dealing with the DNGs. This widows and version 2 Affinity. 20221128_102155.dng 20221128_102308.dng Quote Link to comment Share on other sites More sharing options...
rvst Posted November 28, 2022 Share Posted November 28, 2022 I don't have a solution, but I can confirm the same behaviour here on both Affinity v1 and v2. Other applications display this DNG with what appear to be around a +3.5EV exposure difference. Not seen this behaviour before. Quote Link to comment Share on other sites More sharing options...
john30 Posted November 28, 2022 Author Share Posted November 28, 2022 Thanks I haven’t tried in V1 but I did try some downloaded DNG's from other phones and they opened much lighter so there is something odd with how Affinity is dealing with these DNGs as the RAW data works no problem in FastRawViewer which uses the same RAW information as used in Affenity. Quote Link to comment Share on other sites More sharing options...
rvst Posted November 28, 2022 Share Posted November 28, 2022 1 minute ago, john30 said: Thanks I haven’t tried in V1 but I did try some downloaded DNG's from other phones and they opened much lighter so there is something odd with how Affinity is dealing with these DNGs as the RAW data works no problem in FastRawViewer which uses the same RAW information as used in Affenity. I have a Galaxy Note 9 and I regularly use DNGs from the phone. They do not suffer from this problem. Quote Link to comment Share on other sites More sharing options...
john30 Posted November 28, 2022 Author Share Posted November 28, 2022 Will they pick up what is clearly a bug from this or do I need to pass this on elsehwere? Quote Link to comment Share on other sites More sharing options...
rvst Posted November 28, 2022 Share Posted November 28, 2022 1 minute ago, john30 said: Will they pick up what is clearly a bug from this or do I need to pass this on elsehwere? You should file a bug report in the appropriate forum: https://forum.affinity.serif.com/index.php?/forum/78-photo-2-bugs-found-on-windows/ Quote Link to comment Share on other sites More sharing options...
john30 Posted November 28, 2022 Author Share Posted November 28, 2022 Will do thanks John Quote Link to comment Share on other sites More sharing options...
carl123 Posted November 28, 2022 Share Posted November 28, 2022 I dont think the S22 is on the list of supported cameras as yet Quote To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time. Link to comment Share on other sites More sharing options...
john30 Posted November 28, 2022 Author Share Posted November 28, 2022 There list stops years back with phones, LibRaw apps open OK with there stuff and they are going to add the phone to there list as well now and they thought it was a problem with Affinity causing the way they opend. I just relized that the other DNDs I tried also all said there was no lense avalablee, one that worked OK was a Pixel XL and a Google pixel 6 neather are on the list and both opened OK Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.