Why not add Reply-To and Followup-To headers then with just ML address?
That is assuming that we allow sending to the list only from subscribed
people, otherwise I'm not sure how can one understand does he need to
CC the poster.
On Wed, 26 Oct 2016 13:10:49 +0200
Tobias Ellinghaus wrote:
> Am M
Indeed auto-detection broke with GTK update. I fixed it in 2.2.1.3 DMG. Or you
can always set it manually in ~/.config/darktable/darktablerc option
screen_ppd_overwrite=2.0
> On 28 Dec 2016, at 02:56, Bastian A. wrote:
>
> Hi everyone,
>
> thanks for the Christmas update.
> I am using darkta
Changes to cmake files is probably the culprit - rawspeed now doesn't inherit
CFLAGS from darktable and so is missing include path for libjpeg.
P.S.
About switching from stable to master branch and back - there're also issues
with cherry-picking commits for some reason. We need to come up with c
> On 4 Jan 2017, at 18:21, Roman Lebedev wrote:
>
>> On Wed, Jan 4, 2017 at 10:20 AM, wrote:
>> Changes to cmake files is probably the culprit - rawspeed now doesn't
>> inherit CFLAGS from darktable and so is missing include path for libjpeg.
>
> But from where did darktable get that jpeg in
https://github.com/darktable-org/darktable/blob/master/packaging/macosx/BUILD.txt
On Mon, 4 Dec 2017 20:44:01 +0200
Sarge Borsch wrote:
> https://redmine.darktable.org/projects/darktable/wiki/Darktable_on_OS_X
> I thought that I'd like to test darktable from the latest source code, but
> I'm n
Hi!
I'm not sure why you are missing this port. Did you install MacPorts to
default location (/opt/local)? Maybe try running `sudo port selfupdate`
command.
As for building just for current OSX version - you can skip
/opt/local/etc/macports/macports.conf settings, python and
GraphicsMagick patches
Hi,
backtrace is somewhat strange, maybe another thread is to blame:
Thread 58:
0 librawprepare.so0x00011015f631
process_sse2._omp_fn.3 + 321 (rawprepare.c:401)
1 libgomp.1.dylib 0x000108958d37 0x108951000 + 32055
2 libsystem_pthread.dylib
I will build the package this weekend, sorry everyone for delay, I am very busy
with work after my vacation. I have Apple certificate from my workplace (with
permission to use it for DT), no need for anyone else to buy it.
> On 16 Jan 2018, at 23:14, Neil Schemenauer wrote:
>
>> On 2018-01-16,
And it's done:
https://github.com/darktable-org/darktable/releases/download/release-2.4.0/darktable-2.4.0.dmg
On Wed, 17 Jan 2018 13:06:33 +0100
para...@paraf.in wrote:
> I will build the package this weekend, sorry everyone for delay, I am
> very busy with work after my vacation. I have Apple c
Hi,
I plan on creating 2.6 macOS packages starting with RCs, but no, I don't
test master currently. Maybe someone else on Mac does it.
On Wed, 28 Nov 2018 17:45:38 +0100
Pascal Obry wrote:
> Hi!
>
> Just wanted to know what is the plan for the MacOS and Windows
> releases. Are the maintainers
One can argue that crashing might be helpful for debugging - backtrace
is produced and it's possible to deduce the reason DT exited. E.g. if
some allocation size is computed too high (say due to integer
underflow) malloc can fail and if we just exit cleanly we will lose all
context of the failure.
dxomark.com website seems to have relevant numbers, see for example
Nikon lens mentioned by Sturm Flut:
https://www.dxomark.com/Lenses/Nikon/AF-S-Nikkor-24-70mm-f-2.8G-ED-mounted-on-Nikon-D750__975
https://www.dxomark.com/Lenses/Nikon/AF-S-Nikkor-24-70mm-f-2.8G-ED-mounted-on-Nikon-D7100__865
Inter
I think we mix up 2 (or 3) different things in this topic. Let's say
a contributor wants to implement some feature:
First some discussion should probably happen, for example other
developers can help with pointers on how said feature can and should be
integrated into DT core. I don't see any need
I think dt should just include needed custom fonts and not depend on
system ones if theme requires specific font. So for example default
theme uses system font, that's fine, elegant theme uses specifically
Roboto font - it should be bundled together with the theme then.
The reasoning for it is the
font using @font-face in CSS. Given that dt themes are CSS files I think
it's a good analogy. Elegant theme falls into second category. And yes,
since we have elegant theme in dt repo, we should add Roboto font there
also.
On Sun, 19 May 2019 11:58:06 +0200
dt-l...@stefan-klinger.de wrote:
On Sun, 19 May 2019 13:34:54 +0200
Pascal Obry wrote:
> And let me add that there is no Roboto issue at all.
>
> 1. the default theme does not use it
>
> 2. the elegant theme use it as first proposal but there is many other
> fallbacks. If none found the system font will be picked.
>
> 3. fact
On Sun, 19 May 2019 15:12:43 +0200
Pascal Obry wrote:
> Le dimanche 19 mai 2019 à 14:40 +0200, parafin a écrit :
> > On Sun, 19 May 2019 13:34:54 +0200
> > Pascal Obry wrote:
> >
> > > And let me add that there is no Roboto issue at all.
> > >
>
On Sun, 19 May 2019 13:42:11 -0400
Patrick Shanahan wrote:
> * Patrick Shanahan [05-19-19 13:36]:
> > * Timur Irikovich Davletshin [05-19-19 13:01]:
> >
> > > On Sun, 2019-05-19 at 12:43 -0400, Patrick Shanahan wrote:
> > > >
> > > > probably being built by both in different places. dari
While I really like the idea behind filmic module, still it's not
always easy to get the colors I want with it. I guess, depending on the
camera, base curve might give better colors by default, but will make
much trouble in other departments. Obvious point that it's not that
easy as just using film
that "requires" is the right thing to do. I don't
think we managed to convince him otherwise, it's his decision in the
end after all.
On Sun, 26 May 2019 13:02:34 +0300
Timur Irikovich Davletshin wrote:
> On Sun, 2019-05-19 at 19:50 +0200, parafin wrote:
> &g
I think we still have default-on modules not recorded in history stack
(highlight reconstruction and white balance), so removing all “off” steps might
modify the image. Therefore I’m afraid your implementation is incorrect. Best
approach would be to record all applied iops to history, but it’s a
> On 12 Jun 2019, at 20:21, Aurélien Pierre wrote:
>
> Hi,
>
> I'm the author of the lighttable's compress history button. White balance and
> highlight reconstruction should never be turned off, so what would be
> the purpose of having them disabled in the first place ?
>
Yet they
Just because you don’t agree with some design decisions made previously (I seem
to remember that white balance was always on at some point), doesn’t mean you
should introduce broken code. Correct fix is to add these 2 modules to the
history, as I previously mentioned. Reverting them back to alwa
https://packages.ubuntu.com/search?keywords=libgtk
xenial (16.04LTS) (libs): GTK+ graphical user interface library
3.18.9-1ubuntu3: amd64 arm64 armhf i386 powerpc ppc64el s390x
bionic (18.04LTS) (libs): GTK+ graphical user interface library
3.22.30-1ubuntu1: amd64 arm64 armhf i386 ppc64el s390x
Please provide the error message you're seeing. I can't find any
mentions of specific jsonscheme version in darktable sources.
On Thu, 05 Sep 2019 17:03:33 +1000
"Terry Duell" wrote:
> On Thu, 05 Sep 2019 15:43:10 +1000, Pascal Obry wrote:
>
> > Le jeudi 05 septembre 2019 à 10:25 +1000, Terry
It has nothing to do with darktable, you should probably just
delete /usr/local/bin/jsonschema file (where did it come from?). It
references 3.0.1 version, and it's not part of darktable.
On Thu, 05 Sep 2019 21:03:12 +1000
"Terry Duell" wrote:
> On Thu, 05 Sep 2019 17:54
On Tue, 01 Oct 2019 23:49:03 +0200
Pascal Obry wrote:
> Dear developers !
>
> As announced back in August, we are now entering feature freeze. That
> is, at this point only bugs will be considered to be merged into
> master.
Let's hope it's the opposite - bugs got merged before this point, and
Is it any different from velvia iop in darktable?
On Thu, 10 Oct 2019 20:44:25 +0200
Keresztes Barna wrote:
> Hi all,
>
> I'm a happy user of Darktable! One of my favorite tools in the 2.7 branch
> is the *Basic Adjustments tool*, where I can find in one place most of the
> tools I need to mak
I would vote for doing a 2.6.3 in order to release a fix for this macOS
bug:
https://github.com/darktable-org/darktable/issues/3107
and I will try to fix another one this week too:
https://github.com/darktable-org/darktable/issues/1977
Not sure what else we might want to add.
On Mon, 14 Oct 2019
On Fri, 18 Oct 2019 08:06:34 +0200
Pascal Obry wrote:
> Hello Parafin,
>
> > I would vote for doing a 2.6.3 in order to release a fix for this macOS
> > bug:
> > https://github.com/darktable-org/darktable/issues/3107
> > and I will try to fix another one this we
Haven't some distribution rebased that patchset on 2.6 already?
On Fri, 18 Oct 2019 17:31:48 +0200
Pascal Obry wrote:
> Le vendredi 18 octobre 2019 à 09:44 +0200, Germano Massullo a écrit :
> > Il ven 18 ott 2019, 08:28 Pascal Obry ha scritto:
> > > Le vendredi 18 octobre 2019 à 08:16 +0200,
8, 2019 at 9:06 AM Pascal Obry wrote:
> > >
> > > Hello Parafin,
> > >
> > > > I would vote for doing a 2.6.3 in order to release a fix for this macOS
> > > > bug:
> > > > https://github.com/darktable-org/darktable/issues/3107
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91920
On Sun, 20 Oct 2019 22:39:40 +0200
Germano Massullo wrote:
> With 2.6.3 I am getting weird compilation errors on aarch64 and
> ppc64le. Does anybody else have similar problems?
> Cheers
>
> === build logs ===
> aarch64
> https://koji.fedorapro
People are confused even with history (left panel) and iop list (right
panel) being in different order, and you are proposing to introduce
third ordering of modules. I'm strongly against complicating things
like that. Favorites tab doesn't look any different from any other tab
on the right panel, s
Can't reproduce. Which darktable version are you talking about? Please
try starting darktable with empty config (move away ~/.config/darktable
for the test). Also it's better to report issues on github, not in
mailing list or/and pixl.us forum.
On Mon, 4 Nov 2019 20:56:06 +0200
Henkka wrote:
>
The reason macOS users complain is because it is standard on macOS to
not scale anything to screen's DPI. DPI is assumed constant (either 72,
or 96, I'm not sure). When I originally ported darktable to macOS I
introduced a code that detects actual monitor DPI and applies it, which
results in darkta
Well, that’s the problem with basic adjustment module - IMHO it shouldn’t
exist, because it duplicates functionality of other modules, while adding
problems like the one discussed here.
> On 18 Nov 2019, at 16:13, Moritz Moeller wrote:
>
> On 15.11.19 12:02, parafin wrote:
>>
Re-check that the options you are passing to cmake matche the ones in
BUILD.txt. Specifically I think you are missing at least
-DBUILD_CURVE_TOOLS=ON
make-app-bundle script really needs better error-handling;)
On Fri, 29 Nov 2019 20:41:20 +0100
Sébastien Chaurin wrote:
> Hi everyone,
>
> I ju
y paste… I do miss this one as well
> > as the noise tool. I’ll clean it and rebuild it in the morning but I trust
> > I should be fine now.
> >
> > Somehow I knew it was something stupid ;)
> >
> > Thanks !!
> >
> >> On 29 Nov 2019, at 22
HLG gamma curve was designed to be compatible with SDR displays, so you
can just display HDR content with HLG gamma applied on SDR monitor
(which will assume it's BT.709/sRGB gamma) and get a reasonable picture.
On Thu, 26 Dec 2019 01:04:24 +0100
Aurélien Pierre wrote:
> Hi,
>
> … and that's w
You shouldn't use this version anyway:
https://github.com/darktable-org/darktable/issues/2813
On Wed, 1 Apr 2020 10:16:46 -0400
Patrick Shanahan wrote:
> * Hossam Elgabarty [04-01-20 10:05]:
> > Dear developers,
> >
> > Many thanks for the great work!
> >
> > I am recently having trouble bui
Why do you think that OpenCL is disabled?
On Sun, 21 Jun 2020 12:31:24 +0300
Alexander Rabtchevich wrote:
> Hello
>
>
> Pascal Obry wrote:
> > Le vendredi 19 juin 2020 à 19:44 +0300, Alexander Rabtchevich a écrit :
> >> Latest git builds make the next output at compilation:
> >>
> >>
> >> -
errno=13 is EACCES /* Permission denied */
Maybe you have broken permissions on some files. What does the
following command show:
ls -l
/Applications/darktable.app/Contents/MacOS/../Resources/lib/libepoxy.0.dylib
On Wed, 1 Jul 2020 07:11:08 -1000
Ken Ellinwood wrote:
> This is on OSX 10.15.5
>
relative paths are not allowed for dylib dependencies.
>
> On Wed, Jul 1, 2020 at 7:26 AM parafin wrote:
>
> > errno=13 is EACCES /* Permission denied */
> > Maybe you have broken permissions on some files. What does the
> > following command show:
> > ls -l
> &
/download/release-3.0.2/darktable-3.0.2.dmg
On Wed, 1 Jul 2020 15:06:14 -0500
August Schwerdfeger wrote:
> I have no problem running Darktable 3.0.2 on macOS 10.15.5.
>
> --
> August Schwerdfeger
> aug...@schwerdfeger.name
>
> On Wed, Jul 1, 2020 at 2:39 PM parafin wro
Could you please try the following package?
http://paraf.in/junk/darktable-3.0.2.9.dmg
On Tue, 7 Jul 2020 06:28:33 -1000
Ken Ellinwood wrote:
> FYI, I've solved my problem by building darktable from the source code.
> When I launch /usr/local/bin/darktable I don't get the error.
>
> On Thu, Ju
For the record if someone will encounter this problem - the culprit
turned out to be an antivirus software quarantining libepoxy.0.dylib.
On Sat, 11 Jul 2020 18:38:09 +0200
parafin wrote:
> Could you please try the following package?
> http://paraf.in/junk/darktable-3.0.2.9.dmg
>
&g
If you'd actually followed the BUILD.txt instructions exactly, you
wouldn't have had problems with either OpenMP or current failure. Look
for "Install required dependencies" (the list contains intltool, which
you are missing in your system) and for "Finally build and install
darktable" (there are p
OK, I have missed that you used the correct cmake call in your first
email and I saw that you are missing dependencies that should have been
installed when following the procedure, so I assumed you skipped some
steps. I can see now that one step failed and you haven't noticed, which
I didn't expect
macOS 10.7 is the oldest supported version, as stated here:
https://www.darktable.org/install/#macos
or here:
https://github.com/darktable-org/darktable/blob/master/packaging/macosx/BUILD.txt
Well, when I say supported, I just mean that it should work, I'm not
sure if it actually works on anything
Clean your install dir in this case, not just build.
On Mon, 12 Oct 2020 15:09:41 +0200
Hubert Kowalski wrote:
> People keep making same mistake
>
> Clean your build dir before compiling darktable after git update. the error
> is with "modulelist.c" file which was removed in recent module
Clean your install directory.
On Tue, 3 Nov 2020 22:36:14 +0300
Alexander Rabtchevich wrote:
> Hello. Current git master crushes at attempt to enter darkroom mode.
> Mint Mate 20 x64.
> Here is the output.
>
> (darktable:23644): GdkPixbuf-CRITICAL **: 22:31:36.345:
> gdk_pixbuf_new_from_data:
You don't understand what soft-proofing does. What you describe is
expected behavior.
On Wed, 25 Nov 2020 03:18:03 +0100
Konzertheld wrote:
> Hi everyone,
>
> I wanted to try out the Softproof feature today. I copied a profile to
> the expected folder and it shows up in Darktable. However, whe
Which lensfun version do you have installed?
I will fix this issue in the meantime.
On Wed, 25 Nov 2015 11:28:47 +
Richard Hobday wrote:
>
> Cannot get 'Compile' to complete form current GIT release-2.0rc2 .
> Was fine until I pulled the update this AM.
>
> Throws this error ...
> > [ 86%]
GraphicsMagick installs it's own SIGSEGV handler even if nothing is
loaded through it, that's why it's in backtrace. Actual crash seems to
be caused by some memory corruption (see error message), and I fear
backtrace won't help here at all.
On Tue, 02 Feb 2016 16:25:50 +0100
Tobias Ellinghaus wr
55 matches
Mail list logo
