Hi Klaus,

That is very exciting about a RawSpeed with all that Fuji support. When
you feel good about the source code, I'd be happy to try it out in an
x-trans branch.

Best,
Dan


On Wed, Feb 5, 2014, at 03:36 AM, Klaus Post wrote:
> Hi!
> 
> >>That would be interesting if RawSpeed ends up supporting Fuji
sensors..
> 
> I have a version that supports Fuji (including X-trans). I actually only miss 
> camera definitions and documentation, and a bit more testing to feel 
> comfortable. Also, I will have a final look through the interface to make 
> sure it makes sense and will not break to easily.
> 

> 
> Importing it into darktable shouldn't be a big deal - only a few files to be 
> added to the build system, though I am not sure I would add it to "stable" 
> releases - I like being conservative.

> 
> 
> If the image is "pre-xtrans", it will return 45 degree rotated images. Xtrans 
> is of course returned un-rotated.
> 
> As with other formats, it doesn't do any de-mosaic or transformation other 
> that value scaling.
> 

> 
> I can fairly soon do a drop, which adds the support, which will probably be 
> disabled by default. 
> 
> As a side-note, it also supports Sigma sensors - however, since RawSpeed 
> doesn't do any of the work that "foveon_interpolate"  does in dcraw, it might 
> be a bit more tricky to implement. However, I don't think color interpolation 
> belongs in a decoder. On the plus side the Sigma decoder should be 
> considerably faster.
> 

> 
> Regards, Klaus
> 
>  
> 
> Regards, Klaus Post
> 
> http://www.klauspost.com 
> 
> 
> 
> On Tue, Feb 4, 2014 at 9:12 PM, Dan Torop <d...@pnym.net> wrote:
>> 

Thank you both for all the thoughts...
>> 
>> 
>> 
There's a fork at https://github.com/dtorop/darktable with a branch
>> 
"xtrans2" with the changes so far, bundled into a few commits.
>> 
>> 
>> 
Misc. notes
>> 
>> 
>> 
- I haven't tested if the switch to LibRaw 0.16.0 breaks other things.
>> 
>> 
>> 
- That would be interesting if RawSpeed ends up supporting Fuji
>> 
sensors... As the LibRaw loading seems functional now, that could still
>> 
be a starting point for the rest of the work?
>> 
>> 
>> 
- Right now "filters" in image_ t is overloaded to differentiate Bayer
>> 
from X-Trans mosaics. If "filters" is 9 (an arbitrary magic number from
>> 
dcraw), the mosaic layout is in "xtrans", not "filters". Would it be
>> 
better to have a flag to specify if the image has a Bayer or X-Trans
>> 
mosaic? Not to bloat the image_t even more...
>> 
>> 
>> 
- The in-progress demosaic code uses linear interpolation modified from
>> 
dcraw (a slight improvement from the grayscale code I mentioned
>> 
yesterday). The mosaic is visible in the 1:1 view, though, perhaps from
>> 
an roi offsetting mistake on my part.
>> 
>> 
>> 
- The in-progress fast clip/zoom code is totally off, a quick/flawed
>> 
rehash of existing DT code.
>> 
>> 
>> 
The point about maintenance of code not used by core devs seems really
>> 
key... Still am glad if any of this so far is of use. Am happy to hear
>> 
further thoughts, and I'll hope to improve this.
>> 
>> 
>> 
Thank you,
>> 
Dan
>> 
>> 
>> 
>> 
>> 
>> 
On Tue, Feb 4, 2014, at 05:43 AM, Tobias Ellinghaus wrote:
>> 
> Am Dienstag, 4. Februar 2014, 10:08:24 schrieb johannes hanika:
>> 
>
>> 
> [...]
>> 
>
>> 
> > > - A potential patch could be pretty invasive -- not just requiring the
>> 
> > > LibRaw upgrade
>> 
> >
>> 
> > that's great, we should have done that earlier i guess.
>> 
>
>> 
> AFAIK there is ongoing work to support some of these Fuji sensors in
>> 
> rawspeed,
>> 
> so maybe it would be better to wait for that update and ignore libraw.
>> 
> That
>> 
> part is going to die as soon as possible anyway.
>> 
>
>> 
> [...]
>> 
>
>> 
> Tobias
>> 
>> > ------------------------------------------------------------------------------
>> 
> Managing the Performance of Cloud-Based Applications
>> 
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
>> 
> Read the Whitepaper.
>> 
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
>> 
> _______________________________________________
>> 
> darktable-devel mailing list
>> 
> darktable-devel@lists.sourceforge.net
>> 
> https://lists.sourceforge.net/lists/listinfo/darktable-devel
>> 
>> > Email had 1 attachment:
>> 
> + signature.asc
>> 
>   1k (application/pgp-signature)
>> 
>> 
>> 
>> 
------------------------------------------------------------------------------
>> 
Managing the Performance of Cloud-Based Applications
>> 
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
>> 
Read the Whitepaper.
>> 
>> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
>> 
_______________________________________________
>> 
darktable-devel mailing list
>> 
>> darktable-devel@lists.sourceforge.net
>> 
>> https://lists.sourceforge.net/lists/listinfo/darktable-devel
>> 
> 
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
> _________________________________________________
> darktable-devel mailing list
> darktable-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/darktable-devel

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel

Reply via email to