Problem with Leica Monochrom DNG files and Serif raw engine

[Guest]

Hi,

as of build 118, DNG files from Leica Monochrome MM (first version) appear black when they open with the Serif Raw engine (with the Apple engine they appear fine). I have to drag the exposure slider all the way to the right to see a faint image. Before build 118, the raw conversion was excellent. I've installed build 223, but the problem persists.

Thanks

Thomas

With Serif raw engine

 

With Apple raw engine

 

 

 

 

 

 

[Chris B]

Hey Thomas_M,

Sorry about this, I'll look into it for you but could I trouble you for the DNG? Here is a private Dropbox folder.

[Guest]

Thanks Chris, I'll upload it tonight.

[Chris B]

Thank you. Please respond when you've uploaded it as Dropbox doesn't notify me 

[Guest]

OK, I just uploaded three raw files. I hope things come back to normal soon.

Best regards

Thomas

[MEB]

Thanks for the files Thomas. Issue logged to be looked at.

[MEB]

Hi Thomas_M,
This is now fixed in Affinity Photo Customer Beta 1.7.0.128.

[Guest]

Thanks a lot! I'll check it tonight.

[Guest]

Now they're  totally black, I'm afraid...

[MEB]

It's working fine here. Let me check something.

[Guest]

OK, this happens only when Metal acceleration is enabled.

 

With Metal acceleration deselected, the file loads fine. Is this normal?

 

 

[MEB]

Hi Thomas_M,
Thanks for the additional info. It works fine here with Metal enabled. It's probaby something specific to to your config/graphic card. We are looking into this. Just to rule this out, do you mind resetting the app and try again: press CTRL while launching the app until a Clear User Data appears, keep the first three checkboxes ticked then press Clear. Reload the RAW using the Serif engine - does it still display black? Are you using a scaled resolution or the native screen resolution?

[Guest]

I reset the app and tried again, reloaded the RAW using the Serif engine and it displayed black. I'm using the native screen resolution (Default for display), not a scaled one.

As I wrote before, the problem started with build 118; before that, it worked fine with my configuration.

[Guest]

Seems to be fixed with 134. Thank you!