That confirms that my preliminary patch was correct, merged it.
Question to myself: why it didn't crash for me? why didn't i catch this
initially?
On Tue, Mar 4, 2014 at 2:48 AM, Paul Greindl wrote:
> OK, I've rebuilt DT setting the options "debug" and "!strip" plus added
>
> export CFLAGS="$CF
It doesn't look like it. I usually work with DNG files, and it reads them
fine, but by mistake I took a bunch of PEF shots and found it couldn't read
them. I suspect it isn't a priority since the DNG code works fine. No
complaint, the developer's time is valuable.
On Mon, Mar 3, 2014 at 9:31 PM,
Hi, Derek. Has dt gained the ability to parse the reformatted PEF raw
files from the K-3 yet? I know the devs were working on this but hadn't
heard that they had succeeded. Ricoh messed around with the PEF format
quite a bit.
Jack
On 14-03-03 08:47 PM, Derek Kite wrote:
> I'm certain this has
Francisco - ptrace is not installed by default in Ubuntu 13.10. Looks
like you will need to install it as I had to do :)
Jack
On 14-03-03 06:48 PM, Francisco Cribari wrote:
> I run the unstable version of Darktable (from Pascal's PPA): Version
> 1.4.1+68~ga0e146a. My OS is Ubuntu Gnome 13.10 64
I'm certain this has worked before, but I can't open PEF raw files. Below
is the output from the terminal when I run Darktable.
I'm running 1.5+483~g04771e3, from git. Built a few moments ago.
Oddly I can't open with Rawtherapee either, so it could be a system
library. I'm running debian unstable
I run the unstable version of Darktable (from Pascal's PPA): Version
1.4.1+68~ga0e146a. My OS is Ubuntu Gnome 13.10 64 bit. Dartable crashes
when I try to import a folder of Nikon RAW files. That happens with kernels
Linux darwin3 3.12.6-031206-generic #201312201218 SMP Fri Dec 20 17:20:06
UTC 201
Using the Monochrome module I note that there is only an very minimal
darkening of the sky using the 'red filter' preset (certainly nothing
like the expected effect that would be found with film). Even when the
target circle is reduced to its smallest size and moved to the corner of
the red qua
Of course. Here it is.
On 2014-03-04 00:35, Tobias Ellinghaus wrote:
Am Montag, 3. März 2014, 23:48:34 schrieb Paul Greindl:
OK, I've rebuilt DT setting the options "debug" and "!strip" plus added
export CFLAGS="$CFLAGS -O0 -fbuiltin -g"
export CXXFLAGS="$CXXFLAGS -O0 -fbuiltin -g"
as build
Am Montag, 3. März 2014, 23:48:34 schrieb Paul Greindl:
> OK, I've rebuilt DT setting the options "debug" and "!strip" plus added
>
> export CFLAGS="$CFLAGS -O0 -fbuiltin -g"
> export CXXFLAGS="$CXXFLAGS -O0 -fbuiltin -g"
>
> as build flags. Hope that's correct :)
Way better. Could we also get
/
I currently have around 150 GB of photos that are in a mix of .NEF and .DNG
from two different cameras. I am now attempting to migrate from Lightroom to
Darktable.
I seem to be able to import the .NEF into darktable with Lightroom settings
getting passed through. The DNGs are causing me some tr
Hi,
gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
http://pastebin.com/mFELmutm
Removing build folder and launching build.sh script didn't change anything.
Bye !
2014-03-03 23:07 GMT+01:00 Tobias Ellinghaus :
> Am Montag, 3. März 2014, 22:20:30 schrieb Victor L:
> > Hello,
>
> Hi.
>
> > When I t
OK, I've rebuilt DT setting the options "debug" and "!strip" plus added
export CFLAGS="$CFLAGS -O0 -fbuiltin -g"
export CXXFLAGS="$CXXFLAGS -O0 -fbuiltin -g"
as build flags. Hope that's correct :)
Attaching the new file.
On 2014-03-03 20:51, Tobias Ellinghaus wrote:
Am Montag, 3. März 2014, 2
Am Montag, 3. März 2014, 22:20:30 schrieb Victor L:
> Hello,
Hi.
> When I try to build darktable from the latest github I get this :
>
> Scanning dependencies of target channelmixer
> [ 76%] Building C object
> src/iop/CMakeFiles/channelmixer.dir/introspection_channelmixer.c.o
> /home/victor/dar
Hello,
When I try to build darktable from the latest github I get this :
Scanning dependencies of target channelmixer
[ 76%] Building C object
src/iop/CMakeFiles/channelmixer.dir/introspection_channelmixer.c.o
/home/victor/darktable/build/src/iop/introspection_bilateral.cc:28:5:
error: expected p
On 2014-03-03 ellest...@ninedegreesbelow.com wrote:
> The profile file name isn't actually part of the ICC profile, so that
> information isn't embedded in an image when you embed the ICC profile.
>
> The description tag (and model tag and so on) carries verbally
> identifying information.
Ah,
Am Montag, 3. März 2014, 20:25:18 schrieb Paul Greindl:
> This should of course go to the list as well, sorry!
>
> Hi, here's the file I got.
It seems your version of darktable is stripped. Can you install debug symbols,
too, and then recreate the gdb file?
Tobias
> On 2014-03-03 17:05, Tobias
Hi.
Can you please build this branch and check if it is still reproducible
there?
https://github.com/LebedevRI/darktable/tree/fix-exif-crash
On Mon, Mar 3, 2014 at 11:25 PM, Paul Greindl wrote:
> This should of course go to the list as well, sorry!
>
> Hi, here's the file I got.
>
>
>
> On 201
This should of course go to the list as well, sorry!
Hi, here's the file I got.
On 2014-03-03 17:05, Tobias Ellinghaus wrote:
Am Montag, 3. März 2014, 14:32:51 schrieb Paul Greindl:
Hi!
As of some days ago I'm getting a segfault on importing images in
Darktable-git (from the AUR) running on
On 03/03/2014 12:54 PM, junkyardspar...@yepmail.net wrote:
> On 2014-03-03 be...@judiz.de wrote:
>
>> I understand the licencing issue, but it would be great
>> if the oss tools would agree on one version of sRGB.
It would be nice if they all would agree on one version of sRGB, as long
as it was
On 03/03/2014 10:52 AM, Tobias Ellinghaus wrote:
> Am Montag, 3. März 2014, 10:30:21 schrieb Rich:
>> I'm using a profiled display and I believed that Darktable was writing
>> sRGB jpegs, but it turns out it's writing "Darktable sRGB".
>>
>> When using one of these images on Blogger for my photogra
Am Montag, 3. März 2014, 09:54:19 schrieb junkyardspar...@yepmail.net:
> On 2014-03-03 be...@judiz.de wrote:
> > I understand the licencing issue, but it would be great if the oss tools
> > would agree on one version of sRGB.
> I agree, it makes darktable>gimp workflows a little bit annoying. It se
On 2014-03-03 be...@judiz.de wrote:
> I understand the licencing issue, but it would be great if the oss tools
> would agree on one version of sRGB.
I agree, it makes darktable>gimp workflows a little bit annoying. It seems like
hugin might be a little confused by the profile name, too, althoug
Am Montag, 3. März 2014, 17:50:18 schrieb Michael Below:
> Hi,
Hi.
> I have noticed that gimp has a different concept of sRGB, upon import it
> asks me if I want to convert to its version of sRGB, and that conversion
> causes changes especially in lightness.
>
> I understand the licencing issue,
Hi,
I have noticed that gimp has a different concept of sRGB, upon import it asks
me if I want to convert to its version of sRGB, and that conversion causes
changes especially in lightness.
I understand the licencing issue, but it would be great if the oss tools would
agree on one version of sR
Am Montag, 3. März 2014, 14:32:51 schrieb Paul Greindl:
> Hi!
>
> As of some days ago I'm getting a segfault on importing images in
> Darktable-git (from the AUR) running on Arch.
>
> Launching darktable from the console gives the following output:
>
> /[paul@vostro ~]$ darktable/
> /ptr
Am Montag, 3. März 2014, 10:30:21 schrieb Rich:
> Hi
Hi.
> I'm using a profiled display and I believed that Darktable was writing
> sRGB jpegs, but it turns out it's writing "Darktable sRGB".
>
> When using one of these images on Blogger for my photography blog, the
> colours go very wrong.
>
>
Hi!
As of some days ago I'm getting a segfault on importing images in
Darktable-git (from the AUR) running on Arch.
Launching darktable from the console gives the following output:
/[paul@vostro ~]$ darktable/
/ptrace: Operation not permitted./
//home/paul/8169: No such file or direc
> My suggestion on the user interface side would be :
> * in the "keep one-shot auto result" case, uncheck the "auto" checkbox.
> * in the "re-apply auto" case, keep the "auto" checkbox checked
> (This refers to the auto-exposure UI.)
Re-reading this message, I see possibility of reading it wrong
Hi
I'm using a profiled display and I believed that Darktable was writing
sRGB jpegs, but it turns out it's writing "Darktable sRGB".
When using one of these images on Blogger for my photography blog, the
colours go very wrong.
I expect that Blogger is completely ignoring the colour profile
Le 01/03/2014 19:15, Gonçalo Marrafa a écrit :
> Hi.
>
> I have a question about copying settings between modules in the
> darkroom view.
>
> For example, if i select auto in exposure module ou spot white balance
> in white balance module or just activate the lens correction module
> and copy th
Hello,
This is related to the thread "Copy settings between modules" and
related but focused on UI.
Think "Keep the result of that particular auto-compute result" vs
"Recompute auto for each picture"
One should ask oneself, when doing copy-paste (or apply style):
* you may have applied auto (e
Hello again.
Anyone?
Atentamente,
Gonçalo Marrafa
On Sat, Mar 1, 2014 at 6:15 PM, Gonçalo Marrafa
wrote:
> Hi.
>
> I have a question about copying settings between modules in the darkroom
> view.
>
> For example, if i select auto in exposure module ou spot white balance in
> white balance mo
Am 03.03.2014 00:29, schrieb John Jumper:
> Hello,
>
> I am interested in purchasing a new GPU for my linux desktop, and
> darktable performance on ~25 MB raw files is a major consideration. Is
> there any solid benchmarking of darktable on various GPUs or any
> substantial architectural differenc
Hi John,
For darktable performance it is I think a card's OpenCL benchmark you should
be looking at primarily. If you can find a specific OPenCL float benchmark
that would be ideal but I haven't seen those published myself.
The general rule for dt is that you should have at least 1G memory o
34 matches
Mail list logo
