On 3 Mrz., 19:26, Pablo d'Angelo <pablo.dang...@web.de> wrote: > Am 03.03.2011 18:34, schrieb kfj: > > > Hmmm... I'm very much in two minds about features like this. I feel > > that image processing functionality should be kept out of hugin. Of > > course we need to align the images photometrically, but manually > > finetuning the white balance is close to where I'd draw the border.
I'd draw the border here. I mean it's a borderline case - it's just about still okay, but not much further, that's what I mean. > I don't think so. Its basically a free lunch, and one that makes > technically sense, too. There are a lot of things that would make sense technically, like RAW processing, better masking, integrated tca correction, shared memory for the processes in the toolchain - to name just a few I can think of. But just throwing in a new free lunch feature without documentation for everyone to figure out how it works by trial and error isn't what I consider good style. For example, it took me quite a while to figure out that to see any effect of the grey picker at all, I had to remove the 'photometric' check mark in the preview. It looks a bit like a quick shot to me. > Having to fix 8 bit images with a second application of a "curves tool" > will degrade the image quality, if 8 bit images are used. I agree, and, sadly, 16bit isn't yet an option for everyone and increases processing time and memory use considerably. The resulting degradation from successive processing steps may become quite noticable. So there's another good feature waiting: how about an option to convert to 16 bit on input and/or convert to 8 bit on output? Or am I missing something here? When I process my 16bit TIFFs with hugin, I'd quite like to be able to get 8bit TIFF out, but it seems like I can only store in 16bit. > Second, I haven't found any free image processing application performs > white balancing as good as hugin. That said, a gimp or other plugin with > the same algorithm would be nice ;-) You seem to imply that hugin uses a special white balacing algorithm. I always thought white balance was merely putting a linear scaling factor on the magnitudes of the red and blue channel compared to green. Can you point me to someplace explaining the technicalities of hugin's white balancing algorithm so I can find out about it's special properties? And, while asking for documentation, is the openGL preview considering the colour profile of the monitor, and does it do so an all platforms, be it via the OS or by itself? Otherwise white balancing would merely make the image look nice on that particular screen in the hugin preview. Kay -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
