![]() ![]() ![]() I agree with you about the appreciation of the work they are doing. I probably should get back on C++ to help with a few bugs, have been mostly on web devevelopment for quite a while. That is a great community with many volunteer to do what they can. My first thought was, what the heck are the devs doing and not adding support for a new camera with simple updates, and then I checked the list of commits on github just to see a lot of activities are going there (culling feature, prepping for 2.8 release, Lumix LX100M2 noise profile, translations. Somehow that sentence made me appreciate the darktable project a lot more. Meanwhile I could develop the portrait from the OP using Affinity Photo Meanwhile I could develop the portrait from the OP using Affinity Photo:Ī6600 raw file from DPR Gallery developed in Affinity Photo 1.7.2. The fact that darktable can't open it is connected with the way dt support new cameras (there are historic reasons at play here - they chose RawSpeed as their library at some point in time and now they need submissions from users - so far nobody has submitted their a6600 raw file to the repository at so dt refuses to open it). It's interesting that MakerNotes say that the model release year for the a6600 is 2018 Black level and White level are also exactly the same as in a6400, and that also applies to the Color Matrix info. Last season I almost bought a Fujifilm X-T100 with Bayer sensor.ĮxifTool v.11.63 reports that the raw file you linked to in your OP has file format ARW 2.3.5 (14-bit Sony ARW compressed), which is exactly the same as the format used by a6400. I agree, X-Trans is silly with >= 24Mp sensors. With Fujifilm, I was able to make a link from X-T30 back to X-T3 and had no problems editing RAF from the newer model. The a6600 has essentially the same specs as previous Sony a6* models, so I don't see why it needs to have an incompatible Raw format. If you're going to avoid any manufacturer on the basis of RAW support, boycott Fuji (X-Trans) and Sigma (Foveon), as they use sensors which don't support standard demosaicing algorithms. This isn't a unique issue with Sony, nor is it unique to Darktable, it applies to all manufacturers and all RAW converters. This is why you never see RAW processed shots in newly released camera reviews, they have to be SooC JPEG because nothing on the market can process the new RAW files. The only thing that varies is the amount of pre-release information the manufacturers give out. It doesn't matter whether it's Canon, Nikon, Fuji, or Sony. Why can't Sony maintain ARW compatibility? Camera white balance is not rocket science.Īs I've already explained, each time a new camera comes out, a new build of RAW converter is required to open those RAW files. My solution is to avoid buying the Sony a6600. Thanks for the news about darktable 2.7 and a6600 support. We should expect the new release of the Converter pretty soon, I think. DPR have access to a new beta release of the DNG Converter so they could process the raw files from a6600. The DNG Converter 11.4 doesn't accept a6600 yet, so they can't get the matrix for input profiles for dt or RT. a6400 arw files can be opened now with the development build of dt 2.7 but it still doesn't support a6600 arw's. I couldn't open a6400 arw files in dt 2.6.2 but when I converted them to DNG with the Adobe DNG Converter, 2.6.2 opened them (because the DNG has an embedded input matrix profile). This is where DNG was supposed to help, but my experience is that even Adobe's own software can't open new camera DNG files until you update the converter.Ī similar issue was reported months ago, and the workaround was maybe "convert to DNG" although the bug comments are difficult for me to interpret. The -w flag means use camera white balance! The dcraw -w command is able to convert the ARW file also, but both it and RawTherapee make it look overexposed. I wouldn't expect Darktable to open it yet, and I'm surprised that RawTherapee can. Generally speaking most raw converters can't handle new cameras until the software is updated to do so. Darktable 2.6.2 complains that it cannot read the camera white balance and says "working" until program exit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |