New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segfault opening Fujifilm X-E2 firmware v4.0 RAF files #3137
Comments
Raw file needed http://filebin.net/ |
File is uploaded, let me know if you need any other information |
The link to the file? |
Sorry, my bad - it is here: http://filebin.net/5f0vykiy6q/DSCF9049.RAF |
Have you confirmed this problem with all v4.0 RAF files, to make sure its not just one corrupt file? |
Yes I have. Also. someone else on DPReview has seen it too. |
Duplicate of #3110 Different cam, but exactly same crash. |
@andymcdonaldU2 can you check in your camera whether the v4.0 firmware default to compressed raw files? Can you try a v4.0 RAF with compression disabled, if possible? |
@Beep6581 have checked the camera menus and the new operators manual and neither mention being able to choose whether to have a compressed raw file or not, so I don't believe that this is something that I can change. |
I haven't seen any word about compressed raw files in the official
announcement for new the v4.0 firmware.
|
I'm the other person who posted on the DPR forum. The X-E2 doesn't support compressed RAW files, in addition to this other non-dcraw based editors can still open them (including a 2 year old copy of Silkypix). The crash is occurring in dcraw within crop_masked_pixels() due to a dodgy looking top_margin value which in turn is derived from a dodgy looking height member. From what little I could tell (not the easiest code to read from scratch) it appears the header format has changed and dcraw is parsing it incorrectly. I compiled parse.h also on Dave Coffin's website, and the broken raw header has quite a few different sections and some tags (such as 0x1020 - Macro) have been removed. I've emailed him some details and am awaiting a response. For your reference, here's another non-working RAF: ...and a working RAF taken before the update: |
'not the easiest code to read from scratch': That's true! |
Ingo, I 've sent you an email about x-pro2, have you received any ? t looks like the reason RT (and Dcraw) crash/freeze is wrong reading of exif (sensor size ?). latest exiftool 10.10 reports at -RAF- group .. I tried with camconst the following
and with this RT stops crashing but still does not decode correctly (just a zone of garbage is displayed). I think that if we had a way to overwrite (a new tag in camconst.json ?) what Dcraw reads as size I would be able to "support" the uncompressed mode. |
@iliasg I was spammed a bit last time, so maybe I missed your email. I'll take a look tomorrow. |
I cannot communicate with Dave :(. The usual Dcraw release at Dec-Jan is already very delayed .. who knows. BTW we need to add raw crop for X-E2 also to stop the crash, although it still decodes faulty. |
@iliasg I agree that avoiding the crash is first priority! DrSlony and Hombre seem to able to communicate with Dave. Last time I tried I failed :( Maybe we should try to communicate this stuff to Dave via DrSlony or Hombre? Ingo |
Hello again, I have received a patch from Dave. The RAF tag had indeed changed and the address that once contained the width and height now contained a series of characters. The fix involves replacing the line: ...with: In the RT copy of dcraw this is line 6661 of dcraw.c and line 6685 of dcraw.cc. I've built RT on windows and it works. I also successfully opened a sample X-Pro2 RAF. Can someone else try it out? Cheers! P.S, here's the full email from Dave:
|
I'll try it |
RawTherapee crashes when trying to open the edit window with a Fuji X-E2 RAF file. This problem is for files from a Fuji X-E2 with the v4.0 firmware applied. I have confirmed that RawTherapee does not crash when opening a Fuji X-E2 RAF file from and X-E2 with the previous (v3) firmware applied.
This was tested on Windows 10 64 bit on RawTherapee 4.2.699
The text was updated successfully, but these errors were encountered: