On Tue, Jul 26, 2016 at 9:35 PM, Jonathan Pittman <jonathan.mark.pitt...@gmail.com> wrote: > Figuring out how to handle this problem for one specific camera's raw files > is not too difficult. Figuring out how to do this to handle the majority of > cases requires a bit more work.
I know libraw has its issues (and lots of them), and I completely understand wanting a native Go way to get raw data, but I highly recommend that you don't. There's absolutely no standard for raw image file formats (most of them are slightly-off-standard variants of TIFF with various silly transformations applied to the metadata for no reason) between camera vendors, or even between different models made by specific cameras. You'll be wasting a lot of time and effort trying to duplicate the work that libraw has already done for you (and done well). Instead, consider contributing to libraw if you see cameras that it doesn't support. That being said, if you wanted to talk about processing raw bayer data without using cgo, I'd say go for it! Use libraw to actually extract the data, then do the image manipulation itself in Go instead of using libraws dcraw emulation layer. I'm one of the authors of RawKit (https://rawkit.readthedocs.io/en/latest/), a Python library for photo manipulation that ships with libraw ctype bindings, and this is the approach we will eventually take (although we'll most likely be doing the photo manipulation in Rust, the raw extraction with libraw, and just writing Python bindings for both). —Sam -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
