Am Samstag, 3. Mai 2014, 14:05:39 schrieb Dan Torop: > Hi All, Hi.
> Apologies for a hiatus on x-trans work.The good news is the x-trans > branch works pretty well. Perhaps all too well, as I've not had urgency > to get back to work on it. But there are a bunch of things which still > need work: That's good news. [...] > - have heard bug reports from others, not least including issues with > 32 bit builds and rotated X-Pro 1 files -- am now looking into these, > and would be happy to hear more > > - Markesteijn demosaic operates on integer, not float, data (as it is > directly lifted from dcraw) -- though converting it to float would make > it harder to keep it in sync with any future dcraw development > > - Markesteijn demosaic also has lots of extra code from dcraw to make a > mid-processing conversion to Lab -- it may be possible to use extant > Darktable code here. Let's discuss these on IRC, I guess Jo (hanatos) has some ideas. > - more optimizations (OpenMP, SSE, OpenCL) These can come later. > - cacorrect module still is disabled for x-trans sensors Also something that doesn't need to work from the first commit. > - design decisions I made may be flawed, especially setting up the > UI/parameters for x-trans in the demosaic iop We will see ... > If there's a good time to catch any Darktable developers on IRC, it > would be great -- for thoughts on implementation and ideally what it > would take to get them useful/usable code. European afternoon/evening should be best. > If the update to LibRaw v. 0.16.0 would be of separate interest, I'm > happy to put it into a pull request without any x-trans code. I've > tested that code with both x-trans and Bayer files. The down side is > that to use LibRaw's new API, the code temporarily allocates 4x more > data per image (four uint16_t per pixel as opposed to only one in > current set-up). There may be a way around this, but it would require > either using LibRaw's C++ API or copying in and modifying a bunch of > LibRaw's code. As most images don't come in through LibRaw, perhaps > this is still a worthwhile change, and could lay the groundwork for > potential x-trans code? So you based your work on libraw? I guess for the moment that is ok. Most work probably went into our code I guess, so changing the input over to rawspeed once that supports X-Trans shouldn't be much work? > Best, > > Dan Tobias [...] ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
