HiAs I know, there is some problem about the pfm file.so how to use normal
image to use darkfable?Can I just use imagemagick to convert to pfm?So far,
that pfm have problem to read at noiseprofile.c
BRSY
-------- Original message --------
From: [email protected]
Date: 2015/05/23 12:25 am (GMT+09:00)
To: [email protected]
Subject: darktable-devel Digest, Vol 68, Issue 20
Send darktable-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/darktable-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of darktable-devel digest..."
Today's Topics:
1. Importing Images (David Vincent-Jones)
2. Re: Add support for big-endian pfm images. (Taahir Ahmed)
3. Re: Add support for big-endian pfm images. (Tobias Ellinghaus)
4. Function labels and darktable images from digikam? (Carlos Mart?n)
5. lua script to print contact sheets (Matthias Bodenbinder)
6. Re: Function labels and darktable images from digikam?
(Ariel Kanterewicz)
----------------------------------------------------------------------
Message: 1
Date: Thu, 21 May 2015 14:16:43 +0200
From: David Vincent-Jones <[email protected]>
Subject: [darktable-devel] Importing Images
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Trying to import individual images directly from my camera (Fuji X100S) fails.
dt simply locks-up and subsequently closes.
Not sure if this is a dt problem or again related to gphoto.
Normal import of a folder works just fine.
darktable 1.7.0.1432065804.ee1ec86
David
------------------------------
Message: 2
Date: Thu, 21 May 2015 16:01:10 -0500
From: Taahir Ahmed <[email protected]>
Subject: Re: [darktable-devel] Add support for big-endian pfm images.
To: [email protected]
Message-ID: <13400068.6yPaRXNGeU@basis>
Content-Type: text/plain; charset="us-ascii"
Looks good. I've tested it on big- and little-endian images, and both
load fine. Some comments:
1) This was missing from my original commit, but the pfm export code
at src/imageio/format/pfm.c also needs a similar treatment. It
always exports as little-endian, which is fine, but it needs to
ensure that the exported data is actually little-endian.
2) You use a variable 'cols' to describe the number of channels in the
image. Given that the number of columns in the image is actually
stored in img->width, it may be better to change the name of 'cols'
to something like 'chans'.
3) The branches for 3 channels and one channel are needlessly
different. If you pulled out the fread call, you could write it
like this and it would suffice for both branches:
ret = fread(buf, chans*sizeof(float), (size_t)(img->width * img->height),
f);
if(ret != img->width * img->height)
goto error_corrupt;
This also has the advantage of reporting truncated files as
corrupt, whereas the current code will return an image with the
truncated region uninitialized.
4) There is no need for the loop on line 67 to run backwards, nor for
there to be two separate loops on lines 77 and 78.
Thanks for getting this support landed.
Taahir
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part.
------------------------------
Message: 3
Date: Fri, 22 May 2015 11:07:02 +0200
From: Tobias Ellinghaus <[email protected]>
Subject: Re: [darktable-devel] Add support for big-endian pfm images.
To: [email protected]
Message-ID: <1994661.ZKUoqkxlgu@liber>
Content-Type: text/plain; charset="us-ascii"
Am Donnerstag, 21. Mai 2015, 16:01:10 schrieb Taahir Ahmed:
> Looks good. I've tested it on big- and little-endian images, and both
> load fine. Some comments:
>
> 1) This was missing from my original commit, but the pfm export code
> at src/imageio/format/pfm.c also needs a similar treatment. It
> always exports as little-endian, which is fine, but it needs to
> ensure that the exported data is actually little-endian.
It is.
> 2) You use a variable 'cols' to describe the number of channels in the
> image. Given that the number of columns in the image is actually
> stored in img->width, it may be better to change the name of 'cols'
> to something like 'chans'.
That is just a variable name (and it was there before). No need to mess with
the code for that.
> 3) The branches for 3 channels and one channel are needlessly
> different. If you pulled out the fread call, you could write it
> like this and it would suffice for both branches:
>
> ret = fread(buf, chans*sizeof(float), (size_t)(img->width *
> img->height), f); if(ret != img->width * img->height)
> goto error_corrupt;
>
> This also has the advantage of reporting truncated files as
> corrupt, whereas the current code will return an image with the
> truncated region uninitialized.
Yes, could be done. I don't think anyone cares though. Convincing Jo to add
big endian support was hard enough. It's not like you download PFM files from
the Internet. These are used in a workflow to move pixel data from one
application to another.
> 4) There is no need for the loop on line 67 to run backwards, nor for
Yes, there is. If it ran forward we would overwrite our data. Read the code
again and try to understand what it does.
***** Spoiler ahead *****
The image has 3 channels, darktable uses 4.
> there to be two separate loops on lines 77 and 78.
Sure, it can be turned into a single loop, but that would make the code inside
harder to read, and chances are good that the compiler will take care of them.
> Thanks for getting this support landed.
>
> Taahir
Tobias
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
------------------------------
Message: 4
Date: Fri, 22 May 2015 15:59:24 +0200
From: Carlos Mart?n <[email protected]>
Subject: [darktable-devel] Function labels and darktable images from
digikam?
To: [email protected]
Message-ID:
<CABCDMEipe3eH+ENuBSSaN2XXY=-VFcT=nbgpu-vo3mpfpyq...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Digikam use to organize my images (labels, scores)
When I imported darktable folders, labels did not appear in the image
metadata.
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 5
Date: Fri, 22 May 2015 17:09:08 +0200
From: Matthias Bodenbinder <[email protected]>
Subject: [darktable-devel] lua script to print contact sheets
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hi,
triggered by a question on the user list I created a lua script which creates a
contact sheet (Kontaktabzug) for a set of JPGs. The output is a PDF document.
The script uses lualatex to do the job. How do I incorporate that script into
darktable?
The script works pretty well on the commandline. You can try it out. It is
attached below. Just say
do_contactsheet.lua /path/to/pictures/*.jpg
/path/to/otherpictures/*.png
This will create a contactsheet.pdf in the current directory. With optional
commandline parameters --title and --count you can set a different document
title and a different number of pictures per line (default is 4)
What I would like to do is:
- include it into darktable to excecute it for the current film roll
- set the title to the name of the film roll
- retrieve all JPGs/PNGs from the current export directory and create
the contactsheet.pdf in that directory
- call the pdf viewer when the script is finished (how to determine the
default pdf viewer?)
- eventually allow the user to set the "count" parameter to a different
value
- eventually allow the user to set the "title" parameter to a different
value
I need some help to get there. I dont know how to retrieve the internal
darktable parameters, like the current filmroll, nor do I now how to interact
with the user in darktable.
Your advice is appreciated
Matthias
Here is the script:
-------------------
#!/usr/bin/lua
-- do_contactsheet.lua creates a contact sheet (Kontakabzug) for a set of
pictures
-- it uses LaTeX to create a PDF document
-- it supports JPG and PNG files
-- (c) Matthias Bodenbinder, May 2015
-- default values
title = "Kontaktabz?ge"
thumbs_per_line = 4
-- LaTeX preamble
tex_start="\\documentclass[a4paper,10pt]{article}\
\\usepackage{graphicx}\
\\usepackage{fontspec}\
\\pagestyle{empty}\
\\parindent0pt\
\\parskip1em\
\\usepackage{geometry}\
\\geometry{a4paper,left=5mm,right=5mm, top=5mm, bottom=5mm}\
\\begin{document}"
-- place a thumbnail
function thumbnail(i,f)
-- i = number of this picture
-- f = fullpath to picture
-- remove leading path to retrieve filename
label = string.gsub(f, ".*/", "")
-- print thumbnail in minipage
return "\\begin{minipage}[b]{" .. w .. "\\textwidth}\n" ..
" \\includegraphics[width=\\textwidth]{" .. f .. "}\\newline\n" ..
" \\centering{\\verb|" .. i .. ": " .. label .. "|}\n" ..
"\\end{minipage}\n"
end
-- print usage message
function usage()
print("Usage: " .. arg[0] .. " --title <title> --count <thumbs per
line> <pictures jpg/png>")
end
-- main loop
-- check for lualatex and exit if it does not exist
if( not os.execute("which lualatex >/dev/null") )then
print("lualatex not found. Aborting!")
os.exit()
end
pictures = ""
pcount = 0
i = 1
-- width of a single picture
w = 1/thumbs_per_line - 0.01;
while i<=#arg do
if (arg[i] == "--title" or arg[i] == "-t") then
-- next arg is the title
title = arg[i+1]
-- go to next picture
i=i+2
elseif (arg[i] == "--count" or arg[i] == "-c") then
-- next arg is thumbs per line
thumbs_per_line = arg[i+1]
-- calculate new picture width
w = 1/thumbs_per_line - 0.01;
-- go to next picture
i=i+2
elseif (arg[i] == "--help" or arg[i] == "-h") then
usage()
os.exit()
else
pcount=pcount+1;
pictures = pictures .. thumbnail(pcount, arg[i])
i=i+1
if( pcount % thumbs_per_line == 0 ) then
-- enough pictures in one line =>
pictures = pictures .. "\\par\n"
else
pictures = pictures .. "\\hspace{1mm}\n"
end
end
end
-- write tex file to /tmp
basefile = "/tmp/contactsheet"
texfile = basefile .. ".tex"
pdffile = basefile .. ".pdf"
f = io.output(texfile, "w")
io.write(tex_start)
io.write("{\\Large\\bfseries " .. title .. "}\\par\n")
io.write(pictures)
io.write("\\end{document}")
io.close()
-- execute lualatex to create pdf file
os.execute("cd /tmp; lualatex " .. texfile)
-- move pdf to current folder
if( not os.execute("mv " .. pdffile .. " .") ) then
print("file does not exist: " .. pdffile)
end
------------------------------
Message: 6
Date: Fri, 22 May 2015 15:24:54 +0000
From: Ariel Kanterewicz <[email protected]>
Subject: Re: [darktable-devel] Function labels and darktable images
from digikam?
To: Carlos Mart?n <[email protected]>,
[email protected]
Message-ID:
<CACYHze-Uydf=6g84njngbu84kh3ihawp2sbcrndudbdma-p...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Digikam saves info into a central database, as far as I know. There should
be a way to make it save that information into individual XMP files, which
darktable can read. (DT understanding those XMP is a different story, I
wouldn't know about that)
On Fri, May 22, 2015 at 11:01 AM Carlos Mart?n <[email protected]> wrote:
> Digikam use to organize my images (labels, scores)
> When I imported darktable folders, labels did not appear in the image
> metadata.
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> darktable-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
------------------------------
_______________________________________________
darktable-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel
End of darktable-devel Digest, Vol 68, Issue 20
***********************************************
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
darktable-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel
