In this situation, what you would be developing a base curve for would be the film type (and desired effect), rather than the scanner. In fact, you may even be better off doing this in the scanner software, if you're not saving as high-bit-depth tiff files.
Cecil Carpenter <[email protected]> wrote: >I have a Nikon Coolscan V ED and use Vuescan Pro to scan 35mm negatives >as Tiffs with Color Balance set at Neutral and Scan Resolution set at >4000 dpi in Vuescan. When I process these scans in Darktable, there >are >no Base Curves for these images because the scanner obviously is not a >camera. Since I don't attempt to influence what Vuescan has read from >the film, I was wondering if it made sense to try to develop a Base >Curve for the scanner. I am a neophyte at this, so I'm on shaky ground >here. In any case, as I have thousands of images I am scanning from >years of 35mm SLR photography, an auto applied Base Curve would help >simplify my work flow. So does this make sense, is it worth pursuing, >and does anyone have any opinions as to the best way to create a Base >Curve for my situation? > ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
