Hi,
I suggest you have a look here:
http://www.darktable.org/usermanual/ch03s02s10.html.php
Especially see sections 3.2.10.2, 3.2.10.3, and 3.4.3.10 for a solution.
Best wishes
Ulrich
Am 25.07.2015 um 07:55 schrieb Eugene Mikhantiev:
> Hi all!
>
> I use Darktable for several years and I was v
Forgot to mention. If you have other applications which consume
significant amounts of GPU memory this could also cause OpenCL in
darktable to fail. Unfortunately there is no way to find out at any time
which amount of GPU memory is still available. Therefore darktable
assumes it can have all m
Hi,
then the only chance which I still could see is testing another driver
version, assuming that a driver might be the root cause. I am currently
successfully running version 346.59 (although my GPU is an ancient GTS450).
Ulrich
BTW here are my settings:
[opencl_init] opencl: 1
[opencl_init]
You could try an even higher values of opencl_memory_headroom of 500.
If this does not help please try with lower settings for
opencl_event_handles.
Ulrich
Am 31.05.2015 um 23:37 schrieb joeni:
> Hi,
>
> thanks. Tried that. Same, or similar, result (and I'm seeing colour
> effects where parts o
Hi,
first thing you should try is increase opencl_memory_headroom to 350 or 400.
Ulrich
Am 31.05.2015 um 14:33 schrieb joeni:
> Hi,
>
> not sure this is the right place to send this to: I'm having trouble
> with OpenCL and my new GPU (darktable 1.6.6, GeForce GT 730, Ubuntu
> 15.04). What shall
Oh yes, obviously. Will take care.
Ulrich
Am 07.04.2015 um 21:28 schrieb Pascal Obry:
>
> I think this has introduced a regression:
>
> http://www.darktable.org/redmine/issues/10410
> I can reproduce a crash reliably using the spot removal IOP and bezier
> path.
>
. do we want to keep this
> behaviour or enforce one standard rgb space?
>
> -jo
>
>
> On Thu, Mar 26, 2015 at 7:39 AM, Ulrich Pegelow
> mailto:ulrich.pege...@tongareva.de>> wrote:
>
> Hi,
>
> this is a request for comments on some changes I am
Hi,
this is a request for comments on some changes I am considering to work on.
Concretely I'd like to change the way softproofing and gamut checking
(SP/GC) is handled on the GUI side and in the pixelpipe as at the moment
they are not very convenient IMHO. And being at that I'd also like to
c
027] SELinux: initialized (dev dm-0, type ext4), uses xattr
>
>
> --
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partners
ktable with --disable-opencl as suggested in the manual.
Does the driver need to be shipped with debugging enabled? With
debugging disabled at least the assert statement will not cause the
driver to terminate.
Ulrich
--
*Ulrich Pegelow* · Benrodestraße 76 · 40597
Hi,
I took the image in this old thread as a test case for my new "color
reconstruction" module. This is what I could accomplish:
https://www.dropbox.com/s/qbjc1ol7pdh2014/_1170827_0001.jpg?dl=0
Ulrich
Am 08.04.2014 um 00:40 schrieb Moritz Moeller:
> On 7/4/14 9:51 pm, johannes hanika wrote:
>
Please have a look here:
http://www.darktable.org/usermanual/ch03s02s10.html.php
Especially sections 3.2.10.2 and 3.2.10.3.
Best wishes
Ulrich
Am 08.02.2015 um 12:07 schrieb Pascal Obry:
>
> With the following picture:
>
> https://drive.google.com/open?id=0B_w_CWtzkwW0QUVzZnVaYW82M1E&authuser
Am 09.01.2015 um 11:04 schrieb Pascal Obry:
> 2015-01-09 8:48 GMT+01:00 johannes hanika :
>> for me this is only the case with opencl, the cpu code path seems to update
>> a lot more promptly.
>
> So maybe we should add a small delay in the OpenCL path?
>
This is already done today. You can tune th
On Fri, Jan 9, 2015 at 11:48 AM, Pascal Obry <mailto:pas...@obry.net>> wrote:
>
> Le jeudi 08 janvier 2015 à 21:34 +0100, Ulrich Pegelow a écrit :
> > don't know if this has already been discussed.
> >
> > With current master all sliders have a
anika:
> maybe it has something to do with the gdk lock? not sure it still works
> as we remember it from gtk2. if i move sliders a lot, i usually get the
> attached crash (independent of slider).
>
> -jo
>
> On Fri, Jan 9, 2015 at 9:34 AM, Ulrich Pegelow
> mailto:ulrich
Hi,
don't know if this has already been discussed.
With current master all sliders have an extremely sluggish behavior.
Take a module with some demands in CPU cycles (like shadows &
highlights) and try to quickly move around one of the sliders. It's a
pain to use. In darktable-1.6.x and before
; On Sun, Jan 4, 2015 at 7:57 PM, Ulrich Pegelow
> mailto:ulrich.pege...@tongareva.de>> wrote:
>
> Hmm, could this be a race condition? In order to correctly shorten
> the label string via the ellipsize function the widget needs to be
> packed with the final size
Hi.
>
> I have finally reproduced it.
> All panels except the panel on the right needs to be expanded in order
> for it to happen (at least here, guess it migth depend on screen size)
>
> Roman.
>
> On Sat, Jan 3, 2015 at 10:53 PM, Ulrich Pegelow
> mailto:ulrich.pege...@to
Am 03.01.2015 um 20:48 schrieb Roman Lebedev:
> Hm, could you please check, is this a regression
> since f97032566a03a36b9d48f1d8e36111a6c4f3eef2 or it is reproducible
> before that commit too?
Good catch! The status preceding this commit does not show the problem.
Ulrich
---
t; some
> time ago, have you seen it?
> "time to revert this one"
Yepp, I'll take care soonish.
>
> Roman.
>
> On Sat, Jan 3, 2015 at 9:04 PM, Ulrich Pegelow
> mailto:ulrich.pege...@tongareva.de>> wrote:
>
> Hi,
>
> there's a s
Hi,
there's a small quirk with current master in that the width of the left
hand panel grows under certain conditions. Root cause seems to be that
darktable forgets to ellipse the "full path" field of the image
information panel.
Here is how to reproduce (the images of your collection need to
Hi,
one issue that I observe:
When going from lighttable view to any other view and then back to
lighttable view the right panel is cut off by a few pixels on the right
side. This happens for the German localization, while the English one
does not show this effect.
Ulrich
---
Great, thanks! Let's hope they fix it soon. I got the same lens recently :)
Am 24.12.2014 um 09:32 schrieb Matthias Bodenbinder:
> Am 23.12.2014 um 17:40 schrieb Ulrich Pegelow:
>
>> May I ask you to get into contact with the developers?
>
> I did it: http://dev.exiv2.org/i
Am 23.12.2014 um 17:07 schrieb Matthias Bodenbinder:
>
> In the output of exiv2 I find the "(507)" value in:
> Exif.CanonCs.LensTypeShort 1 (507)
Looks like the new lens is not yet fully supported by libexiv2.
>
> But the correct lensname is also there two times:
>
Am 23.12.2014 um 15:39 schrieb Patrick Shanahan:
> * Matthias Bodenbinder [12-23-14 08:57]:
>> today I got a new lens: Canon 16-35mm 1:4 L IS USM
>>
>> The lens is not recognized by darktable. The Information section for the
>> RAW says "Lens = (507)". Whereas the exiftool correctly reads "Lens I
Am 21.12.2014 um 14:58 schrieb Richard Levitte:
> Done.
Thanks!
Ulrich
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with
Dear Richard,
looks good! Do you want to push the fix?
Ulrich
Am 21.12.2014 um 10:14 schrieb Richard Levitte:
> In message <5495cf4c.20...@tongareva.de> on Sat, 20 Dec 2014 20:34:36 +0100,
> Ulrich Pegelow said:
>
> ulrich.pegelow> Am 20.12.2014 um 19:44 sc
Am 20.12.2014 um 19:44 schrieb Richard Levitte:
> An external reference will certainly have a colon, so something like
> this (assuming they're all surrounded by ")?
>
> 's|"\([^":]*\.html\)"|"\1.php"|g'
>
> I haven't really tested much, but it's an idea...
OK, looks reasonable. But now come the s
The culprit seems to be this command in doc/usermanual/CMakeLists.txt:
COMMAND find ${CMAKE_CURRENT_BINARY_DIR}/wp -name *.html -exec sed -i
"s/\\.html/\\.html\\.php/g" {} \;
(and the corresponding command for mult-line replacements if Saxon is used).
It does not destinguish between internal re
Oh, right. Thanks for reporting. I'll need to find out where the suffix
gets added and how to fix it.
Ulrich
Am 20.12.2014 um 17:56 schrieb Markus Jung:
> Hello folks,
>
> the online version of the user manual has broken links, because a ".php"
> suffix is appended to them. Apparently, this only
FWIW our most recent manual contains a short section on how to setup a
working OpenCL system:
http://www.darktable.org/usermanual/ch09s02s04.html.php
As we explain a bit about the OpenCL data flow this section might also
be a starting point in case of issues.
Ulrich
Am 12.12.2014 um 14:42 sch
Thanks, I'll have a look. Saxon is only needed if you want to build the
html version of our usermanual in www.darktable.org. So most users can
happily live with saxon not be found.
Ulrich
Am 10.12.2014 um 21:22 schrieb Kasun Chathuranga:
> Hello,
> In Fedora systems saxon.jar is provided by sax
I don't have any access to the system you describe, so all I can do is
guess. Most likely the problems are caused by the OpenCL compiler
implementation for the specific hardware. At least the unusal number of
compiler warnings points into that direction - neither AMD nor NVIDIA
show these warni
Dear translators,
I'd like to announce the string freeze of our user manual as of now.
This should give you some time to update your translations.
An upcoming notice about the release plan of darktable 1.6 will tell you
further details when we will publish the next darktable release. If your
t
Am 04.11.2014 um 23:48 schrieb Tobias Ellinghaus:
> Am Dienstag, 4. November 2014, 23:10:40 schrieb Richard Levitte:
>
> [...]
>
>> P.S. how iminent is the 1.6 release? I don't want to rush this thing,
>> so if the release is very soon, chances are I won't be done before then.
>
> We plan to get 1
OK, thanks for testing.
Then I would say that - given the inherent limitations of GPU memory -
darktable does a pretty decent job :)
We cannot influence other applications claiming GPU memory. All we can
do is deal with this situation - fall back to CPU but continue trying to
use the GPU if po
Interesting observation! Does you issue only happen while you are
actively working with geeqie or does it also occur when geeqie is idle?
Ulrich
Am 03.11.2014 um 12:30 schrieb Matthias Bodenbinder:
> I made some more tests also with newest NVIDIA driver 343.22. What I found so
> far is that the
Hi,
I did some further checks on older images.
Frankly speaking, I have to say we are in a deep shit.
Just checked an image where some weeks ago I successfully applied
geometric lens correction. Nothing works now, image is heavily
distorted. Can't even get darktable to detect the lens profile.
Hi Jo,
the reported issue seems to be fixed with current master (commit
164ad8cae3b40017e48581c143084fa3759405b7). I only checked the behavior
of the demosaic module. Please tell me if you need further testing from
my side on other modules.
@Roman:
I noticed the problem with c15f26a6c57fbf5583
Hi,
I just observed a problem in the demosaic module. Changes from the
default settings of a demosaic method seems not to get recorded in the
history stack. When I leave darkroom and come back again the demosaic
method is back to its default (VNG for X-Trans and PPG for the rest).
The same is
Hi Matthias,
unfortunately I did not find anthying helpful in there. I had the faint
hope that you might be using some seldomly used module that might have a
memory leak in its OpenCL code - this would have explained your issues.
However, nothing like that is the case. You have the same modules
0.10.2014 um 18:23 schrieb Matthias Bodenbinder:
> Am 20.10.2014 um 07:39 schrieb Ulrich Pegelow:
>> What denoising method did you chose in that module? Non-local means or
>> wavelet?
>>
>> Best wishes
>>
>> Ulrich
>>
> I am always using non-local mean
.
Ulrich
Am 20.10.2014 um 18:23 schrieb Matthias Bodenbinder:
> Am 20.10.2014 um 07:39 schrieb Ulrich Pegelow:
>> What denoising method did you chose in that module? Non-local means or
>> wavelet?
>>
>> Best wishes
>>
>> Ulrich
>>
> I am always u
inder:
> Am 20.10.2014 um 07:39 schrieb Ulrich Pegelow:
>> What denoising method did you chose in that module? Non-local means or
>> wavelet?
>>
>> Best wishes
>>
>> Ulrich
>>
> I am always using non-local means. I have attached an example dtstyle file
What denoising method did you chose in that module? Non-local means or
wavelet?
Best wishes
Ulrich
Am 20.10.2014 um 07:22 schrieb Matthias Bodenbinder:
> Am 19.10.2014 um 21:32 schrieb Patrick Shanahan:
>>
>> just installed 340.46 but on openSUSE-Factory and using darktable from
>> git. Will r
I don't know for sure but most likely neither of the two uses OpenCL.
Concerning that graphics driver version maybe some other people using it
can tell us their experiences.
Ulrich
Am 19.10.2014 um 19:26 schrieb Matthias Bodenbinder:
> Am 19.10.2014 um 15:55 schrieb Ulrich Pegelow:
&g
I don't think that values as high as 600 really make sense as I can't
imagine that typical gui and driver related requirements are much higher
than 300MB. I see two possibilities: either there is another application
or background job on your system that uses OpenCL memory, or the
graphics drive
Hi,
the error code -4 in opencl means that a memory object could not be
allocated. It is not uncommon that the whole memory management on your
graphics card has issues once this happens so that only a reboot helps.
My best guess would be that your setting of opencl_memory_headroom
should be in
Hi,
should be fixed now in git master. Please test.
Thanks for reporting.
Ulrich
Am 08.10.2014 um 01:00 schrieb Per Östlund:
> Hi,
>
> I've felt that darktable has been rather slow for a while now, and when
> trying to figure out why I found out that even though I have OpenCL
> activated it's r
Hi,
that's really a bit strange. I'll have a look.
Ulrich
Am 08.10.2014 um 01:00 schrieb Per Östlund:
> Hi,
>
> I've felt that darktable has been rather slow for a while now, and when
> trying to figure out why I found out that even though I have OpenCL
> activated it's running demosaicing on th
Am 17.09.2014 19:35, schrieb Pascal Obry:
>
> After a full day to rebuild my mipmap cache (40% was done):
>
> [mipmap_cache] serialization to
> `/home/obry/.cache/darktable/mipmaps-62d87cbcad56aa2b4a21cd680776714d70e93ef6'
> failed!
>
> Shouldn't we consider reverting the recent patches on this co
Am 15.09.2014 23:42, schrieb parafin:
> try now, should be fixed with 893b171b8531a5367a0c4039baa019027a2d1987
>
Well, now it fails to compile for me on openSUSE 13.1 :(
In file included from
/home/pegelow/darktable/src/imageio/format/exr.cc:39:0:
/home/pegelow/darktable/src/control/conf.h: In f
Am 15.09.2014 21:10, schrieb Roman Lebedev:
> Hi.
>
> As far as i am aware, struct dt_mipmap_buffer_dsc is *not* being stored
> in on-disk mipmap cache.
>
>
> Aside from that, so far i have no more ideas.
>
If you can't fix it you need to revert the one or two commits in
question. You just can't
Please see also remine ticket #10109. darktable just crashes for me on
start due to commit ffbec14de21b0d3cf0b77e040308134c49632c22.
Ulrich
Am 15.09.2014 21:05, schrieb Pascal Obry:
> (Roman, I CC you as this seems a serious regression).
>
> I think this is a big problem with the mipmap cache.
>
Dear Istvan,
I consider your proposed option but it will take a bit time for
implementation.
In between you might upgrade your nvidia driver. The background of your
issue is a long standing bug in nvidia's opencl implementation reported
to the developers some time ago. I recently got the confi
Hi,
your current darktable version is obviously older than the last one you
have used to edit your photos. There is no way of downgrading to older
versions withtout risking parts of your newer edits.
From the version numbers you gave it seems that you have been working
with darktable 1.4.2 an
Hi Edoardo,
the kernels in nlmeans.cl are used from the non-local means module which
you can find in src/iop/nlmeans.c.
We make use of some abstraction layer functions which are defined in
src/common/opencl.c.
Ulrich
Am 19.06.2014 16:21, schrieb edo.brune...@gmail.com:
> Hi, I'm interested i
Hi Sven,
nice to hear of you. I think we talked a bit in the breaks of Pat's
portrait retouching session.
When we started with OpenCL in darktable we could only rely on OpenCL
1.0, as drivers for higher versions were not widespread. Therefore even
today we only use the basic set of 1.0 command
Am 12.06.2014 19:34, schrieb Pascal Obry:
> Le jeudi 12 juin 2014 à 19:10 +0200, Ulrich Pegelow a écrit :
>> So would this also be extensible to turboprint as a driver? I know that
>> this is not an open source project but according to my experience it
>> often has the better
Am 12.06.2014 13:37, schrieb Pascal Obry:
> Hi Tobias,
>
>> I am not too knowledgeable about printing, but from what I understand
>> Gutenprint is "just" a set of drivers that can be used from CUPS. So in order
>> to
>> - cut down on direct dependencies and
>> - make this useful on OSX
>> I wou
Am 17.05.2014 01:16, schrieb Chris:
> Ulrich Pegelow wrote, le 16/05/2014 21:32 :
>> No idea. Does not happen here, neither with AMD nor with NVIDIA.
>>
>> Ulrich
>
> I found that Performance Level of the GPU switch from 0 to 2 (the
> maximum) as soon as DT is launc
No idea. Does not happen here, neither with AMD nor with NVIDIA.
Ulrich
Am 16.05.2014 21:23, schrieb Chris:
> Hi,
>
> After launching DT the GPU temperature (and fan speed) rise
> significantly even without using it (see curve) :-\
> OpenCL activated or not !
>
> DT 1.4.2 from ppa
> Ubuntu 14.04
Can you share the mask (i.e. XMP) please?
Ulrich
Am 02.05.2014 23:39, schrieb Moritz Moeller:
> I was editing a single mask (path) for almost an hour before this
> happened. So mask stability has improved heaps.
> Also, after the crash, only the very last edit on the mask was missing.
> Great wor
Am 28.04.2014 11:26, schrieb Pascal Obry:
> Since I've upgraded to Nvidia 331.67 I cannot get OpenCL to work. I
> have run darktable with -d open and got:
>
> [opencl_init] opencl related configuration options:
> [opencl_init]
> [opencl_init] opencl: 1
> [opencl_init] opencl_library: ''
> [opencl_i
Hi guys,
I decided to start early with updating the usermanual for the next
feature release (that's 1.6 or 2.0 or whatever, not 1.4.2!). As we have
now a manual with translation(s) (thanks to Victor, Michel and Jean-Luc)
I need to finish the english version a bit earlier than I used before.
Th
Hi David,
I guess you need to be a bit more specific about the problem else nobody
can help.
Ulrich
Am 11.04.2014 17:08, schrieb David Vincent-Jones:
> Putting a fresh install of dt into place the subject element now appears
> to pose a problem.
> Has something changed?
> This is on an openSUSE
Am 26.03.2014 22:33, schrieb Christian Kanzian:
> Am Mittwoch, 26. März 2014 schrieb jerome:
>
>> So is this normal ?
>> I mean, core use and the fact I need export only one at time ?
>>
>> Sorry for long story but it help to understand how and why.
>>
>> And sorry for my bad english ;)
>>
>> Thank
In short: currently there is no open source OpenCL driver, neither for
AMD nor for NVIDIA.
Ulrich
Am 11.03.2014 12:58, schrieb Dave:
> Hello all.
>
> I may get shot for this question, but here goes:
>
> Is it possible to have darktable use libOpenCL without installing
> proprietary graphics driv
Am 13.02.2014 20:44, schrieb David Vincent-Jones:
> I have seen this change only in the last week. There appears to be a
> problem that may have originated in changes within the data-base.
> When I rebuilt my 64 bit system the 'bad' tag problem became apparent
> (something that was fixed a long tim
Am 13.02.2014 02:35, schrieb David Vincent-Jones:
> With the most recent dt versions (darktable 1.5+373~gb4ecc10) I am
> showing significant memory problems on my 32 bit 'traveling' system
> despite having the 4 Gb. max memory installed.
> After processing all the image thumbnails turns to skulls.
Great idea!
I'm in. Size L.
Am 27.01.2014 23:51, schrieb Tobias Ellinghaus:
> Dear everyone on the mailing lists,
>
> darktable is celebrating its 5th birthday this year, and since that is quite a
> nice excuse for doing something extra we decided to make the first official
> darktable t-shirt. Y
Am 19.01.2014 22:56, schrieb Simon Spannagel:
> Pascal fixed this, should be fine again now.
> Thanks for reporting!
>
> /Simon
Well, the current french usermanual as in master is still incomplete
with only parts of the english strings translated. There was another
version coming with commit 843
This problem is usermanual related. Seems that we have two people,
Victor and Jean-Luc, working on the French translation and there are
some conflicting changes. It would be cool if you guys could align.
Ulrich
--
Centu
Hi Jean-Luc,
really cool! Pushed.
Ulrich
Am 17.01.2014 19:50, schrieb Jean-Luc Coulon:
> Le 17/01/2014 18:30, Ulrich Pegelow a écrit :
>> Hi,
>>
>> that's really great to hear! Would be the first non-english version of
>> the manual then! The best option
Am 17.01.2014 19:50, schrieb Jean-Luc Coulon:
> Le 17/01/2014 18:30, Ulrich Pegelow a écrit :
>> Hi,
>>
>> that's really great to hear! Would be the first non-english version of
>> the manual then! The best option for us to review would be a pull
>> request th
Hi,
that's really great to hear! Would be the first non-english version of
the manual then! The best option for us to review would be a pull
request that you would create from within github.
We recently had some formal changes to the docbook sources to make them
pass xmllint. So there might be
Hi Mark,
it's a known bug in NVIDIA's OpenCL-compiler of that version number
304.xx. Please try to upgrade your driver to a later version like 319.xx
or better.
Ulrich
Am 09.01.2014 02:05, schrieb Mark Garrow:
> As I'm on IRC when most are sleeping I thought I'd post.
> I just got a new card i
Am 05.01.2014 01:08, schrieb Tobias Ellinghaus:
> Dear developers, contributors and regulars.
>
> As you probably heard by now the next Libre Graphics Meeting (LGM) will be
> held in Leipzig from April 2nd till 5th this year. It will most likely be the
> last one in Europe for a while.
>
> darktabl
Am 03.01.2014 09:46, schrieb Frederic Crozat:
> Hi all,
>
> I'm able to easily trigger a crash when adding / removing mask in spot
> removal module.
>
> Feel free to ask for more informations, if needed.
>
Yes, I ask you :) Would you be so kind to releal more of your findings,
e.g. what to do in
Am 31.12.2013 04:07, schrieb Mark Heieis:
> I did some looking around and found this from
> https://lists.oasis-open.org/archives/docbook-apps/201011/msg00043.html:
>
> [ ... ]
>
> Is there a reason why darktable using such an old version of saxon?
>
This is what the docbook saxon extensions requ
Hi,
I just saw that there have been done some changes to the usermanual
sources as part of recent commits.
Please don't do that!!!
We have currently some translators actively working on the current
manual. In parallel I have an improved version which passes xmllint in
branch "usermanual". If
Am 27.12.2013 18:12, schrieb Moritz Moeller:
> On 27/12/13 6:04 pm, Ulrich Pegelow wrote:
>> Guess I found the cause. Too bad this got only discovered just after the
>> release :/
>
> Well, I think it's not such an issue to do 1.4.1, innit? :D
>
> Btw, is there
Am 27.12.2013 17:56, schrieb Moritz Moeller:
> On 27/12/13 5:52 pm, Ulrich Pegelow wrote:
>> Some info on the size of the image (w * h) and the rough percentage of
>> area covered by the path would be fine.
>
> The images come from my GH2, so they're RAWs 4752x3168 in si
Am 27.12.2013 17:35, schrieb Moritz Moeller:
> On 27/12/13 3:32 pm, Ulrich Pegelow wrote:
>> Can you offer a recipe of how to reproduce the crash? From the backtrace
>> I would guess that this happens if the path has a significant portion of
>> self-intersections.
>
>
Can you offer a recipe of how to reproduce the crash? From the backtrace
I would guess that this happens if the path has a significant portion of
self-intersections.
Ulrich
Am 25.12.2013 20:43, schrieb Moritz Moeller:
> I get this crash regularly, when editing path-based masks in 1.4 on OS X
>
Hmm, works without problems here - both when building with saxon and
with xsltproc (the latter one with the known formatting issues).
Have you cleaned ./build before?
Ulrich
Am 23.12.2013 17:09, schrieb Alexander Wagner:
> Hi!
>
> Upon conversion of the user manual to epub I found the following
Nope, this is not possible without changing significant parts of
darktable's architecture. darktable is event driven which means that
there is no single place in code where any reliable synchronization
between pixelpipes could be managed.
Ulrich
Am 22.12.2013 00:13, schrieb suni:
> OK, it seem
David,
attached is a patch that tries another workaround for NVIDIA's OpenCL
bug. Maybe you can give it a try.
Ulrich
Am 02.12.2013 20:26, schrieb David Vincent-Jones:
After installing the latest Nvidia drivers my machine appears to go a
long way towards fully implementing the compiles neede
This is a bug in NVIDIA's OpenCL compiler. I reported it to them a year
ago and they confirmed it's a bug. Seems that they did not fix it in the
304.xx legacy series of their driver.
I guess there are only two chances for you to get OpenCL running. Either
you switch to a newer driver version an
Am 02.12.2013 01:44, schrieb Moritz Moeller:
> The online user manual says v1.2 and I can't find anything about how
> focus detection in lighttable works (nor can I figure it out myself,
> intuitively).
The online usermanual will be updated when the pre-release phase is
finished.
In between you
age <5291b9d2.8090...@tongareva.de> on Sun, 24 Nov 2013 09:33:22
> +0100, Ulrich Pegelow said:
>
> ulrich.pegelow> Am 24.11.2013 01:28, schrieb Tobias Ellinghaus:
> ulrich.pegelow> > Tada, STRING FREEZE!
> ulrich.pegelow> >
> ulrich.pegelow>
> ulrich.pegelow>
Am 24.11.2013 01:28, schrieb Tobias Ellinghaus:
> Tada, STRING FREEZE!
>
Effective from now also the usermanual is in string freeze.
Usermanual translators welcome!
Ulrich
--
Shape the Mobile Experience: Free Subscrip
Am 23.11.2013 16:21, schrieb Michael Born:
> Am 23.11.2013 15:09, schrieb Ulrich Pegelow:
>
> Nobody would be surprised about driver bugs, but I have to say, that
> this problem isn't there all the time.
> So, I have to find something to trigger/reproduce the bug :-(
>
Pl
Am 23.11.2013 16:04, schrieb Togan Muftuoglu:
>>>>>> "Ulrich" == Ulrich Pegelow writes:
>
> Ulrich> Looks like a driver bug. I am running the same HD7950 device with
> Ulrich> Catalyst 13.8.beta1 without any issues. Maybe you should try t
Looks like a driver bug. I am running the same HD7950 device with
Catalyst 13.8.beta1 without any issues. Maybe you should try that one.
Ulrich
Am 23.11.2013 13:11, schrieb Michael Born:
> With the GIT version of yesterday (I had this with older GIT versions,
> too) I had massive picture corrupt
Hi,
I agree to most of your suggestions. However, as these changes should be
part of bigger revision of that module we won't see these changes in 1.4
as this would clearly break feature freeze. All this will happen after
1.4 is there.
Ulrich
Am 13.11.2013 22:19, schrieb Roumano:
> Hi,
>
> Yes
Hi,
I just pushed a fix according to the principles I layed out earlier,
both for ISO and aperture properties.
Please have a look.
Ulrich
Am 11.11.2013 23:57, schrieb Matze:
> Hi,
>
> recently I noticed, that something goes wrong with collections ISO
> filtering, so I made some testshoots with
techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> ___________
> dark
Hi Elle,
I think something you wrote in an earlier posting explains:
"I'm running up-to-date 64-bit Gentoo Linux and Darktable 1.2.3 from
Gentoo portage. My "desktop" is Icewm, with the minimal amount of
gnome/gtk to get Gimp to run, plus the minimal amount of kde/qt to get
digiKam and Krita to r
Am 03.11.2013 16:48, schrieb Togan Muftuoglu:
>
> Hi,
>
> When using collect images module to narrow down the selection with color
> labels is stuck to "red" even if I click to any other color. So let's say I
> want only "green", but it is stuck with "red". I correct it to green by first
> deleting
1 - 100 of 352 matches
Mail list logo
