I would like to find all the pictures I have taken with a specific aperture, says F/16 for example.
But it seems impossible to get this with the current advanced search: - if I put only one value, Digikam considers it as a minimum or a maximum, depending on which field I put the value in - if I try to put two values, one for the minimum, the other for the maximum, Digikam prevents me to put the same value in both fields. So I can either get aperture less or equal to F/16, or greater or equal to F/16; but it seems impossible to get only the pictures with a F/16 value. Am I missing something? Or the criteria entry controls are a bit too constraining? Marie-Noëlle -- Mes dernières photos sont dans ma galerie. Retrouvez-moi aussi sur mon blog. Et parcourez les Cévennes à ma façon avec Cévennes Plurielles, _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tue, 6 Nov 2012, Marie-Noëlle Augendre wrote: > I would like to find all the pictures I have taken with a specific > aperture, says F/16 for example. > But it seems impossible to get this with the current advanced search: > - if I put only one value, Digikam considers it as a minimum or a maximum, > depending on which field I put the value in > - if I try to put two values, one for the minimum, the other for the > maximum, Digikam prevents me to put the same value in both fields. > > So I can either get aperture less or equal to F/16, or greater or equal to > F/16; but it seems impossible to get only the pictures with a F/16 value. > > Am I missing something? Or the criteria entry controls are a bit too > constraining? I don't think the search criteria are too restricted. It seems that the « editing help » logic is too ... sophisticated :-) (Or too simple) Try to type, as a min value, the value : 15 The field editor completes your input and change it in : f/15.0 Now move the cursor till end, erase the trailing 0 and replace by 9, you get : f/15.9 Same trick for the max value, you can input f/16.1 Then you'll find all your pictures taken with an aperture in range [15.9 - 16.1] and it will mostly (or only) be f/16. Regards, Jean-François _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Good trick! Thank you Jean-François.
I had the impression Digikam only knew the "real" values as it goes from f/8 to f/11 and such when I used the '+' and '-' keys; it probably automatically proposes the values that are available in the pictures recorded in its database. Marie-Noëlle 2012/11/6 Jean-François Rabasse <[hidden email]>
-- Mes dernières photos sont dans ma galerie. Retrouvez-moi aussi sur mon blog. Et parcourez les Cévennes à ma façon avec Cévennes Plurielles, _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tue, 6 Nov 2012, Marie-Noëlle Augendre wrote: > Good trick! Thank you Jean-François. > > I had the impression Digikam only knew the "real" values as it goes from > f/8 to f/11 and such when I used the '+' and '-' keys; it probably > automatically proposes the values that are available in the pictures > recorded in its database. Well, not exactly. The field editor logic, when using the '+' or '-' keys or the spin buttons, loops on the standard values serie, 4, 5.6, 8, 11, 16, 22, etc. This uses plus or minus 1 EV increments. Perhaps plus or minus 1/3 EV should be more suitable and more close to cameras settings. (The ISO sensitivity field uses +- 1/3 EV, e.g. 800, 1000, 1250, 1600, and not just 800, 1600.) But all this is just typing help and as long as it's possible to input user typed values, things are Ok. From my point of view, what is a real restriction is that input is locked into a predefined range of values. For aperture setting, the max value is f/128.0 and this is probably ok for most lenses. But the ISO setting field limits to 6400, and the exposure time field limits to 1/1000s. With somewhat strange behaviour, if you try to input 1/2000s, the editing corrects into 1/2s :-( Maybe this should go on a wish list, as with modern cameras, values of ISO 12800, or 1/2000s shutter speed are possible and there seems to be no way to do searches for such values. And a wish list should also consider what you mentionned, i.e. the possibility of setting the same value as mini and maxi. Regards, Jean-François _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Interesting information, I was not aware of all of this as it is the first time I use this kind of parameters in the advanced search.
And why any edit check in this kind of fields, by the way? It'll be more convenient (and easy for the developers I guess) to let the user enter whatever values he/she wants. At worst, there will be no result! Marie-Noëlle 2012/11/6 Jean-François Rabasse <[hidden email]>
-- Mes dernières photos sont dans ma galerie. Retrouvez-moi aussi sur mon blog. Et parcourez les Cévennes à ma façon avec Cévennes Plurielles, _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by tosca
Þann þri 6.nóv 2012 09:20, skrifaði Jean-François Rabasse:
> Maybe this should go on a wish list, as with modern cameras, > values > of ISO 12800, or 1/2000s shutter speed are possible and > there seems > to be no way to do searches for such values. Not to mention astronomical and other scientific imagery ;-) Regards, Sveinn í Felli _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
In reply to this post by tosca
On Tue, 6 Nov 2012, Marie-Noëlle Augendre wrote: > And why any edit check in this kind of fields, by the way? It'll be more > convenient (and easy for the developers I guess) to let the user enter > whatever values he/she wants. At worst, there will be no result! I agree. There's no technical reason to bound input values into a fixed range, as a database selection is something like : select ... where value >= mini and value <= maxi So, as you say, if users input stupid values, the search will answer : No images ! Wish list : please, remove these restrictions in a future release :) Jean-François _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
No time to do it just now. Either you register it (and I will vote for it !), or I'll do it sometime in the evening.
Marie-Noëlle 2012/11/6 Jean-François Rabasse <[hidden email]>
-- Mes dernières photos sont dans ma galerie. Retrouvez-moi aussi sur mon blog. Et parcourez les Cévennes à ma façon avec Cévennes Plurielles, _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Tue, 6 Nov 2012, Marie-Noëlle Augendre wrote: > No time to do it just now. Either you register it (and I will vote for it > !), or I'll do it sometime in the evening. Done -> [309638] Jean-François _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Voted.
Here is the complete link for those who would like to vote: https://bugs.kde.org/show_bug.cgi?id=309638 Marie-Noëlle -- Mes dernières photos sont dans ma galerie. Retrouvez-moi aussi sur mon blog. Et parcourez les Cévennes à ma façon avec Cévennes Plurielles, _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
2012/11/6 Marie-Noëlle Augendre <[hidden email]> Voted. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |