It *appears* that LibRaw's normal processing sequence is to convert the mosaicked image pixel data into an intermediate (YUV?) representation, which may be manipulated for noise, etc; that in turn is converted into a picture-ready RGB (which apparently varies from the camera RGB (or camera CMY); that RGB in turn is gamma-adjusted and then formatted appropriately for the output file format.
• Is this approximately correct? Anything missing especially?
First post here. I'm very much a Newbie in RAW image work, and have only a little knowledge of C.
I run a Canon 6D with a fisheye lens that creates allsky images every 45 seconds during the night.
That's a lot of images, which I need to convert to PNG format with embedded customised metadata (not EXIF).
I program in Interactive Data Language (IDL), and have written a program to create the necessary PNG files with
embedded metadata. However the current workflow is CR2=>TIFF=>PNG which takes a lot of time and a lot of disk space!
I came across this library when searcing for possible solutions to interpolate dead or hot pixels in ML raw footage. The footage can easily be converted to dng images. I seems certain that LibRaw can read these dng files, so I might be able fix my sequence of image files. My question is, what file formats can the library write. Does LibRaw include code to write dng files?
I'm building an time-lapse app that needs to convert CR2 files (from 5DM3) as fast as possible (using some automated/predefined/default settings, i.e. no user interaction). This is Windoze app (yeah, yeah, I know...). I tried dcraw (needed to dance around for couple hours to make it work in VS2012), and then Canon's native EDSDK. Both gave me about same speed (~6 to 6.3s CR2 to TIF conversion on a pretty good machine - I7-3960, 64GB RAM, SATA3-RAID0 SDD array, etc, etc).
I have tested a lot of RAW files & formats with the new Version (0.17 alpha 1), and "nearly" everything works great. But i have a problem with the following file "1D_RAW.TIF".
Recent comments