Credit where credit is due, this must be the best tagging software out there, however, you NEED to come up with a better solution than adding a ton of bloat to the system with these .ts thumbnail files. Not to mention, it duplicates everything in a simple explorer file search. Feels super sloppy. Use built-in system thumbnails or add an option to generate them as needed in memory temporarily, or at the very least, an option to hide them as that at least solves the search issue while keeping hidden files hidden from explorer.
Hi @Chaothicc , and thanks for your feedback. The .ts folders have the advantage that they save all the tags, thumbnails and description for the files in the main folders. This makes the tagged files easy to copy, move, sync and backup. With the .ts folders the app creates a kind of decentralized storage for the meta-data of your files.
On MacOS and Linux the .ts folders are hidden by default, on Windows the app sets a special attribute which should hide this folders, unless you explicitly makes Windows Explorer to show hidden files and folders.
Generating thumbnails on the fly will slow down the app, imagine opening a folder with 100 photos, and the app have to open all this files every time you open this folder. Now the photos are opened only the first you open this folder.
tbh i agree with author, i want to see 1 folder and 1 file with tags, its much easier to backup and dont flood million folders with another folders and files…
That’s debatable. If you want to backup specific files only, having separate sidecar files is much easier to handle than one collected file (same as with xmp sidecars for images).
The approach to collect would almost be like a collected database already which has some advantages but isn’t without disadvantages.
Great would be if all file types would handle metadata the same and would include tags and descriptions but as this isn’t the case, there always will be workarounds that come with compromises.
For some file managers that means you have to import files first (breaking file structures, making it harder to handle files on a file system level), collecting data in a database (making it harder to backup only part of the data and could be a problem when this database gets corrupted, some DAM tools link to files and work only with proxies.
The best approach I’ve seen so far is indexing with checksum and automatic relinking of the metadata when files are moved elsewhere but even that has some disadvantages as indexing takes more time.
So really the best approach how this is handled, is tied to your needs. An ultimate solution (like having tagging data stored into files themselves) doesn’t exist unfortunately.
(And even if this kind of data could be stored into files, it would still not be ultimate because the original file would be modified which is not always something you want either, when I think about archiving)