Am 06.11.19 um 19:33 schrieb François Tissandier:
> Well, look at Sony RX100. Sony keeps producing and selling several
> generations at the same time, right ?
Indeed - the only replaced modules is the RX100-V that got replaced by a
RX100-VA. The others (RX100, RX100-II, -III, -IV, -VI, -VII) remai
Hi,
filmic RGB works in a native RGB space, while the previous filmic worked
in a native Lab space and did the RGB conversion internally.
The difference is in the blending and masking options : old filmic had
(non-linear) Lab blending parameters, while filmic RGB has (linear) RGB
blending paramet
On Wednesday, 6 November 2019 21:27:30 CET Pascal Obry wrote:
> Hi Ihor,
>
> > When 3.0 GA is expected to be released?
>
> Sorry what is GA ?
General Availability
https://en.wikipedia.org/wiki/
Software_release_life_cycle#General_availability_(GA)
--
Andreas Schneider a...@cry
Le mercredi 06 novembre 2019 à 20:52 +, Simon a écrit :
>
> On 6 November 2019 20:27:30 GMT, Pascal Obry wrote:
> > Hi Ihor,
> >
> > > When 3.0 GA is expected to be released?
> >
> > Sorry what is GA ?
>
> GA = General Availability. (I.e., out of beta and available to the masses)
Ok, so
Hi Ihor,
> When 3.0 GA is expected to be released?
Sorry what is GA ?
> Also, is the project public roadmap available somewhere?
There is no roadmap, public or not. The project advance based on
developers' proposals.
Best wishes,
--
Pascal Obry / Magny Les Hameaux (78)
The best way to
Great news, thanks for the update.
When 3.0 GA is expected to be released? Also, is the project public roadmap
available somewhere?
Thanks
On Mon, Nov 4, 2019, 7:45 PM Pascal Obry wrote:
>
> The darktable 3.0.0rc0 release is out.
>
> The full description and release notes can be found here:
>
Well, look at Sony RX100. Sony keeps producing and selling several
generations at the same time, right ?
François
Le mer. 6 nov. 2019 à 18:56, Julian Rickards a
écrit :
> Not quite sure how to interpret "entertaining". I was approaching this
> from a different point of view, one that we tak
Not quite sure how to interpret "entertaining". I was approaching this from
a different point of view, one that we take here at my workplace. When a
new model of a camera is released (OMD E-M5 Mk III for example), the
manufacturer generally doesn't continue to produce any of the previous
versions (
On 6.11.19 14:35, Julian Rickards wrote:
From my perspective, filmic2 isn't appropriate. I work in the
publication services section of an Ontario (Canada) government ministry
and when we assign "2" to a publication, "1" is gone and no longer
available.
That's the most entertaining reasoning
>From my perspective, filmic2 isn't appropriate. I work in the publication
services section of an Ontario (Canada) government ministry and when we
assign "2" to a publication, "1" is gone and no longer available.
If the original filmic is gone from this version, then I would just name
the new one
On Tue, Nov 5, 2019, at 16:03, Heiko Bauke wrote:
> PS: What is the preferred place to report issues particularly for the
> release candidate? Github might be more suitable, but rc issues might
> get lost among other general issues.
For something like that, where you know the commit involve
Hi,
Am 04.11.19 um 18:44 schrieb Pascal Obry:
The darktable 3.0.0rc0 release is out.
just observed some odd behavior: Resetting all parameters of the local
contrast module via the module's reset button yields:
* detail 125%
* highlights 50%
* shadows 50%
* midtone range 0.5
resetting the i
Hi,
Am 05.11.19 um 23:59 schrieb jys:
I think that would cause *endless* confusion... probably better to
call the new one 'filmic2' or something.
agree, "filmic2" is not bad.
Heiko
--
-- Number Crunch Blog @ https://www.numbercrunch.de
-- Cluster Computing @ https://www.clustercomp
On Tue, Nov 5, 2019, at 14:29, Heiko Bauke wrote:
> * Some modules can not be turned off (e.g. demosaic, output color
> profile) and therefore appear always in the active modules tab. The
> knob left to the module name of those mandatory modules is always grayed
> out as if the modules was
Thank you for quick and useful reply.
Good night!
On Tue, 2019-11-05 at 23:00 +0100, Nicolas Auffray wrote:
> > Nicolas, can you fix those two issues I addressed earlier? I just
> > copy
> > from one of my letters to this mailing list.
> >
> >
> >
> > 1. Default dt theme has switched to sans-s
Nicolas, can you fix those two issues I addressed earlier? I just copy
from one of my letters to this mailing list.
1. Default dt theme has switched to sans-serif as default font but
#live-sample-data still uses "courier". I believe "monospace" is better
choice if aliased font is used in all ot
On Tue, 2019-11-05 at 19:49 +0100, Nicolas Auffray wrote:
> ... I'm the author of grey theme...
Nicolas, can you fix those two issues I addressed earlier? I just copy
from one of my letters to this mailing list.
1. Default dt theme has switched to sans-serif as default font but
#live-sample-data
On Tue, 2019-11-05 at 22:22 +0100, Nicolas Auffray wrote:
Looks like I'm having bad day and have to repeat myself once again. I
was talking about default Debian 10 installation. This uses 11 pt size
like most distro do.
As I said I know that theme is "entirely" CSS adjustable. This is how I
fixed
Hum, have you read what we have said ? It's also related to dpi
rendering, so it is the way that works in GTK (related to font OS size
and dpi rendering)... What I just add is how on start em, px, etc. work
with CSS. And the new darktable UI is entirely adjustable by CSS
(colors, fonts, sizes,
I know how it should look like, but it is not the way it works in GTK
implementation. Size differs in browsers (they use 16 as base for 1em
usually) and GTK.
On Tue, 2019-11-05 at 21:45 +0100, Nicolas Auffray wrote:
> em size and how it works is not related to GTK but a standard usage
> on
> scre
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
em size and how it works is not related to GTK but a standard usage on
screen rendering. So all apps, system should use this standard thing.
It's noted for example on CSS standard W3C page :
https://www.w3.org/Style/Examples/007/units.en.html
Anyway, it seems as Aurelien precise it, that some
On Tue, 2019-11-05 at 20:47 +0100, Aurélien Pierre wrote:
> > Real size of 1em is 13.33px on my OS (with default OS font on
> > 10 size). If I increase my OS font on 11 size, the size of 1em
> > become 14.66. 1em = 1.px, so just the normal
> > behaviour.
> >
Nicolas, strange thin
On Tue, 2019-11-05 at 20:47 +0100, Aurélien Pierre wrote:
> Setting font size to 1em should tell GTK to use the default OS font
> size, no matter its value.
Size doesn't match default OS settings (Debian 10 default installation)
on 3 displays I tried (2 low-dpi, 1 high-dpi). Do you have link on GT
Hi,
I have a PR waiting with a possible fix :
https://github.com/darktable-org/darktable/pull/3068
I have tested dt 3.0rc0 on Mac OS (temporary access to a MacBook) and
fixed the oversizing with dpi set to 80 too. But I reproduced. Same way,
the fonts in tone-equalizer are oversized.
But I have
Hi Timur,
Real size of 1em is 13.33px on my OS (with default OS font on 10
size). If I increase my OS font on 11 size, the size of 1em become
14.66. 1em = 1.px, so just the normal behaviour.
Le 05/11/2019 à 19:57, Timur Irikovich Davletshin a écrit :
Hi, Nicolas!
Don't take
Anyway, that's not ok as the new UI is now size adjustable (by using
CSS, not have anymore hardcoded things and use emphasis sizes on most
parts to adjust correctly). It seems to be a MacOS specific issue...
Le 05/11/2019 à 18:56, Moritz Moeller a écrit :
On 5.11.19 18:42, I wrote:
I have th
Hi, Nicolas!
Don't take offense, I'm not yelling :)
But can you tell me, what is real size of 1em (used in your theme too)
in GTK/Linux and GTK/MacOS?
Thanks for your work on themes, btw.
Timur.
On Tue, 2019-11-05 at 19:49 +0100, Nicolas Auffray wrote:
> Many people I know use darktable, even
Many people I know use darktable, even on Linux correctly. And I'm the
author of grey theme so work a lot on the UI and made many tests on my
system. I never had issue you relate, even on my previous 27" full HD
screen, my Macbook Pro retina 13" or my new 24" WQHD screen. So that
would say it's
Actually I have same issue on Linux too. But I was tired telling
Aurelien about font size issues and modified theme to match my needs.
On Tue, 2019-11-05 at 19:21 +0100, Moritz Moeller wrote:
> On 5.11.19 19:18, Nicolas Auffray wrote:
> > Anyway, that's not ok as the new UI is now size adjustable
On 5.11.19 19:18, Nicolas Auffray wrote:
Anyway, that's not ok as the new UI is now size adjustable (by using
CSS, not have anymore hardcoded things and use emphasis sizes on most
parts to adjust correctly). It seems to be a MacOS specific issue...
It's not an issue for me but for a first time
On 5.11.19 18:42, I wrote:
I have the crazy oversized UI issue on macOS again. :)
Setting the bauhaus/scale in darktablerc doesn't help.
Never mind, setting screen_dpi_overwrite to 80 made the UI kinda the
right size (except side panels which I had to scale down to 300).
.mm
Thanks for the great work, guys!
On 4.11.19 18:44, Pascal Obry wrote:
The darktable 3.0.0rc0 release is out.
[...] > This is the first pre-release, test it and please be sure to report
issues you found.
I have the crazy oversized UI issue on macOS again. :)
Setting the bauhaus/scale in darkt
The darktable 3.0.0rc0 release is out.
The full description and release notes can be found here:
https://github.com/darktable-org/darktable/releases/tag/release-3.0.0rc0
This is by far one of the best release ever. I understand that I have
already said that for 2.6. But the list of enhancement
34 matches
Mail list logo
