Re: [darktable-dev] Darktable crash on export with openCl enabled

Tobias Ellinghaus writes: > Am Dienstag, 25. Oktober 2016, 23:38:57 CEST schrieb Christoph Paulik: >> Hi, >> >> I consistently get a crash when exporting images with openCL enabled. >> Darktable more or less hangs my system by using a lot of memory and then >> crashes. Export without openCL

Re: [darktable-dev] Darktable crash on export with openCl enabled

Am Dienstag, 25. Oktober 2016, 23:38:57 CEST schrieb Christoph Paulik: > Hi, > > I consistently get a crash when exporting images with openCL enabled. > Darktable more or less hangs my system by using a lot of memory and then > crashes. Export without openCL works without problems. Strangely

Re: [darktable-dev] can't find libintl while building and no Internationalization as a result

I thinks what I'm really asking is about how the github repository works in the sense of keeping sync. I forked darktable to my account and push to my account each time. Whenever I click on the "pull request" link it is actually merged to the darktable master branch. So how do I get the changes

Re: [darktable-dev] can't find libintl while building and no Internationalization as a result

Hi Roman I just want to clarify a git issue I just encountered so I will not repeat the same mistake: if I commit to my own repository on github, but didn't initiate a pull request, than I shouldn't do $ git fetch --all -p $ git rebase upstream/master master but only push the commit by $ git

[darktable-dev] Location of file export

Just exported 18 JPG files to $(DESKTOP)/CIRCUIT/$(FILE_NAME) dt correctly created the non-existing CIRCUIT folder and placed the first file in it but then placed all other files into DESKTOP. When I further tried to send other files into CIRCUIT they were all directed into DESKTOP also

Re: [darktable-dev] can't find libintl while building and no Internationalization as a result

Okay great. thanks for the walk through! I did it all wrong and that explains a lot. Now it builds okay with internationalization and all. I can see changes in the translation again. Problem solved On Tue, Oct 25, 2016 at 7:15 PM, Roman Lebedev wrote: > On Tue, Oct 25,

Re: [darktable-dev] can't find libintl while building and no Internationalization as a result

Version string: 2.1.0+2014~ge493501 Better :) On Tue, Oct 25, 2016 at 6:13 PM, shlomi braitbart wrote: > So if I understood correctly: > shlomi@avia:~/darktable2/darktable$ git fetch --tags > shlomi@avia:~/darktable2/darktable$ git fetch --tags upstream >

Re: [darktable-dev] can't find libintl while building and no Internationalization as a result

On Tue, Oct 25, 2016 at 5:28 PM, shlomi braitbart wrote: > Okay here is what I got: > > shlomi@avia:~/darktable2/darktable$ git pull --tags > Already up-to-date. > shlomi@avia:~/darktable2/darktable$ git pull --tags upstream > remote: Counting objects: 50, done. > remote:

Re: [darktable-dev] can't find libintl while building and no Internationalization as a result

try git pull --tags git pull --tags upstream git fetch upstream On Tue, Oct 25, 2016 at 5:11 PM, shlomi braitbart wrote: > Still getting the > Already up-to-date > message with no change of number: > > git describe > release-0.9.3-13734-ge493501 > git status > On branch

Re: [darktable-dev] can't find libintl while building and no Internationalization as a result

Still getting the Already up-to-date message with no change of number: git describe release-0.9.3-13734-ge493501 git status On branch master Your branch is ahead of 'origin/master' by 3 commits. (use "git push" to publish your local commits) Untracked files: (use "git add ..." to include in

[darktable-dev] darktable 2.0.7 released

we're proud to announce the seventh bugfix release for the 2.0 series of darktable, 2.0.7! the github release is here: https://github.com/darktable-org/darktable/ releases/tag/release-2.0.7. as always, please don't use the autogenerated tarball provided by github, but only our tar.xz. the

Re: [darktable-dev] Change darkroom background color

OK. I have made a flat medium-grey stylesheet in attachment. So far, I just had problems to set the colors of the background and of some modules (dropdown menus labels, sliders labels and borders). We are not to far from being able to skin entirely DT. *Aurélien PIERRE* aurelienpierre.com

Re: [darktable-dev] Change darkroom background color

Am Dienstag, 25. Oktober 2016, 06:06:25 CEST schrieb Aurélien PIERRE: > Yes, neutral = 18 % grey / 50 % luminance. So I guess there is no other > mean to change it but to recompile from the source ? Shouldn't the style > be separated from the code ? Yes, there are many places with hard coded

Re: [darktable-dev] Change darkroom background color

Yes, neutral = 18 % grey / 50 % luminance. So I guess there is no other mean to change it but to recompile from the source ? Shouldn't the style be separated from the code ? Thanks anyways. *Aurélien PIERRE* aurelienpierre.com

Re: [darktable-dev] Change darkroom background color

Am Dienstag, 25. Oktober 2016, 01:29:37 CEST schrieb Aurélien PIERRE: > Hi, > > I really believe that a photo software should have a neutral grey With "neutral" you mean "50%", not "untinted" I presume? > background in a order to avoid wrong feelings of contrast and exposition > during the

Re: [darktable-dev] can't find libintl while building and no Internationalization as a result

Am Montag, 24. Oktober 2016, 20:06:23 CEST schrieb shlomi braitbart: > git describe > release-0.9.3-13734-ge493501 That looks good. Does a "git pull" bring you any updates now? And change the 13734 to 13738 or something like that? > git status > On branch master > Your branch is ahead of

Re: [darktable-dev] Re: Another real-life example

hi, On Mon, Oct 24, 2016 at 9:46 PM, Alex wrote: > He complains about magenta shadows. [..] > The issue is obvious in these images: > http://i.imgur.com/0sixStb.jpg > http://i.imgur.com/12eQb4y.jpg yes, those images do show the mean shift when clamping to 0 before