[darktable-user] Sharpening on export

2018-06-06 Thread darktable
DT 2.4.3

Is there a way of sharpening on export?

Currently, I use mostly the highpass module for sharpening. It does
an excellent job for full-size exports, but it's not that great
when I shrink the exports (usually it's in the 900 to 1000 pixels
range).

I'd like to sharpen after shrinking either as part of the export
process or as an external (what I'm not sure). Especially when the
destination is jpeg for screen or jpeg for 4k or 5k monitors.

BTW, highpass does an extremely good job for prints.

What would you recommend?

-- 
sknahT

vyS

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org



Re: [darktable-user] Red-eyes removal

2018-06-06 Thread Jean-Luc CECCOLI
Hello,

And thanks everyone for helping.
To sum up, if I understand correctly, there are many ways to deal with red 
eyes, each one being more or less suitable for a particular case.
I now know at least 5 !
Will try others and see which applies to the case that bothers me.

Regards,

J.-Luc

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org



[darktable-user] higher zoom levels

2018-06-06 Thread sarg314 sarge
I am using darktable to analyze long exposure pictures of the night sky.
Such images are full of stars (point sources).  In order to judge the
quality of the focus (these images have to be focused manually) I need to
zoom in far enough to see the individual pixels in the star images.  At
present idarktable seems to be limited to a 200% zoom maximum which is no
where near enough.  Is there a way to zoom in further?  If not, what are
the prospects of adding this feature?

thanks,
-- 
Tom Sargent


darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: [darktable-user] darktable 2.4.4 released (Mac OS ?)

2018-06-06 Thread Tobias Ellinghaus
Am Mittwoch, 6. Juni 2018, 14:12:51 CEST schrieb J Albrecht:
> Thanks, Tobias!

Hi,

> I realise that we Mac users must usually wait longer for any new Mac OS
> releases. However, I see  that a checksum exists for the .dmg. This
> suggests that parafin has already compiled one. Yet, it isn’t in the asset
> list. Was this an oversight or have I missed something?

[...]

> > $ sha256sum darktable-2.4.4.dmg
> > ??? darktable-2.4.4.dmg

There is no checksum for the DMG yet.

Tobias

[...]

PS: I am subscribed to the list, there is no need to send me mails twice.

signature.asc
Description: This is a digitally signed message part.


Re: [darktable-user] darktable 2.4.4 released (Mac OS ?)

2018-06-06 Thread J Albrecht
Thanks, Tobias!

I realise that we Mac users must usually wait longer for any new Mac OS 
releases. However, I see  that a checksum exists for the .dmg. This suggests 
that parafin has already compiled one. Yet, it isn’t in the asset list. Was 
this an oversight or have I missed something?




> On 06 Jun 2018, at 09:39, Tobias Ellinghaus  wrote:
> 
> we’re proud to announce the fourth bugfix release for the 2.4 series of
> darktable, 2.4.4!
> 
> the github release is here: [https://github.com/darktable-org/darktable/
> releases/tag/release-2.4.4](https://github.com/darktable-org/darktable/
> releases/tag/release-2.4.4).
> 
> as always, please don't use the autogenerated tarball provided by github, but
> only our tar.xz. the checksums are:
> 
> ```
> $ sha256sum darktable-2.4.4.tar.xz
> 964320b8c9ffef680fa0407a6ca16ed5136ad1f449572876e262764e78acb04d
> darktable-2.4.4.tar.xz
> $ sha256sum darktable-2.4.4.dmg
> ??? darktable-2.4.4.dmg
> $ sha256sum darktable-2.4.4-win64.exe
> 3763d681de4faa515049daf3dae62ee21812e8c6c206ea7a246a36c0341eca8c
> darktable-2.4.4-win64.exe
> $ sha256sum darktable-2.4.4-win64.zip
> 5dba3423b0889c69f723e378564e084878b20baf3996c349bfc9736bed815067
> darktable-2.4.4-win64.zip
> ```
> 
> when updating from the currently stable 2.2.x series, please bear in mind that
> your edits will be preserved during this process, but it will not be possible
> to downgrade from 2.4 to 2.2.x any more.
> 
>  Important note: to make sure that darktable can keep on supporting the
> raw file format for your camera, *please* read [this post](https://
> discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri) on how/what raw
> samples you can contribute to ensure that we have the *full* raw sample set
> for your camera under CC0 license!
> 
> and the changelog as compared to 2.4.3 can be found below.
> 
> ## New Features
> 
> - Added 50% zoom option in darkroom mode to the navigation dropdown
> - perspective correction: usability improvement – allow setting the radius
> when (de)selecting lines
> 
> ## Bugfixes
> 
> - Fix selecting drives in the import dialog on Windows by bundling a patched
> glib
> - Add some space between checkbox and label in color picker
> - OpenCL: better readability of debug output on memory usage
> - Levels: catch an edge case where float != int
> - Fix the alignment in a tooltip in lens correction
> - Local contrast: Reset strength slider to 120% when double clicked
> - Drop unused clone masks when loading xmp files
> - Remove all sub masks when clearing cloning masks
> - darktable-cltest: do not print summary statistics on OpenCL usage
> - Perspective correction: take aspect parameter into account when judging on
> neutral settings
> - Haze removal: fix tiled processing
> - Fix install on Windows due to GraphicsMagick's versioned filenames
> - PPM: Handle byte order when loading files
> - Fix #12165: Don't try to show dialog without gui
> - Fix an out-of-bounds memory access
> - Tools: Fix typo in darktable-gen-noiseprofile that made it unusable
> - MacOS package: point gettext to correct localedir
> 
> ## Camera support, compared to 2.4.2
> 
>  Warning: support for Nikon NEF 'lossy after split' raws was
> unintentionally broken due to the lack of such samples. Please see [this post]
> (https://discuss.pixls.us/t/nikon-a-specific-raw-sample-wanted/5483?
> u=lebedevri) for more details. If you have affected raws, please contribute
> samples!
> 
> ### White Balance Presets
> 
> - Sony ILCE-6500
> 
> ### Noise Profiles
> 
> - Canon EOS 800D
> - Canon EOS Kiss X9i
> - Canon EOS Rebel T7i
> - Nikon COOLPIX B700
> - Nikon D5600
> - Olympus TG-5
> 
> ## Updated translations
> 
> - German
> - Russian



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: [darktable-user] Parametric Masking (output bar)

2018-06-06 Thread Rémi DUGRAIN
Hi,

For me it's still the same mask, but different threshold based on the
pre-effect image (input slider) or post-effect image (output slider).

Yours,

Rémi


2018-06-06 1:48 GMT+02:00 David Vincent-Jones :

> OK ... I do understand this response ... the two different bars are used
> for two different masks. Those masks could also have been used in the
> reverse order. But the same thing can be done with a single bar used for
> multiple masks. I have on occasions used three sets of masks  all of which
> have been applied through one single bar (scale).
>
> My real question is: since multiple masks can be applied with a single
> bar, is the double bar confusing for users?
>
> David
>
> On 06/05/2018 01:49 PM, William Ferguson wrote:
>
>
>
> On Tue, Jun 5, 2018 at 1:57 PM, David Vincent-Jones 
> wrote:
>
>> I use parametric masking ... a lot!     It probably is a part of my
>> processing on at least 90% of my images but, for me, there is still a
>> problem in understanding how to correctly use the 'output' bar to gain full
>> functionality of the module.
>>
>> I have watched a number of on-line videos and read the blogs and with one
>> exception the top output bar appears to be totally ignored.. I do remember
>> when this module was new that there was a blog showing the use of both bars
>> (I am not sure that I really understood it even then) but the question that
>> I have today is if this output bar is truly useful then maybe we need
>> some further direction from somebody that is fully familiar with its
>> capabilities and actually uses it.
>>
> I used a picture that had grass.  I opened the monochrome module and
> created a parametric mask, using the input sliders, to select the grass and
> desaturate it.   Then I used the output sliders on  the luminosity channel
> to change how the desaturation was applied, like a blend if.
>
> I also tried it with exposure.  I selected something with the eyedropper
> so that I got the indicator in the channels.  I created a parametric mask
> to select something that was indicated, then changed the exposure.  The
> ouput slider indicator moved as I changed the exposure.
>
> So, it appears to me that the input sliders select what is given to the
> module to be changed and the output sliders select how the result of the
> change is applied.  Up until you asked the question I'd never played with
> them, but this opens up all sorts of new possibilities.  Thanks.
>
> Bill
>
>> David
>>
>> 
>> darktable user mailing list to unsubscribe send a mail to
>> darktable-user+unsubscr...@lists.darktable.org
>>
>
>
> 
> darktable user mailing list to unsubscribe send a mail to
> darktable-user+unsubscr...@lists.darktable.org
>
>
>
> 
> darktable user mailing list to unsubscribe send a mail to
> darktable-user+unsubscr...@lists.darktable.org
>


darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org



[darktable-user] darktable 2.4.4 released

2018-06-06 Thread Tobias Ellinghaus
we’re proud to announce the fourth bugfix release for the 2.4 series of 
darktable, 2.4.4!

the github release is here: [https://github.com/darktable-org/darktable/
releases/tag/release-2.4.4](https://github.com/darktable-org/darktable/
releases/tag/release-2.4.4).

as always, please don't use the autogenerated tarball provided by github, but 
only our tar.xz. the checksums are:

```
$ sha256sum darktable-2.4.4.tar.xz
964320b8c9ffef680fa0407a6ca16ed5136ad1f449572876e262764e78acb04d 
darktable-2.4.4.tar.xz
$ sha256sum darktable-2.4.4.dmg
??? darktable-2.4.4.dmg
$ sha256sum darktable-2.4.4-win64.exe
3763d681de4faa515049daf3dae62ee21812e8c6c206ea7a246a36c0341eca8c 
darktable-2.4.4-win64.exe
$ sha256sum darktable-2.4.4-win64.zip
5dba3423b0889c69f723e378564e084878b20baf3996c349bfc9736bed815067 
darktable-2.4.4-win64.zip
```

when updating from the currently stable 2.2.x series, please bear in mind that 
your edits will be preserved during this process, but it will not be possible 
to downgrade from 2.4 to 2.2.x any more.

 Important note: to make sure that darktable can keep on supporting the 
raw file format for your camera, *please* read [this post](https://
discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri) on how/what raw 
samples you can contribute to ensure that we have the *full* raw sample set 
for your camera under CC0 license!

and the changelog as compared to 2.4.3 can be found below.

## New Features

- Added 50% zoom option in darkroom mode to the navigation dropdown
- perspective correction: usability improvement – allow setting the radius 
when (de)selecting lines

## Bugfixes

- Fix selecting drives in the import dialog on Windows by bundling a patched 
glib
- Add some space between checkbox and label in color picker
- OpenCL: better readability of debug output on memory usage
- Levels: catch an edge case where float != int
- Fix the alignment in a tooltip in lens correction
- Local contrast: Reset strength slider to 120% when double clicked
- Drop unused clone masks when loading xmp files
- Remove all sub masks when clearing cloning masks
- darktable-cltest: do not print summary statistics on OpenCL usage
- Perspective correction: take aspect parameter into account when judging on 
neutral settings
- Haze removal: fix tiled processing
- Fix install on Windows due to GraphicsMagick's versioned filenames
- PPM: Handle byte order when loading files
- Fix #12165: Don't try to show dialog without gui
- Fix an out-of-bounds memory access
- Tools: Fix typo in darktable-gen-noiseprofile that made it unusable
- MacOS package: point gettext to correct localedir

## Camera support, compared to 2.4.2

 Warning: support for Nikon NEF 'lossy after split' raws was 
unintentionally broken due to the lack of such samples. Please see [this post]
(https://discuss.pixls.us/t/nikon-a-specific-raw-sample-wanted/5483?
u=lebedevri) for more details. If you have affected raws, please contribute 
samples!

### White Balance Presets

- Sony ILCE-6500

### Noise Profiles

- Canon EOS 800D
- Canon EOS Kiss X9i
- Canon EOS Rebel T7i
- Nikon COOLPIX B700
- Nikon D5600
- Olympus TG-5

## Updated translations

- German
- Russian


signature.asc
Description: This is a digitally signed message part.