Lighttable: Add number of images in group near the group icon
When managing bracket shots or panorama sequences it is helpful to know how many images are in an existing group. For example bracketed shots, at least with my camera, come with an odd number of images. It would be nice, to be able to check that easily.
Describe the solution you'd like
Display the number of images each group near the groups icon like this (red only choosen for this demonstration):
Alternatives I dont see any.
Additional context None.
You already get this information by selecting the collapsed group
The mouse-over tooltip on the group icon of each thumbnail gives the number of images in that group.
Thanks for the comments. Thats all correct, but my idea is that in the lightroom view, with one glance, I see the counts for each group. I am starting to use the autogroup lua-script. with that, as it only uses the time difference between shots to form groups, it often happens, that images are grouped which are shot in short sequence, but are not in a bracket.
Actually I am trying to find a way to easily identify images which are part of an HDR-bracket. The suggestion is just a way to make that easier.
May be a more intelligent autogroup script could solve the problem also. Something like:
- images in short sequence
- plus taken with different exposures
- plus optionally, it has to be an odd number of images in the group
it often happens, that images are grouped which are shot in short sequence, but are not in a bracket.
But simply showing the number of images in a group will not make it possible to accurately determine whether these images are bracketed. Indeed, to solve your problem, the script needs to be modified.
This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
This issue was closed because it has been inactive for 300 days since being marked as stale. Please check if the newest release or nightly build has it fixed. Please, create a new issue if the issue is not fixed.