Re: [darktable-dev] darktable 3.6 released

2021-07-07 Thread Solarer
Hi Matthias,
there are 2 ways to delete pictures. You can just remove them from your catalog 
or truely delete them from your disk.

You probably used the first option. That is why they were still inside the 
folder when you moved it and so they showed up again.

Your edits are stored in xmp files. Can you see those? You need to copy them as 
well!

Best, Jan



07.07.2021 08:51:41 Matthias Elsdörfer :

> Quick follow-up... I read through the announcement more thoroughly now and 
> realize that what previously was the "import" button is now the "add to 
> library" button.
> 
> I also found that DT on my laptop still had all the files, so I used DT's own 
> "move" feature to put them back into my home folder.
> 
> I'd still like to know where they were copied to in the first place. I 
> couldn't find that info in your article.
> 
> 
>  
> [https://www.brandartery.com/wp-content/uploads/2019/03/Logo_Design_150.png][Bild-Link][https://www.brandartery.com]
> 
> *Matthias Elsdörfer* · Weitererzähler.
> a.k.a. Matt Eastwood
> 
> Web Design · Fotografie
> Copywriting · Kommunikation
> 
> Website[https://www.brandartery.com/] · Matts 
> Fotografie[https://www.meetmatteastwood.com/]
> Phone: (+49) 170 - 7 555 701
> 
> 
> On 7/7/21 8:32 AM, Matthias Elsdörfer wrote:
>> 
>> Hello, Darktable team!
>> 
>> First of all, thanks so much for this new release, it's always extremely 
>> exciting to hear about one and to test it out. I've been a user since 2013 
>> and the program just keeps getting better.
>> 
>> I do have a problem with the new "Copy and Import" feature though. I worked 
>> through a whole photo session on Monday on my laptop, deleting over 40 
>> pictures and retouching the remaining 30. Then, I moved the whole folder 
>> over to my desktop PC.
>> 
>> When I opened it on my desktop today, I found that the 40 pictures I deleted 
>> were back and all my editing work was gone.
>> 
>> Why? Where did it go? Do my files get copied somewhere when I import them? 
>> What's wrong with keeping them where I put them in the first place?
>> 
>> I hope you can help me make sense of this and, perhaps, recover my 2 hours 
>> of work. I'm hoping it's still somewhere on my laptop.
>> 
>> Thanks,
>> Matt.
>> 
>> 
>>  
>> [https://www.brandartery.com/wp-content/uploads/2019/03/Logo_Design_150.png][Bild-Link][https://www.brandartery.com]
>> 
>> *Matthias Elsdörfer* · Weitererzähler.
>> a.k.a. Matt Eastwood
>> 
>> Web Design · Fotografie
>> Copywriting · Kommunikation
>> 
>> Website[https://www.brandartery.com/] · Matts 
>> Fotografie[https://www.meetmatteastwood.com/]
>> Phone: (+49) 170 - 7 555 701
>> 
>> 
>> On 7/3/21 10:14 AM, Pascal Obry wrote:
>>> We're proud to announce the new feature release of darktable, 3.6.0!
>>> 
>>> The github release is here:
>>> [https://github.com/darktable-org/darktable/releases/tag/release-3.6.0](https://github.com/darktable-org/darktable/releases/tag/release-3.6.0)
>>> .
>>> 
>>> As always, please don't use the autogenerated tarball provided by
>>> github, but only our tar.xz file. the checksums are:
>>> 
>>> ```
>>> $ sha256sum darktable-3.6.0.tar.xz
>>> 86bcd0184af38b93c3688dffd3d5c19cc65f268ecf9358d649fa11fe26c70a39
>>> darktable-3.6.0.tar.xz
>>> $ sha256sum darktable-3.6.0.3.dmg
>>> 12c9319d68dac5b1b5602bf470254467b90f5c5b9d2e93ea081d42884cfd4f80
>>> darktable-3.6.0.3.dmg
>>> $ sha256sum darktable-3.6.0-win64.exe
>>> aad925988545ff3c50f54243520e8481c695b38b209daa808a490113f6400374
>>> darktable-3.6.0-win64.exe
>>> ```
>>> 
>>> When updating from the currently stable 3.4.x series, please bear in
>>> mind that your edits will be preserved during this process, but the new
>>> library and configuration will not be usable with 3.4.x any more.
>>> 
>>> You are strongly advised to take a backup first.
>>> 
>>>  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!
>>> 
>>> - Almost 2680 commits to darktable+rawspeed since 3.4
>>> - 954 pull requests handled
>>> - 290 issues closed
>>> 
>>> ## The Big Ones
>>> 
>>> - Full rework of the import module. The new module allows you to see
>>>   thumbnails of your images before import and makes it easier to handle
>>>   multiple import tasks. The same dialog is now used for importing
>>>   from disk, card or camera.
>>> 
>>>   When importing "in-place", images that are already present in
>>> darktable
>>>   are flagged and can be automatically excluded from the import.
>>> 
>>>   Importing from a local drive won't use gphoto and so should work more
>>>   reliably on Windows.
>>> 
>>> - A vector-scope is added to complement the current histogram,
>>>   waveform and parade views.
>>> 
>>> - A new default demosaic algorithm (RCD) has 

Re: [darktable-dev] darktable 3.6 released

2021-07-07 Thread Matthias Elsdörfer

Thanks, Jan! Yeah, technically, what I did was: I copied the pictures
from my SD card to my /home/Test/ folder, like I always do. Then, I used
"import and copy" in DT and pointed to that folder.

What I didn't realize that 3.6 now actually makes new copies somewhere
else on the file system. That's why I was so surprised later to find all
73 CR2s still there in /home/Test, and no XMP files at all.

What I'm wondering is, where on my file system is the directory that DT
copied my files to and placed my XMPs in?



Matthias Elsdörfer · Weitererzähler.
a.k.a. Matt Eastwood

Web Design · Fotografie
Copywriting · Kommunikation

Website  · Matts Fotografie

Phone: (+49) 170 - 7 555 701

On 7/7/21 9:26 AM, Solarer wrote:

Hi Matthias,
there are 2 ways to delete pictures. You can just remove them from
your catalog or truely delete them from your disk.

You probably used the first option. That is why they were still inside
the folder when you moved it and so they showed up again.

Your edits are stored in xmp files. Can you see those? You need to
copy them as well!

Best, Jan



07.07.2021 08:51:41 Matthias Elsdörfer :

Quick follow-up... I read through the announcement more thoroughly
now and realize that what previously was the "import" button is
now the "add to library" button.

I also found that DT on my laptop still had all the files, so I
used DT's own "move" feature to put them back into my home folder.

I'd still like to know where they were copied to in the first
place. I couldn't find that info in your article.



Matthias Elsdörfer · Weitererzähler.
a.k.a. Matt Eastwood

Web Design · Fotografie
Copywriting · Kommunikation

Website  · Matts Fotografie

Phone: (+49) 170 - 7 555 701

On 7/7/21 8:32 AM, Matthias Elsdörfer wrote:


Hello, Darktable team!

First of all, thanks so much for this new release, it's always
extremely exciting to hear about one and to test it out. I've
been a user since 2013 and the program just keeps getting better.

I do have a problem with the new "Copy and Import" feature
though. I worked through a whole photo session on Monday on my
laptop, deleting over 40 pictures and retouching the remaining
30. Then, I moved the whole folder over to my desktop PC.

When I opened it on my desktop today, I found that the 40
pictures I deleted were back and all my editing work was gone.

Why? Where did it go? Do my files get copied somewhere when I
import them? What's wrong with keeping them where I put them in
the first place?

I hope you can help me make sense of this and, perhaps, recover
my 2 hours of work. I'm hoping it's still somewhere on my laptop.

Thanks,
Matt.



Matthias Elsdörfer · Weitererzähler.
a.k.a. Matt Eastwood

Web Design · Fotografie
Copywriting · Kommunikation

Website  · Matts Fotografie

Phone: (+49) 170 - 7 555 701

On 7/3/21 10:14 AM, Pascal Obry wrote:

We're proud to announce the new feature release of darktable, 3.6.0!

The github release is here:

[https://github.com/darktable-org/darktable/releases/tag/release-3.6.0](https://github.com/darktable-org/darktable/releases/tag/release-3.6.0)
.

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

```
$ sha256sum darktable-3.6.0.tar.xz
86bcd0184af38b93c3688dffd3d5c19cc65f268ecf9358d649fa11fe26c70a39
darktable-3.6.0.tar.xz
$ sha256sum darktable-3.6.0.3.dmg
12c9319d68dac5b1b5602bf470254467b90f5c5b9d2e93ea081d42884cfd4f80
darktable-3.6.0.3.dmg
$ sha256sum darktable-3.6.0-win64.exe
aad925988545ff3c50f54243520e8481c695b38b209daa808a490113f6400374
darktable-3.6.0-win64.exe
```

When updating from the currently stable 3.4.x series, please bear in
mind that your edits will be preserved during this process, but the new
library and configuration will not be usable with 3.4.x any more.

You are strongly advised to take a backup first.

 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!

- Almost 2680 commits to darktable+rawspeed since 3.4
- 954 pull requests handled
- 290 issues closed

## The Big Ones

- Full rework of the import module. The new module 

Re: [darktable-dev] darktable 3.6 released

2021-07-07 Thread Matthias Elsdörfer

Quick follow-up... I read through the announcement more thoroughly now
and realize that what previously was the "import" button is now the "add
to library" button.

I also found that DT on my laptop still had all the files, so I used
DT's own "move" feature to put them back into my home folder.

I'd still like to know where they were copied to in the first place. I
couldn't find that info in your article.



Matthias Elsdörfer · Weitererzähler.
a.k.a. Matt Eastwood

Web Design · Fotografie
Copywriting · Kommunikation

Website  · Matts Fotografie

Phone: (+49) 170 - 7 555 701

On 7/7/21 8:32 AM, Matthias Elsdörfer wrote:


Hello, Darktable team!

First of all, thanks so much for this new release, it's always
extremely exciting to hear about one and to test it out. I've been a
user since 2013 and the program just keeps getting better.

I do have a problem with the new "Copy and Import" feature though. I
worked through a whole photo session on Monday on my laptop, deleting
over 40 pictures and retouching the remaining 30. Then, I moved the
whole folder over to my desktop PC.

When I opened it on my desktop today, I found that the 40 pictures I
deleted were back and all my editing work was gone.

Why? Where did it go? Do my files get copied somewhere when I import
them? What's wrong with keeping them where I put them in the first place?

I hope you can help me make sense of this and, perhaps, recover my 2
hours of work. I'm hoping it's still somewhere on my laptop.

Thanks,
Matt.



Matthias Elsdörfer · Weitererzähler.
a.k.a. Matt Eastwood

Web Design · Fotografie
Copywriting · Kommunikation

Website  · Matts Fotografie

Phone: (+49) 170 - 7 555 701

On 7/3/21 10:14 AM, Pascal Obry wrote:

We're proud to announce the new feature release of darktable, 3.6.0!

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

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

```
$ sha256sum darktable-3.6.0.tar.xz
86bcd0184af38b93c3688dffd3d5c19cc65f268ecf9358d649fa11fe26c70a39
darktable-3.6.0.tar.xz
$ sha256sum darktable-3.6.0.3.dmg
12c9319d68dac5b1b5602bf470254467b90f5c5b9d2e93ea081d42884cfd4f80
darktable-3.6.0.3.dmg
$ sha256sum darktable-3.6.0-win64.exe
aad925988545ff3c50f54243520e8481c695b38b209daa808a490113f6400374
darktable-3.6.0-win64.exe
```

When updating from the currently stable 3.4.x series, please bear in
mind that your edits will be preserved during this process, but the new
library and configuration will not be usable with 3.4.x any more.

You are strongly advised to take a backup first.

 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!

- Almost 2680 commits to darktable+rawspeed since 3.4
- 954 pull requests handled
- 290 issues closed

## The Big Ones

- Full rework of the import module. The new module allows you to see
   thumbnails of your images before import and makes it easier to handle
   multiple import tasks. The same dialog is now used for importing
   from disk, card or camera.

   When importing "in-place", images that are already present in
darktable
   are flagged and can be automatically excluded from the import.

   Importing from a local drive won't use gphoto and so should work more
   reliably on Windows.

- A vector-scope is added to complement the current histogram,
   waveform and parade views.

- A new default demosaic algorithm (RCD) has been introduced, which
should provide
   better quality than the current default (PPG) without the long run-
times
   of AMaZE. the order of the demosaic algorithms has also been adjusted
for clarity.

- Support for "dual demosaic" has also been added, allowing you to
combine
   "RCD + VNG4" and "AMaZE + VNG4" for bayer sensors, for xtrans sensors
there is
   "Markesteijn 3-pass + VNG". This allows you to use an algorithm
better resolving
   fine detail and another one delivering smoother output depending on
local image content.

- You can now create an opacity mask based on the sharpness of the
image. This uses
   a similar algorithm to that used in dual demosaic.

- Drawn shapes are drawn on the original RAW image and then distorted
through
   the pixelpipe. This previously led to, for example, circles becoming
ellipses
   (due to lens distortion) after being placed on the image. All drawn
shapes can
   now be pre-visualized and moved prior to placement, with full
deformation
   applied. This makes the 

Re: [darktable-dev] darktable 3.6 released

2021-07-07 Thread Matthias Elsdörfer

Hello, Darktable team!

First of all, thanks so much for this new release, it's always extremely
exciting to hear about one and to test it out. I've been a user since
2013 and the program just keeps getting better.

I do have a problem with the new "Copy and Import" feature though. I
worked through a whole photo session on Monday on my laptop, deleting
over 40 pictures and retouching the remaining 30. Then, I moved the
whole folder over to my desktop PC.

When I opened it on my desktop today, I found that the 40 pictures I
deleted were back and all my editing work was gone.

Why? Where did it go? Do my files get copied somewhere when I import
them? What's wrong with keeping them where I put them in the first place?

I hope you can help me make sense of this and, perhaps, recover my 2
hours of work. I'm hoping it's still somewhere on my laptop.

Thanks,
Matt.



Matthias Elsdörfer · Weitererzähler.
a.k.a. Matt Eastwood

Web Design · Fotografie
Copywriting · Kommunikation

Website  · Matts Fotografie

Phone: (+49) 170 - 7 555 701

On 7/3/21 10:14 AM, Pascal Obry wrote:

We're proud to announce the new feature release of darktable, 3.6.0!

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

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

```
$ sha256sum darktable-3.6.0.tar.xz
86bcd0184af38b93c3688dffd3d5c19cc65f268ecf9358d649fa11fe26c70a39
darktable-3.6.0.tar.xz
$ sha256sum darktable-3.6.0.3.dmg
12c9319d68dac5b1b5602bf470254467b90f5c5b9d2e93ea081d42884cfd4f80
darktable-3.6.0.3.dmg
$ sha256sum darktable-3.6.0-win64.exe
aad925988545ff3c50f54243520e8481c695b38b209daa808a490113f6400374
darktable-3.6.0-win64.exe
```

When updating from the currently stable 3.4.x series, please bear in
mind that your edits will be preserved during this process, but the new
library and configuration will not be usable with 3.4.x any more.

You are strongly advised to take a backup first.

 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!

- Almost 2680 commits to darktable+rawspeed since 3.4
- 954 pull requests handled
- 290 issues closed

## The Big Ones

- Full rework of the import module. The new module allows you to see
   thumbnails of your images before import and makes it easier to handle
   multiple import tasks. The same dialog is now used for importing
   from disk, card or camera.

   When importing "in-place", images that are already present in
darktable
   are flagged and can be automatically excluded from the import.

   Importing from a local drive won't use gphoto and so should work more
   reliably on Windows.

- A vector-scope is added to complement the current histogram,
   waveform and parade views.

- A new default demosaic algorithm (RCD) has been introduced, which
should provide
   better quality than the current default (PPG) without the long run-
times
   of AMaZE. the order of the demosaic algorithms has also been adjusted
for clarity.

- Support for "dual demosaic" has also been added, allowing you to
combine
   "RCD + VNG4" and "AMaZE + VNG4" for bayer sensors, for xtrans sensors
there is
   "Markesteijn 3-pass + VNG". This allows you to use an algorithm
better resolving
   fine detail and another one delivering smoother output depending on
local image content.

- You can now create an opacity mask based on the sharpness of the
image. This uses
   a similar algorithm to that used in dual demosaic.

- Drawn shapes are drawn on the original RAW image and then distorted
through
   the pixelpipe. This previously led to, for example, circles becoming
ellipses
   (due to lens distortion) after being placed on the image. All drawn
shapes can
   now be pre-visualized and moved prior to placement, with full
deformation
   applied. This makes the editing of masks easier fully WYSIWYG.

- A new Color Balance RGB module has been added. This can be used as a
one stop module
   for all color grading work.

- A new censorize module has been added. This allows you to hide parts
of the image by adding
   a blur/pixelization.

- A new crop module has been added. This new module has been added late
in the
   pixelpipe and makes it possible to use cropped parts of the image for
source spots
   in the retouch module, for example.

- A new section has been added to the color calibration module to allow
you to calibrate
   colors using a color checker chart.

- The map module has been enhanced in a number of ways:
   - When importing a GPX the trace can be displayed.
   - 

Re: [darktable-dev] darktable 3.6 released

2021-07-05 Thread Peter Schlaufer
thank you for this fantastic work

peter switzerland

> Am 03.07.2021 um 10:14 schrieb Pascal Obry :
> 
> We're proud to announce the new feature release of darktable, 3.6.0!
> 
> The github release is here:
> [https://github.com/darktable-org/darktable/releases/tag/release-3.6.0](https://github.com/darktable-org/darktable/releases/tag/release-3.6.0)
> .
> 
> As always, please don't use the autogenerated tarball provided by
> github, but only our tar.xz file. the checksums are:
> 
> ```
> $ sha256sum darktable-3.6.0.tar.xz
> 86bcd0184af38b93c3688dffd3d5c19cc65f268ecf9358d649fa11fe26c70a39
> darktable-3.6.0.tar.xz
> $ sha256sum darktable-3.6.0.3.dmg
> 12c9319d68dac5b1b5602bf470254467b90f5c5b9d2e93ea081d42884cfd4f80
> darktable-3.6.0.3.dmg
> $ sha256sum darktable-3.6.0-win64.exe
> aad925988545ff3c50f54243520e8481c695b38b209daa808a490113f6400374
> darktable-3.6.0-win64.exe
> ```
> 
> When updating from the currently stable 3.4.x series, please bear in
> mind that your edits will be preserved during this process, but the new
> library and configuration will not be usable with 3.4.x any more.
> 
> You are strongly advised to take a backup first.
> 
>  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!
> 
> - Almost 2680 commits to darktable+rawspeed since 3.4
> - 954 pull requests handled
> - 290 issues closed
> 
> ## The Big Ones
> 
> - Full rework of the import module. The new module allows you to see
>  thumbnails of your images before import and makes it easier to handle
>  multiple import tasks. The same dialog is now used for importing
>  from disk, card or camera.
> 
>  When importing "in-place", images that are already present in
> darktable
>  are flagged and can be automatically excluded from the import.
> 
>  Importing from a local drive won't use gphoto and so should work more
>  reliably on Windows.
> 
> - A vector-scope is added to complement the current histogram,
>  waveform and parade views.
> 
> - A new default demosaic algorithm (RCD) has been introduced, which
> should provide
>  better quality than the current default (PPG) without the long run-
> times
>  of AMaZE. the order of the demosaic algorithms has also been adjusted
> for clarity.
> 
> - Support for "dual demosaic" has also been added, allowing you to
> combine
>  "RCD + VNG4" and "AMaZE + VNG4" for bayer sensors, for xtrans sensors
> there is
>  "Markesteijn 3-pass + VNG". This allows you to use an algorithm
> better resolving
>  fine detail and another one delivering smoother output depending on
> local image content.
> 
> - You can now create an opacity mask based on the sharpness of the
> image. This uses
>  a similar algorithm to that used in dual demosaic.
> 
> - Drawn shapes are drawn on the original RAW image and then distorted
> through
>  the pixelpipe. This previously led to, for example, circles becoming
> ellipses
>  (due to lens distortion) after being placed on the image. All drawn
> shapes can
>  now be pre-visualized and moved prior to placement, with full
> deformation
>  applied. This makes the editing of masks easier fully WYSIWYG.
> 
> - A new Color Balance RGB module has been added. This can be used as a
> one stop module
>  for all color grading work.
> 
> - A new censorize module has been added. This allows you to hide parts
> of the image by adding
>  a blur/pixelization.
> 
> - A new crop module has been added. This new module has been added late
> in the
>  pixelpipe and makes it possible to use cropped parts of the image for
> source spots
>  in the retouch module, for example.
> 
> - A new section has been added to the color calibration module to allow
> you to calibrate
>  colors using a color checker chart.
> 
> - The map module has been enhanced in a number of ways:
>  - When importing a GPX the trace can be displayed.
>  - Location can be set using polygons and directly created from
> information
>reported by Open Street Map. As a reminder, all locations
>create tags automatically for images placed into the area.
> 
> - The basic adjustments module has been replaced with the quick access
> panel, which
>  can be used to group controls from multiple different modules in one
> place. Currently,
>  only non-graphical controls (sliders, comboboxes etc.) can be used.
> 
> ## Other New Features And Changes
> 
> - The various lighttable modes can now be accessed via clear and
> descriptive icons
>  at the bottom of the screen. These should be easier to use than the
> existing drop-down
>  selection.
> 
> - The export module is now also accessible on the left-hand panel of
> the
>  darkroom view.
> 
> - The mix control in the contrast equalizer module is now retained as
>  module parameter. This means that no data is lost