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.
Worth filing bug reports for this stuff?
-R
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
