john30

Yes its now fixed, thaks Thanks Chris B

Brilliant is only a little quicker!

They said it was supported in the version Affinity uses, its the same one used in FastRaw, but there was an error in reading exposure by Affinity. Listing it it as supported they now tell me just meant it worked without any changes. They did also ask that support was made aware of the exposure issue not a LibRaw one. And Afffinity sipport found there were problems with the Mac and pad versions.

Well suport have now come back "I have logged this as a new issue with our developers with the information that you received from LibRAW" its slow geting it sorted!

LibRaw have replied to me again and have asked me to pass it onto Affinity developers. I have sent it to support but… “For almost all smartphones with recording DNG-files, adding them to the list of supported cameras means "we got examples, checked, everything works." I don't remember a single case in the last few years when changes in the content of the LibRAW were required to decode DNG files recorded by smartphones (except for the somewhat special case of Apple ProRAW). Google Pixel 7 and Samsung Ultra 22 are no exception, adding them to the supported list did not require any changes to the library, it's just a testament to "tested, everything is in order". More general: We do not provide direct user support for other's end user products (with the exception of ours end-user products, of course). If Affinity takes money from its users, they should be engaged in support without throwing this ball to us. LibRAW is targeted to developers, we're ready to provide support for Affinity team, but they never contacted us. We would be grateful if you could bring this message to Affinity support.” So no one from Affinity has contacted LibRaw.

Well support has come back and they are passing it to developers. Interestingly they found the problem is much wider than I thought, as "the Apple Core RAW that we can use on the Mac and iPad version corrupts the file when opened". Oddly they hope the problem may be fixed in Windows when the next LobRaw version is used. But as I have pointed out to them Affinity and FastRawViewr use I understand the same LibRaw version and FastRawViewer opens Samsung DNGs correctly but Affinty doesn't so doesn’t look to be LibRaw that’s the problem but as LibRaw support said last year “Probably Affinity does not takes 'BaselineExposure' DNG tag into account on rendering.”

Well that didn't happen no change with 2.1.1

Well withn my 22 Ultra DNG on facebook I have been told "Hi John, this is still with our developers to be investigated I'm afraid. It should hopefully be fixed in our next update." Clearly there is a lot of flexibility in that and to take over 6 months that LibRaw support did in as many minutes isn't impressive. Be interesting to see if it happens and what is meant by next update!

2.1 out and still no fix. LibRaw took under an hour to come back saying they had added the 22ultra to there managed imiges so it opened correctly.

LibRaw do it properly as I contacted them a long time agao and they added the phone and said of Affinity not working correcly " Dear John: Probably Affinity does not takes 'BaselineExposure' DNG tag into account on rendering. Please address your question to Affinity." I reported this in the initail bug report, the the DNG problem was Affinity not correctly reading the DNG files. A quick example between the two Affinity and fastrawview

Well many months on, nearly 6 now, and still no fix. Google Pixel I am told works no problem, indeed I tried some old Samsung before getting the ultra 22 and were OK. I have had to warn other users to not use Affinity as its not supporting the DNG produced which is a pity. Lightroom apparently has no problems nor do many other programs which clearly any one with Samsung phones will have to use if the user RAW.

New BETA installed OK so they have done a permanent fix, but Samsung DNG still not fixed.

I have no idea if the DNG for other Samsung are treated the same way or not. But I know the Ultras are selling in approaching Apple numbers now so to not be able to open there DNG correctly could put off any one using a trial Affinity.

Latest BETA had no problems Bitdefender have sorted it. If only the Samsung DNG bug could be sorted as quickly by Serif!