Normal
While thinking about this I had the following idea: we give the user an option to decide between the "small" EXIF thumbs and the "big" MP thumbs.For option 1 (EXIF) the EXIF thumbs will used whenever they exist in a file, only when there is no thumb available, the MP thumb generator starts to create one, which is used then. If a file has exif thumbs no "big" MP thumbs are ever used.For option 2 the best solution would be a section in the configuration program that generates thumbs for all your shares. Like the building of the music db is done already. So you could start this, leave MP alone once for some time, but then you'll have all thumbs ready. For monitoring shares for new picures there is something like the music share watcher. It creates the "big" MP thumbs in the background with a very low priority. If a user enters a folder with no big thumbs created yet, he will see the EXIF thumbs like in option 1.I hope at least somebody can follow my thoughts What do you think?Maschine
While thinking about this I had the following idea: we give the user an option to decide between the "small" EXIF thumbs and the "big" MP thumbs.
For option 1 (EXIF) the EXIF thumbs will used whenever they exist in a file, only when there is no thumb available, the MP thumb generator starts to create one, which is used then. If a file has exif thumbs no "big" MP thumbs are ever used.
For option 2 the best solution would be a section in the configuration program that generates thumbs for all your shares. Like the building of the music db is done already. So you could start this, leave MP alone once for some time, but then you'll have all thumbs ready. For monitoring shares for new picures there is something like the music share watcher. It creates the "big" MP thumbs in the background with a very low priority. If a user enters a folder with no big thumbs created yet, he will see the EXIF thumbs like in option 1.
I hope at least somebody can follow my thoughts What do you think?
Maschine