This is a decent looking application. It looks close to (and related
to) a function I'd like to have.
I'd like to have an application take a subtree (that includes
multiple folders of canon RAW images and thumbnails), and put
all the RAW+thumbnails into folders of no more than a particular
total size. I'd use this to quickly divide my images into CD-R (and
someday DVD) sized blocks that I can easily back up.
One way to do this would be to select a subtree, and have a "copy
to folders" button or option. You could set the maximum size of
folders (arbitrary size lets this work for any size backup media),
and provide a prefix for folder names (so they'd end up being <
foldername>-1, <foldername>-2, etc.). You'd need to have some
method of keeping thumbnails and images together---this could
either be special purpose (hard coded for a particular camera
model), or you could provide an option that copies/moves all files
with the "current" prefix (like if the next file to be copied is
IMG3487.CRW, check size for and move IMG3487.*). The latter
method would work for any camera I've used, and would work for
cameras that can shoot different formats (like cameras that shoot
either a raw or jpg format, where they create files with either a
.NEF or .CRW suffix, or a .JPG suffix).
With such a tool, my workflow would change to copying files off
flash into arbitrary folders, running your tool to chunk them up
appropriately (avoiding all that wasted space), and then loading
them into a catalog.
Thanks!
Logged In: YES
user_id=97026
This sounds like it would be a useful feature that would
benefit even non-pro users seeking to compile collections
into archivable sizes.
* Only image extensions viewable by your system can be
displayed (not sure about .NEF or .CRW suffixes).
* Not sure what is required to keep thumbnails and images
together (Are you saying images/thumbnail pairing should not
span multiple discs or, Are the names predicated differently?)
Good idea - feature request accepted.
Logged In: YES
user_id=677740
It is reasonable that odd image formats can't be displayed.
On the thumbnails question, I can provide an example. If I shoot jpeg
on my Canon D60, I get two files---IMG1234.JPG and IMG1234.THM. If
I shoot raw, I get IMG1234.CRW and IMG1234.THM. The .THM file
contains most of the photo's EXIF information (like the lens used,
shutter speed, lens opening, etc.). Image browsing programs expect
these files to be in the same directory, so it would be convenient if
these files were always kept together. If they are split apart, it isn't a
killer, it's just an annoyance.
One other thing I can think of that might complicate life is cameras that
name photos the same thing (like they always start numbering pictures
on a new flash card at 1). I don't have this problem, but some might,
and I expect your program would have to deal with this in some manner.
Then again, maybe it doesn't (so long as the originals aren't touched).