[Mark Sisco]

I'm sure there is an easy answer for this, but I am really confused over all of the numbering tokens and how to use them to achieve what I want.

I have downloaded a CF card and used GSR8-8{L3} as my file name. The result is GSR8-8001, GSR8-8002, GSR8-8003, etc. There were 225 images in total.

I have a second card from the same job and I would like to do one of two things:
- have it pickup the numbering where the previous card left off (i.e. GSR8-8226, or
- specify where I want it to start, for example have the 2nd card start downloading with GSR8-8250.

Can someone help me with each of these two options? I've attempted using {seq#3} for example but cannot even get the numbering to increment on one card much less accomplish what I want with the 2 cards.

I am using Downloader Pro 2.0.1

Thanks - Mark

[mike.strock]

I'm paranoid about losing images, so here's what I do:

- I have four cards that I usually use on a regular basis
- I copy all the cards onto the computer manually into a directory
- I then use DownloaderPro to move the images from that working directory to another directory, naming them as I want them named.

Yeah, it's a secondary step. But it assures me (in my mind at least) that I don't overwrite anything or lose anything.

Mike.

[Clive]

Mike, the {I} and {L} are intended to handle filename clashes, and not serial numbering.

I use {n3} with a date and batch number, partly because {seq#} was not implemented.

My understanding is that the sequence number is stored in the registry and is therefore not lost between BDLP loadings. In Preferences, you can specify a start number, or you can reset the counter.

One solution: Enter as Job No. GSR8-8, and use {J}{seq#3}.

When you insert the second card, you should see in Preferences the current next number (eg 226) and the correct file renaming in the download panel.

What do you get with seq#3 and one card - in what way is it wrong?

EDIT: I've tested - you are right - seq# is not working as expected! Must investigate further.

[Clive]

Aha!

After checking the information in both the Preferences/Tokens dialog and the Help/File Tokens page, I went back to test again. The settings were correctly carried forward from the failed session!

It seems that "Name Clash" will be shown in the download pane if the Registry key has not been created. Setting up {seq#} in a filename specification and not using it will force the key to be created when you quit BDLP with the default value "1".

After that there should be no problem at all.

[Mark Sisco]

Aha!

After checking the information in both the Preferences/Tokens dialog and the Help/File Tokens page, I went back to test again. The settings were correctly carried forward from the failed session!

It seems that "Name Clash" will be shown in the download pane if the Registry key has not been created. Setting up {seq#} in a filename specification and not using it will force the key to be created when you quit BDLP with the default value "1".

After that there should be no problem at all.

Clive,

Thanks for the information. I'll be honest, I'm still quite confused over all of this though. What string(s) would I use on card one and subsequent cards to accomplish what I laid out in my initial post? Something along the lines of what you noted above (Enter as Job No. GSR8-8, and use {J}{seq#3}.)?

Would appreciate clarification . . . having trouble wrapping my brain around this one with the proper tokens.

Thanks,

Mark

[Clive]

My quick test on two cards, each with three images, worked as i understand you require.

{J}{seq#3)

However, with only three digits, I would expect you to run off the end quite quickly. I would expect to use {seq#4 - 6}.

If you want to use a fresh sequence for each job , you would need to reset the start number in Preferences, and not download other jobs in the middle.

{seq#} is designed to continue forever (ie 999999), giving a unique number to each and every image, regardless of job, date, card, etc.

If there is a way of applying a continuous sequence series to each job, regardless of card insertion, date of insertion,and other jobs being being downloaded, I am not aware of it.

[Mark Sisco]

My quick test on two cards, each with three images, worked as i understand you require.

{J}{seq#3)

However, with only three digits, I would expect you to run off the end quite quickly. I would expect to use {seq#4 - 6}.

If you want to use a fresh sequence for each job , you would need to reset the start number in Preferences, and not download other jobs in the middle.

{seq#} is designed to continue forever (ie 999999), giving a unique number to each and every image, regardless of job, date, card, etc.

If there is a way of applying a continuous sequence series to each job, regardless of card insertion, date of insertion,and other jobs being being downloaded, I am not aware of it.

Clive-Thanks.

When I use {J}-{seq#4} it wants to name every file on the card the same (example: GSR8-0001). I must still be missing something.

Mark

[Clive]

Clive-Thanks.

When I use {J}-{seq#4} it wants to name every file on the card the same (example: GSR8-0001). I must still be missing something.

Mark
That is what I got, too, until I set the filename format to use seq#, do no downloading but instead close BDP. (I made sure that the starting number was 1 first.) Re-opened and loaded the card into BDP and there were no clashes becayse they were sequentially named.

Perhaps a test - specify a start of say, 123, actually download 1 image, Exit BDP and check the new file, then reopen BDP and see if the number has incremented.

I presume that you have no Registry cleaning/monitoring in place.