David: could a damaged manifest file trigger something like this? It might not actually be uploading everything again, but the process of checking files one at a time can be pretty pokey.
SharpByCoop: connect to your server with something like FileZilla, or go into the cPanel File Manager on your hosting account, and take a look at the timestamps on some of the older, unchanged slide images. Are they actually new file dates?
I AM paying close attention to this issue, but it's frustrating that it's hard to reproduce. Thank you for your patience. ARE YOU SURE you noticed jAlbum performing a lenghty "Make All" operation when you simply hit the "Make album" button?
@Jeff: If, for some reason, the old manifest file isn't updated with a new one and not deleted either, then jAlbum will re-upload all updated files again, but I can't see how this can happen as jAlbum deletes the old manifest file prior to uploading the changes. It's good if the user can check the date stamp of the manifest file after an upload. It should have the most recent "last modified" date.
ARE YOU SURE you noticed jAlbum performing a lenghty "Make All" operation when you simply hit the "Make album" button?
I have doubts about that, as well. Uploading is just a file-copying operation. I can't imagine how it could ever trigger another Make album operation of any sort.
SharpByCoop, please take a look at the timestamps on the slide images in the output directory on your PC. Do they all have new dates? If not, there's no Force remake operation happening here - that would produce all new file dates.
Thanks for the update. Perhaps some IO issue can cause this, but I've tried to design the uploader to account for IO problems. There is for instance the scenario where an IO problem prevents jAlbum from writing an updated manifest file at the end. In this case, the uploaded album is left without a manifest file. This should not cause a full re-upload, but instead trigger jAlbum to compare each file manually in order to figure out what files to upload.
Perhaps the extreme case of a half-written or empty manifest file can cause this problem. I have to investigate that further...
This thread is unfortunately very familiar... 15000 images, 2.5GB. I always just click "Make and upload in the background" - and from time to time the tool decides everything needs to be uploaded again, but it takes several attempts to do so. After a few hundred MB it just stops doing anything, until all of a sudden on one of my attempts it gets through it and from then on I'm good for a while. Why it sometimes decides everything is new all of a sudden - beats me. So if you need another case for your investigation, feel free to contact me (sorry, can't put the URL public).
Currently I have another 4.5 hours of uploading ahead of me, so I better not let this laptop fall asleep...