{jobname} variable only good for one ingest

[jdemott]

Kirk,

Sorry if it's been mentioned, but when I use the {jobname} variable on ingest to create a folder name and name images,  it works fine the first card, but if I ingest any additional cards , a new folder is created as "{jobname}".  If I restart PM it'll work fine, but again, only the one time.  Other variables used in the string work fine the second time, for instance.

{datesort}-{jobname}-{seq}

20060521-Orioles-v-Nationals-001 (all images fine for first card)

............

20060521-{jobname}-0xx  (for all subsequent cards)  datesort and seq continue to work.


Thanks,

-Jason

[Kirk Baker]

Sorry if it's been mentioned, but when I use the {jobname} variable on ingest to create a folder name and name images,  it works fine the first card, but if I ingest any additional cards , a new folder is created as "{jobname}".  If I restart PM it'll work fine, but again, only the one time.  Other variables used in the string work fine the second time, for instance.

{datesort}-{jobname}-{seq}

20060521-Orioles-v-Nationals-001 (all images fine for first card)

............

20060521-{jobname}-0xx  (for all subsequent cards)  datesort and seq continue to work.

I did not know that.  I'll look into it right away.

Thanks for the heads-up.

-Kirk

[Kirk Baker]

Sorry if it's been mentioned, but when I use the {jobname} variable on ingest to create a folder name and name images,  it works fine the first card, but if I ingest any additional cards , a new folder is created as "{jobname}".  If I restart PM it'll work fine, but again, only the one time.  Other variables used in the string work fine the second time, for instance.

{datesort}-{jobname}-{seq}

20060521-Orioles-v-Nationals-001 (all images fine for first card)

............

20060521-{jobname}-0xx  (for all subsequent cards)  datesort and seq continue to work.

I did not know that.  I'll look into it right away.

Thanks for the heads-up.

I tried to reproduce this issue on both Mac OS X and on Windows XP SP2.  I could not get this issue to happen for me.

-Kirk

[dbrouse]

I've never had this problem either.

Mac OS X 10.4.6