helgeerbe
commented
1 week ago Hm, you could cancel picframe, copy images, resart picframe.
Or you could run 'touch' on the copied filed. If I remember right picframe, will reimport the meta data.
The contents of the file will not be lost, and it won't even be modified. The only thing that happens when you run touch on an already existing file is that the file's access and modification timestamps are updated to the current time.
When attempting to add new images to picframe, the application will correctly identify new images to process, but the process appears to fail.
The new images appear in the database with the fname, last_modified, file_id, orientation, and exif_datetime added, but no other information is inserted despite these image files having a large amount of EXIF data.
When imported, and added to the DB, the new images are also never displayed.
The only solution is the delete the DB and have it rebuilt, but then obviously it doesn't display newly added images first, which is what I want.
Ive checked file/folder permissions, file corruption etc.
I suspect the error occurs as a result of the slow network copy operation into the Pictures folder. Watching the tail output of the log, these checks for new images were happening regularly, and thus they were occurring while the file was still copying over from a network location. But I am not sure how to solve this.
Raspberry Pi 4B 4GB OS and all software (lastest/stable) for this frame was pulled within the last 3 weeks.
Debug log output: