File rename string problem, using code replacement

[DaveRe]

I'm having a problem with PM on one particular Mac Mini running Mavericks. I'm trying to run a Live Ingest, and have the incoming files renamed upon ingest. I'm trying to use a rename string like this:

Code: [Select]

{yr4}{mn0}{day0}{tmsl}_\{serialnum}#10\_{fbas}
In my code replacement file, the 10th field is the photographer's initials. This works fine on a couple of machines. On the particular machine I'm having the trouble with (which happens to be the machine I *need* to use for this Live Ingest), PM keeps substituting hyphens ("-") for the backslashes, so it ends up like this:

Code: [Select]

{yr4}{mn0}{day0}{tmsl}_-{serialnum}#10-_{fbas}
I've tried copying and pasting it from other places, typing by hand, etc, and I can't get it to take the silly backslash.

Any thoughts on how to correct this, so I can use code replacement in this rename string?

[Kirk Baker]

Does the build number of the various machines differ?  The current build of PM5 is 15800.

-Kirk

[Hayo Baan]

The \ is not a valid character in a filename on Macs. My guess is you mean a / instead (your other machines are likely windows, not?)

HTH,
Hayo

[Kirk Baker]

Hayo,

The \ is not a valid character in a filename on Macs. My guess is you mean a / instead (your other machines are likely windows, not?)

I think the OP's Code Replacement delimiter is the backslash character.

I don't know if all of the systems in use have the same Code Replacement delimiter, but that would be another setting to check for consistency.

-Kirk

[Hayo Baan]

Oops, of course, the \ is the replacement delimiter (duh…) And actually the \ is a valid character in a Mac filename anyway (just not on Windows as there it is the folder delimiter)

However, that all said, it is PM that changes the \ (and a /) to a - in the rename string on the Live Ingest dialogue.
I recall from long ago PM had this same “issue” with other fields (I think I even reported one of them myself), but these now all allow the \, I guess you overlooked the rename box in the Live Ingest dialogue. Should be easy to fix, I think 

Cheers,
Hayo

[DaveRe]

Yeah, \ is the code replacement delimiter  And, all the systems have the default, that way - they all are using \ as the CR delimiter.

Kirk, everything is running 15451. Looks like you might've just released 15800 on the 11th? I actually tried to look for a software update via PM that day before I posted, and it didn't find anything. To be clear, the machine that shows the symptom, and the machines that do not show the symptom are all running the same build.

I don't think they missed the Live Ingest file rename box for support of code replacement - it works on some machines, just not this one

I'm about to upgrade the problem child and my current laptop to 15800 - will report back on results in just a bit...

[DaveRe]

Well, isn't that special. After the upgrade, it's now broken on both machines 

[Kirk Baker]

If you don't mind changing your Code Replacement delimiter to something else like '-' or some other character besides '/' or '\' then I expect you'll have no problems on any of your systems.

-Kirk

[Hayo Baan]

If you don't mind changing your Code Replacement delimiter to something else like '-' or some other character besides '/' or '\' then I expect you'll have no problems on any of your systems.

Yeah, that'll probably work too, but the fault is still with PM; it should allow the \ there, just like it does in the other rename string boxes.

[Kirk Baker]

Hayo,

If you don't mind changing your Code Replacement delimiter to something else like '-' or some other character besides '/' or '\' then I expect you'll have no problems on any of your systems.

Yeah, that'll probably work too, but the fault is still with PM; it should allow the \ there, just like it does in the other rename string boxes.

True, but I don't think the OP wants to wait for a new release to solve his problem.

-Kirk

[DaveRe]

Well... we've trained everyone to use \ as the delimiter, so it's potentially painful on the human end to retrain our editors in that fashion. Something other than a dash works better for us, but that's neither here nor there, really - except that (without having tested it), I'm going to guess that only PC legal filesystem characters work in that field, now, or something?

Is there an easy way to get back to a version that works? We really haven't had any issues we've seen on our end fixed in the last couple of versions, so I don't think there's a problem with that. I'd rather run an older version that doesn't display this bug (at least two versions back, I'm guessing?), rather than have to retrain everyone (those "finger macros" take a while to fix).

My timeline is that I need it to work by next Tuesday - I suspect that's likely before the next planned release?

[Kirk Baker]

Dave,

Well... we've trained everyone to use \ as the delimiter, so it's potentially painful on the human end to retrain our editors in that fashion. Something other than a dash works better for us, but that's neither here nor there, really - except that (without having tested it), I'm going to guess that only PC legal filesystem characters work in that field, now, or something?

Is there an easy way to get back to a version that works? We really haven't had any issues we've seen on our end fixed in the last couple of versions, so I don't think there's a problem with that. I'd rather run an older version that doesn't display this bug (at least two versions back, I'm guessing?), rather than have to retrain everyone (those "finger macros" take a while to fix).

My timeline is that I need it to work by next Tuesday - I suspect that's likely before the next planned release?

Yes.  I suggest that you go back to an earlier build.

-Kirk

[DaveRe]

Well, maybe that's not going to work, either. I have 15277 on a machine here at home (a release earlier than the one I had on the work machines and laptop originally, and two releases or more back from the latest), and it shows the same behavior. Unless you have the build earlier than that handy and can test it, I think we're going the new delimiter route anyway.

[Kirk Baker]

Dave,

All of the release builds are listed in the Announcements section of the forums.  How far back you'll need to go is unknown to me.

-Kirk

[Kirk Baker]

Dave,

I'm working on a fix for your renaming problem in Live Ingest.  I plan to have a build you can test available later today.

-Kirk