This is interesting but relies on the ordering which has to come either from
the sequence itself or rely on other information like the timestamp which,
as I've mentioned, leads to other problems.  I do save the original file
information from the camera at the time of download, so I can bypass the
problems I've been having getting it via an API call, but the rollover
problem based solely on sequence numbers is a purer problem.  Also, an
example using the API to get the various timestamps has potentially wider
uses.

The limitations of the breakpoint methods imply that there can't be multiple
rollovers.  However, based on even my extreme amount of photo-taking, it
seems safe to assume that I won't be dealing with a span of more than a
couple of thousand per batch. I guess this assumption could be violated as
memory chips get ever-larger and if I get less diligent about clearing it
off frequently.

Actually, it just occurred to me that the camera itself deals with rollover
by starting a new parent directory whenever the count goes past a certain
amount.  That is, you would see sub-directory\file names like this on the
chip:

\Fuji_154\DSCN9997.JPG
     "        DSCN9999.JPG

\Fuji_155\DSCN0000.JPG
        "    \DSCN0003.JPG

 Unfortunately, different models even from the same camera maker do this
inconsistently: my older Fuji would start a new sub-directory at the
rollover of 10,000 as shown here but my new camera starts a new
sub-directory every 1,000.  Also, if I used this information, I'd have to
keep track of it going forward but don't have it historically.

I guess what I have is good enough for now, though it would be good to
figure out how to use those APIs effectively.

Thanks all,

Devon

On Mon, Jan 19, 2009 at 5:31 AM, Aai <[email protected]> wrote:

>
>
> Devon McCormick schreef:
> > To All -
> >
> > Thanks for all the suggestions.  I particularly like Raul's though it
> still
> > uses breakpoints;
> If input is not much more complex than shown hereafter (e.g. no multiple
> rollovers):
>
>   (]`(i...@[({.,1e3 + }.)])@.(+./@[)~2 >/\0,]) 1 2 3 9500 9603  1 2 3
> 1 2 3 9500 9603 1001 1002 1003
>
>
>
> =@@i
>
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
>



-- 
Devon McCormick, CFA
^me^ at acm.
org is my
preferred e-mail
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to