Filtering collections based on exposure using relative operators

I am trying to filter an image collection based on exposure using the relative operators.

If I filter on ISO using: <=320
I get a correct list of images with ISO 320 or less.

Similarly, Aperture also works.

If I filter on Exposure using: <=1/250, it is ignored.

My assumption is that the exposure is not being interpreted as numerical fractions in a way that would support the relative operators.

Hi, I don’t reproduce with dt 5.2.1 on Ubuntu 24.

When I filter on Exposure <=1/500 the lightroom display photos from 1/500 to 1/x000 which are speeds lower than 1/500 as intended.

And when it’s >=1/500 the photos from 1/500 to 1/4 (or longer).

I chatted with Bruce Williams on Facebook and he also could not replicate, but I have spent a lot of time on this and haven’t been able to get it to work. Running on Windows 11.

Ok, so it could be that the filter is being used as a second or third level.

I cleared the filter, and it seems to work as a top-level filter.

Something funky is happening and it now works - kinda.

The collection I have has:
1/100 (3)
1/200 (4)
1/2000 (82)
1/2500 (7)

If I specify >=1/200, I expect to see 7 images. I only get the three shots at 1/100. If I specify >=1/250, I get the 7 images.

This is different to what I have been seeing which the criteria was being ignored.

I tested with the Exposure filter as 2nd following (and) a Keyword filter.

@DominusFulguris Andrew, which dt build are you using?

I’m on Windows 11, using the nightly builds.

I have tried this on

  • darktable-5.3.0+946.ge8b378d586-win64
  • darktable-5.3.0+949.g610a60488b-win64

I too am getting strange results.

In the collection filters module, when using the slider to select exposure of 1/7 → 1/6

this is what it shows up in build 5.3.0+949.g610a60488b-win64

and this is what it shows up in build 5.3.0+946.ge8b378d586-win64

You’ll notice several problems. I’m not the biggest maths guy in the world, but 1/7 and 1/6 I think do not equal what darktable thinks it equals. And, depending on the nightly version of dt, it associates two different decimal values for 1/7 and 1/6. Unless there is something I’m missing/not understanding.

This image above also shows there are supposedly 19 images from 1/7 → 1/6.

Next, you’ll see that according to the collections module, the left panel shows I have a total of 82 1/7 & 1/6 exposure images, but the current view claims there are 0 such images (no, there are no other collections or filters set):

If I choose just 1/6 exposure, the collections module claims there are 51 such images and the current images views shows only 43 of those 51 (no, there are no other collections or filters set):

Next, looking at a different exposure collection, we have these problems: