Page 1 of 1

Can't Change Create Date Timestamp

Posted: 21 Feb 2015 08:17
by shamill15
Hi there,

Maybe a Newbie question. Have looked for an answer in the forum but can't find one...

I am trying to correct the Create Date on my 2000+ video clips on my NAS to use data from the file name (yyyyddmmhhss.mpg). The script says it's working but the date isn't changing.

Code: Select all

$date = regexreplace("<curbase>", "(\d{4})(\d{2})(\d{2})(\d{2})(\d{2})(\d{2})", "$3-$2-$1 $4:$5:$6"); timestamp c, $date;
I don't believe it's the script - If I manually correct the date from the XYplorer interface, it accepts the change but doesn't actually make it (reverts immediately to the original).

I've tried removing the 'read-only' and 'archive' toggles but no dice. Is it a restriction in the trial version? Is it to do with the NAS operating system? Any suggestions?

Re: Can't Change Create Date Timestamp

Posted: 21 Feb 2015 09:07
by highend
What's the full script?

<curbase> resolves only to the current list item...

Re: Can't Change Create Date Timestamp

Posted: 21 Feb 2015 09:29
by shamill15
That is the full script but I can't get it working even on the current list item even though it says "Timestamping done: 1 Item stamped" in green text). Neither can I change it manually by adjusting the date in the user interface (Properties Tab > Modified:). Manual adjustment simply accepts the change but the entry reverts back to the original.

Once I get it working for a single list item I plan to run it on a selection.

Thanks a million for offering support.

Re: Can't Change Create Date Timestamp

Posted: 21 Feb 2015 09:45
by highend
Ok, the problem is your NAS. Do you use the latest firmware? We had a similar issue not too long ago on the forum.

This was the post: http://www.xyplorer.com/xyfc/viewtopic. ... &hilit=nas

Re: Can't Change Create Date Timestamp

Posted: 21 Feb 2015 10:24
by shamill15
Thanks again highend, just upgraded the firmware and still the same issue. Tested on local files and it works perfectly. You are correct it is clearly the NAS, I will report the issue in the QNAP forum.