The .thm solution is outdated and hasn't received as much attention as the mechanism currently used to display thumbnails, and that's using JPEG images stored under .jalbum/cache. You should basically not need to rely on .thm files anymore, at least not for videos.
David,
This is both a good thing and a somewhat confusing thing. Firstly, I hate the thm files residing in my source data (as you know, I like to keep source and project data separate). I have a very large collection of processed video files, ie I have already created the thumbnail I would like to see that suits the particular video. These
thm files only exist for jAlbum, so putting them in the project area would be a good thing.
If the
thm files exist in the correct project folder, they are used as expected. So there is a one-off requirement (when I’m using links) to move them from the source to relevant
Project folder. In addition, jAlbum creates standard, default thumbnails
jpg files in the cache folder. Whenever I Make, these cache files are re-created/refreshed.
I have experimented, and I keep coming up against an issue. The cache (as one might expect) is overwritten as decided by jAlbum. If I rename the
thm to
jpg, and put them in the cache folder, they are overwritten when I refresh the GUI.
The only way I can get the cache files to be permanent is to re-create a thumbnail image via the Edit window. After that, even if I put back the thm files and re-Make (actually, I have to
Force Remake), the GUI-created cache images remain (though the album, of course) uses the thm thumbnails.
So at the moment, I still see the thm files as being essential, in that they are easy to locate in the project (not buried down a few levels) and won’t be inadvertently overwritten when maybe just playing around.
Am I missing something?
Mark
Edited by: MarkE on 28-Nov-2020 17:16
And a lot of unnecessary jpgs in the cache folder!
