Ingest Bug in Version 4.6.6

[Jan]

I have following Problem, I ingested from two cards both starting with filenumber 0001, on the first card where the first pictures RAW only. On the second card all files where jpg. Ingest of the first Card went fine, when i ingest the second card the seqenz variable started again by 0001 and I got the jpg connected to the raw file then the other jpgs would get an A to the Filenumber like 0025A.

Regards Faas

[Kirk Baker]

Faas,

I have following Problem, I ingested from two cards both starting with filenumber 0001, on the first card where the first pictures RAW only. On the second card all files where jpg. Ingest of the first Card went fine, when i ingest the second card the seqenz variable started again by 0001 and I got the jpg connected to the raw file then the other jpgs would get an A to the Filenumber like 0025A.

Thanks.  We'll look into the issue.

-Kirk

[Jan]

Hello Kirk,
it seems that PM 4.6.6 is also forgetting the {seqn} variable after shut down, i started for a prober ingest with 0392 it ingested me the files to 0608. Then i shut down my system, then i started again ingesting new files in the same folder, but the {seqn} variable was not 0608 it remaind on 0392 an all files get a A again at the end of the name.

Best regards Faas

[Kirk Baker]

Faas,

it seems that PM 4.6.6 is also forgetting the {seqn} variable after shut down, i started for a prober ingest with 0392 it ingested me the files to 0608. Then i shut down my system, then i started again ingesting new files in the same folder, but the {seqn} variable was not 0608 it remaind on 0392 an all files get a A again at the end of the name.

What OS are you running?

-Kirk

[Jan]

Windows 7 Ultimate 32Bit

I hope this helps.

Faas

[pjs]

I have the same ingest problem!
PM 4.6.6 with OS X 10.6.4

[dean]

it seems that PM 4.6.6 is also forgetting the {seqn} variable after shut down...

I'm getting the same issue but it's not just on a shutdown.
I've just shot my second weekend worth of events with 4.6.6 and I've had the ingress {seqn} issue on both of them.  The strange thing is...  sometimes it works and sometimes it doesn't.
Sometimes I'll put in a card and notice that the ingress screen has popped up and the sequence number has increased to one greater than the last image number (the correct behavious).  Sometimes the screen will pop and the sequence will be the same as the starting number of the previous ingress (this causes a duplicate numbering and the addition of lots of 'A' versions).  I thought it was related to using alternating flash cards, but I've seen it with just one card now.

At the last game I resorted to setting the seqn numbers by hand on each ingress.  It worked fine for me on 4.6.5.

I've thought about getting some screen shots, but I'm always on deadline.

Dean

[Kirk Baker]

Dean,

it seems that PM 4.6.6 is also forgetting the {seqn} variable after shut down...

I'm getting the same issue but it's not just on a shutdown.
I've just shot my second weekend worth of events with 4.6.6 and I've had the Ingest {seqn} issue on both of them.  The strange thing is...  sometimes it works and sometimes it doesn't.
Sometimes I'll put in a card and notice that the Ingest screen has popped up and the sequence number has increased to one greater than the last image number (the correct behavious).  Sometimes the screen will pop and the sequence will be the same as the starting number of the previous Ingest (this causes a duplicate numbering and the addition of lots of 'A' versions).  I thought it was related to using alternating flash cards, but I've seen it with just one card now.

At the last game I resorted to setting the seqn numbers by hand on each Ingest.  It worked fine for me on 4.6.5.

I've thought about getting some screen shots, but I'm always on deadline.

No need for screen shots.  The original poster helped me find the cause and I made some changes to how the sequence number is saved.  He tells me that the problem is solved.

A fix is on the way.

-Kirk

[dean]

A fix is on the way.

-Kirk

Love ya work.  =)

[Gray]

Great. Can't wait.  Same thing happening on my Mac. 

[Sven]

same here

[dean]

A fix is on the way.

Any word on when a fixed version is due?  I'm trying to decide if I should hold out of roll back to 4.6.5?

Dean

[Kirk Baker]

The Ingest {seqn} issue is resolved in the 4.6.7 beta version:

http://forums.camerabits.com/index.php?topic=6072.0

-Kirk