stack multiple takes of a scene #1937

Closed
opened 2026-02-20 01:02:44 -05:00 by deekerman · 2 comments
Owner

Originally created by @gertjanvanzwieten on GitHub (Oct 23, 2023).

Describe what problem this solves and why this would be valuable to many users

I often take a few photos of a scene so that I can select my favorite later. I might not always get to this pruning step, though, so the many near duplicates end up forming awkward clusters in the timeline view.

Describe the solution you'd like

The stacking concept already in place is currently limited to exact duplicates and edits. I would love to see this optionally relaxed by making the temporal and spatial identification windows configurable. Ideally this is paired with the ability to select a favourite to represent the stack, and the ability to break up stacks that were wrongly identified by the heuristic.

Describe alternatives you've considered

I could not think of another way to deal with the situation of near duplicates but I imagine it to be a fairly common problem, so I would be happy to learn of a different solution if it exists.

Originally created by @gertjanvanzwieten on GitHub (Oct 23, 2023). **Describe what problem this solves and why this would be valuable to many users** I often take a few photos of a scene so that I can select my favorite later. I might not always get to this pruning step, though, so the many near duplicates end up forming awkward clusters in the timeline view. **Describe the solution you'd like** The stacking concept already in place is currently limited to exact duplicates and edits. I would love to see this optionally relaxed by making the temporal and spatial identification windows configurable. Ideally this is paired with the ability to select a favourite to represent the stack, and the ability to break up stacks that were wrongly identified by the heuristic. **Describe alternatives you've considered** I could not think of another way to deal with the situation of near duplicates but I imagine it to be a fairly common problem, so I would be happy to learn of a different solution if it exists.
deekerman 2026-02-20 01:02:44 -05:00
  • closed this issue
  • added the
    idea
    label
Author
Owner

@graciousgrey commented on GitHub (Oct 23, 2023):

Thank you very much for your feedback!

The stacking concept already in place is currently limited to exact duplicates and edits. I would love to see this optionally relaxed by making the temporal and spatial identification windows configurable.

We do have a very similar feature request:

It might also make sense to add an option to stack by "time" & "camera" in addition to "time" & "place".

Ideally this is paired with the ability to select a favourite to represent the stack

You can choose the primary file of a stack as described here

the ability to break up stacks that were wrongly identified by the heuristic

Unstacking files one by one is already possible. Unstacking all files of a stack at once is planned:

@graciousgrey commented on GitHub (Oct 23, 2023): Thank you very much for your feedback! > The stacking concept already in place is currently limited to exact duplicates and edits. I would love to see this optionally relaxed by making the temporal and spatial identification windows configurable. We do have a very similar feature request: - https://github.com/photoprism/photoprism/issues/1446 It might also make sense to add an option to stack by "time" & "camera" in addition to "time" & "place". > Ideally this is paired with the ability to select a favourite to represent the stack You can choose the primary file of a stack as described [here](https://docs.photoprism.app/user-guide/organize/stacks/#change-primary-files) > the ability to break up stacks that were wrongly identified by the heuristic [Unstacking files one by one is already possible](https://docs.photoprism.app/user-guide/organize/stacks/#unstack-files). Unstacking all files of a stack at once is planned: - https://github.com/photoprism/photoprism/issues/667
Author
Owner

@gertjanvanzwieten commented on GitHub (Oct 23, 2023):

Thanks for the pointers and suggestions, yes "time & camera" would be excellent if time can be configurable. And indeed #1446 covers the ground already, apologies for failing to find it. I will close my issue in favour of that one.

Edit to add: thanks for photoprism! I like it quite a bit.

@gertjanvanzwieten commented on GitHub (Oct 23, 2023): Thanks for the pointers and suggestions, yes "time & camera" would be excellent if time can be configurable. And indeed #1446 covers the ground already, apologies for failing to find it. I will close my issue in favour of that one. Edit to add: thanks for photoprism! I like it quite a bit.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/photoprism#1937
No description provided.