On Thu, Dec 1, 2016 at 3:33 PM, Jimmy Gowrisanker <seekjim...@gmail.com> wrote:
> I did a git clone to /home/jimmy folder and then coped extract_wb to the
> ~/darktable ....but I had to change a line (path) to
> CAMERAS=File.expand_path("../darktable/src/external/rawspeed/data/cameras.xml",
> File.dirname(__FILE__)) as path
> "../src/external/rawspeed/data/cameras.xml" gave me errors.

After cloning, just run

$ path/to/clone/of/darktable/tools/extract_wb  files

> Attached is the text file.
>
> I currently have 2.2rc1 installed from git and I will try to follow Robert's
> instructions for building into 2.2rc1.
>
> Regards
> Jimmy
> 972-755-1244
> seekjim...@gmail.com
> www.Capture2Sell.com
>
> On Thu, Dec 1, 2016 at 5:27 AM, Roman Lebedev <lebedev...@gmail.com> wrote:
>>
>> On Thu, Dec 1, 2016 at 2:24 PM, Robert William Hutton
>> <r...@helms-deep.net> wrote:
>> > On 01/12/16 21:51, Roman Lebedev wrote:
>> >>
>> >> On Thu, Dec 1, 2016 at 2:55 AM, Robert William Hutton
>> >>>>>
>> >>>>> for file in *; do ~/wd/darktable/tools/extract_wb "$file" >>
>> >>>>> ~/white_balance.txt ; echo >> ~/white_balance.txt ; done
>> >>
>> >>
>> >> Uh, oh, s/is the tool/can work on multiple raw files at once, no need
>> >> to call it in a loop/
>> >
>> >
>> > Ah, the reason I called it in a loop was so that I could get a blank
>> > line
>> > between the output for each image with the echo >> ~/white_balance.txt.
>> > This is because the script gave me multiple lines of output for each
>> > file,
>> > and I had to go and sort out which line I wanted to keep.  E.g.:
>> >
>> >
>> > $ ~/wd/darktable/tools/extract_wb IMG_2130.CR2 2> /dev/null
>> >   { "Canon", "PowerShot G7 X", Daylight        , 0, {
>> > 1.7831603229527104, 1,
>> > 2.1199538638985005, 0 } },
>> >   { "Canon", "PowerShot G7 X", Daylight        , 0, {
>> > 2.1252847380410023, 1,
>> > 1.703872437357631, 0 } },
>> >   { "Canon", "PowerShot G7 X", Shade           , 0, {
>> > 2.4133180252583237, 1,
>> > 1.4638346727898968, 0 } },
>> >   { "Canon", "PowerShot G7 X", Cloudy          , 0, {
>> > 2.2782212086659066, 1,
>> > 1.5530216647662485, 0 } },
>> >   { "Canon", "PowerShot G7 X", Tungsten        , 0, {
>> > 1.4674285714285715, 1,
>> > 2.7302857142857144, 0 } },
>> >   { "Canon", "PowerShot G7 X", WhiteFluorescent, 0, {
>> > 2.0830188679245283, 1,
>> > 2.3559748427672957, 0 } },
>> >   { "Canon", "PowerShot G7 X", Flash           , 0, {
>> > 2.5853658536585367, 1,
>> > 1.3612078977932636, 0 } },
>> >
>> >
>> > Note that in that output there is two daylight lines... The first is the
>> > value I want, shot at -9 on the blue/amber axis, the second is the value
>> > for
>> > 0 on the blue/amber axis, and the following ones are also for 0 on the
>> > blue/amber axis for the other presets.  So I had to go delete all the
>> > spurious lines and change the number from 0 to -9, and so on for all the
>> > other files.  Having the blank line in between just made this less
>> > confusing.
>> Yeah, it does not do anything wrt blue/amber axis tune values.
>>
>> > Worth filing bug reports for this stuff?
>> Yes, and please provide a few shots to debug this on.
>> E.g. Daylight -9; 0; 9
>>
>> > -R
>> Roman.
>>
>> >
>> > ____________________________________________________________________________
>> > darktable user mailing list
>> > to unsubscribe send a mail to
>> > darktable-user+unsubscr...@lists.darktable.org
>> >
>>
>> ____________________________________________________________________________
>> darktable user mailing list
>> to unsubscribe send a mail to
>> darktable-user+unsubscr...@lists.darktable.org
>>
>
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Reply via email to