Closed mrRo8o7 closed 1 month ago
It would be interesting to see the details of the other file IMG_6199.JPG
underneath as well. I also noticed that the actual folders seem to be different from the example file structure you provided. All in all, this is not enough information to help with troubleshooting as we do not have the resources to create our own sample files and directories based on your screenshots. Could you provide us with a zip file with 3 sample files located in the same folders as in your library so we can try to reproduce your problem?
Thank you very much!
Please also note that files that were already indexed (i.e. stacked before you moved them) will not be unstacked if you change their name or folder.
It would be interesting to see the details of the other file
IMG_6199.JPG
underneath as well. I also noticed that the actual folders seem to be different from the example file structure you provided. All in all, this is not enough information to help with troubleshooting as we do not have the resources to create our own sample files and directories based on your screenshots. Could you provide us with a zip file with 3 sample files located in the same folders as in your library so we can try to reproduce your problem?Thank you very much!
Of course I will send you a sample. Yes, because the file structure was an example.
Please also note that files that were already indexed (i.e. stacked before you moved them) will not be unstacked if you change their name or folder.
All right. The photos were never in the same folder or were moved after indexing. Yes, unfortunately I now have the problem that I can no longer get them unstacked. I don't want to reset my database either, as we have already sorted the photos into albums.
Thank you very much.
Thank you @lastzero. I was able to solve the problem by not using German umlauts in my Originals path.
Another small update. The problem was that I forgot the character set and collation when creating the table
CREATE DATABASE photoprism CHARACTER SET = 'utf8mb4' COLLATE = 'utf8mb4_unicode_ci';)
as described here: https://docs.photoprism.app/getting-started/advanced/databases/
1. What is not working as documented?
When I index my originals folders, photos and videos (live photos) with the same name are stacked despite the fact that the photos are in different subfolders. As a result, I sometimes see the wrong live photo when I move the mouse pointer over a photo.
The documentation says that only files with the same name and in the same folder (i.e. with different file extensions) are stacked to enable Live Photos. When I export photos from different iPhones to separate folders, they often have the same name. I don't think this is the desired behavior of Photoprism.
2. How can we reproduce it?
Steps to reproduce the behavior:
Amount of originals: 31601 Config options: I have tried disabling sequential name stacking and metadata stacking without success.
3. What behavior do you expect?
Photos / videos (live photos) from different folders should not be stacked.
4. What could be the cause of your problem?
I think this is an implementation problem.
5. Can you provide us with example files for testing, error logs, or screenshots?
File structure: USA/iPhoneA/IMG_6199.JPG USA/iPhoneB/IMG_6199.JPG USA/iPhoneB/IMG_6199.MOV
6. Which software versions do you use?
(a) PhotoPrism Architecture & Build Number: Unraid CA Docker, PhotoPrism CE Build 240523-923ee0cf7
(b) Database Type & Version: MariaDB 10.11.6-MariaDB-log
(c) Operating System Types & Versions: Linux (Unraid)
(d) Browser Types & Versions: Firefox