5 ms·

What do you guys think of one of my creations (still in development stage) - Secure Digital Archive: http://goryachev.com/products/archive http://goryachev.com/

What do you guys think of one of my creations (still in development stage) - Secure Digital Archive: http://goryachev.com/products/archive http://goryachev.com/products/archive While not strictly a photo organizer app, it does have a photo gallery, timeline, and raw file format support.

miahi 12y ago
Trying it now. Opinions/bugs (not very well organized, sorry): - please allow multiple folder selection for volume source folder - the analysis phase is really slow and it looks CPU-bound on the ImageScaler.resize() method; try to find a faster resize library or at least allow user setting for scaling (smooth is quite slow) and multithread the resize - right now I have 7 idle CPU cores and you have a really slow application. This is bordering on unusable. I have ~2TB of jpg and raw photos, it would take at least half a month to resize them - and I didn't even ask for a thumbnail. - A snapshot cannot be stopped (there is no "stop" button/menu entry). - the persistent mode is called "Persistent" in one place and "Archival" in another - Not sure I understand the "persistent/archival" setting; I would expect that I can access the old/deleted files as long as they are in the repository files even if the source is deleted/unavailable. I now have a 2GB repository "backup" but I cannot access anything from it because I removed the volumes (the repository did not shrink). At least make it the default with a big warning if you disable it. - 64MB file chunk for the repository is quite small for something containing photos that cannot ever be deleted (a raw file can easily have 10 or 20MB); file access in folders with a lot of files is slow - please read EXIF data - it's way more important than Hex views; the metadata-extractor library[1] is stable and fast (I'm using it for my photo organizing application) - please rotate the thumbnails by EXIF data - corrupting/deleting a backup file doesn't give any warning (just that the backups don't work anymore and I cannot see the photos) - not providing a name for the volume in step 1 gives a warning when you want to leave step 2 (and not when you leave step 1) - raw image decoding is painfully slow; processing an 8MP Canon RAW takes 40 seconds; it estimates 6 hours for 480 photos. - try to buffer the DBInput/Output as RAF can be quite slow; check MappedByteBuffer So it looks like a good idea but it's really slow and it can fill up disk space with files that cannot be recovered. [1] https://code.google.com/p/metadata-extractor/ https://code.google.com/p/metadata-extractor/
- java-man 12y ago
  Excellent feedback, many thanks! The tool is still in the development stage, so a lot of things are sub-optimal or missing. But your comments are all valid. Persistent mode idea is for situations where the user wants to accumulate a large repository piecemeal - for example, a photographer can dump a day worth of files in a folder, upload to the repository and then delete the files on the local machine. This way the next sync will not delete the files dring the next snapshot. Can you email me an example of an image file that needs to be rotated (all mine have been rotated using windows preview)? Again, thanks for your comments! Very helpful.

miahi 12y ago

Trying it now. Opinions/bugs (not very well organized, sorry): - please allow multiple folder selection for volume source folder - the analysis phase is really slow and it looks CPU-bound on the ImageScaler.resize() method; try to find a faster resize library or at least allow user setting for scaling (smooth is quite slow) and multithread the resize - right now I have 7 idle CPU cores and you have a really slow application. This is bordering on unusable. I have ~2TB of jpg and raw photos, it would take at least half a month to resize them - and I didn't even ask for a thumbnail. - A snapshot cannot be stopped (there is no "stop" button/menu entry). - the persistent mode is called "Persistent" in one place and "Archival" in another - Not sure I understand the "persistent/archival" setting; I would expect that I can access the old/deleted files as long as they are in the repository files even if the source is deleted/unavailable. I now have a 2GB repository "backup" but I cannot access anything from it because I removed the volumes (the repository did not shrink). At least make it the default with a big warning if you disable it. - 64MB file chunk for the repository is quite small for something containing photos that cannot ever be deleted (a raw file can easily have 10 or 20MB); file access in folders with a lot of files is slow - please read EXIF data - it's way more important than Hex views; the metadata-extractor library[1] is stable and fast (I'm using it for my photo organizing application) - please rotate the thumbnails by EXIF data - corrupting/deleting a backup file doesn't give any warning (just that the backups don't work anymore and I cannot see the photos) - not providing a name for the volume in step 1 gives a warning when you want to leave step 2 (and not when you leave step 1) - raw image decoding is painfully slow; processing an 8MP Canon RAW takes 40 seconds; it estimates 6 hours for 480 photos. - try to buffer the DBInput/Output as RAF can be quite slow; check MappedByteBuffer So it looks like a good idea but it's really slow and it can fill up disk space with files that cannot be recovered. [1] https://code.google.com/p/metadata-extractor/ https://code.google.com/p/metadata-extractor/

java-man 12y ago
Excellent feedback, many thanks! The tool is still in the development stage, so a lot of things are sub-optimal or missing. But your comments are all valid. Persistent mode idea is for situations where the user wants to accumulate a large repository piecemeal - for example, a photographer can dump a day worth of files in a folder, upload to the repository and then delete the files on the local machine. This way the next sync will not delete the files dring the next snapshot. Can you email me an example of an image file that needs to be rotated (all mine have been rotated using windows preview)? Again, thanks for your comments! Very helpful.