Copy link to clipboard
Copied
Hello Community,
filenames out of the camera are set as _DSC1.* _DSC2.*, _DSC3.* …
My Batch Renaming procedure includes MMSS to ensure right chronological sequence:
(Another text line not shown, as last step to add model).
What I get is:
So Milliseconds are reflected as 000 in the renaming procedure although they are included in the metadata: File info:
How do I get this to work correctly? Result should be: 20240928_102028980_D750
These issues have been reported earlier Adobe Bridge Batch rename - issues to include mill... - Adobe Community - 12519842 but doesn’t seem to be fixed yet?
Thanks for your ideas!!
Martin
(Bridge 14.1, Windows 11)
For what it's worth, here is the Bridge script to batch rename using milliseconds:
/*
Batch Rename to YYYYMMDD_HHMMSSMS_D750.jsx
v1.0 - 3rd October 2024, Stephen Marsh
https://community.adobe.com/t5/bridge-discussions/batch-renaming-issue-with-milliseconds/td-p/14886235
Rename from:
_DSC1.jpg
_DSC1.NEF
to:
YYYYMMDD_HHMMSSMS_D750.jpg
YYYYMMDD_HHMMSSMS_D750.NEF
With the MS or Millisecond value being the only unique part of the filename.
Note: Bridge 2024 fails to refresh, so refresh/F5 man
...
Copy link to clipboard
Copied
This has been brought up before as an issue with video and image sequences. Who knows if a fix is possible or if it will be implemented.
Copy link to clipboard
Copied
@Lumigraphics wrote a fantastic Bridge script to run ExifTool commands, essentially allowing Bridge to be used as an GUI for selecting files and running commands outside of Terminal.app or CMD.exe:
P.S. I have updated the previous code examples to remove the underscore before the milliseconds value since these screenshots were taken.
Copy link to clipboard
Copied
Hi Guys
what a great piece of work! And having an Exiftool-GUI inside Bridge is an amazing improvement in handling the tool!
Now I'm off to work, will try to implement all this in my workflow later. Thanks guys!!!
Copy link to clipboard
Copied
The latest versions of my scripts are available for download on Dropbox.
https://www.dropbox.com/sh/mg817g9a9ymbasi/AADTmXUVxmFfM58bcyYE7yiwa?dl=0
Copy link to clipboard
Copied
Hi Lumigraphics,
very sorry, but unfortunetely I couldn't get your script RunEXIFTool to work.
What did I do:
- some time ago installed Exiftool (located: "C:\Windows\exiftool.exe"; "C:\Windows\exiftool_files\").
- tested codes provided above by Stephen with ExiftoolGUI direct, and they worked perfectly
- downloaded your script Run EXIFTool from the Dropbox, download directly as *.jsx, no renaming necessary
- copied into Bridge2024/Startup Scripts folder
- started Bridge, Bridge asks for approval of new script, yes
- Preferences/ Startup Scripts show correctly installed script
- Switched to content panel, selected 3 test files, right click, Run EXIF Tool is offered as new option.
So far, so good.
- click - and nothing happens, no new panel comes up, no hidden window either.
What do I miss here?
Sorry to bother again.
Thanks!!
Copy link to clipboard
Copied
Hold down command/control key when running it. I need to update the code a bit, it works on Bridge 12 as-is but not Bridge 13+.
Copy link to clipboard
Copied
Ah, ok. Got the panel opening in Bridge 11 with CTRL key (not in 14, as you said).
Entered the same code as you did (except changing ' into ", I'm on Windows).
And produced a compiling error in vbstemp.vbs ("syntax error at position 166")
Which is position 166? It's the $ ?
vbstemp.vbs:
CreateObject("Wscript.Shell").Run "powershell -NoLogo -NoProfile -Command Start-Process -FilePath 'exiftool' -ArgumentList '-P_in_place "-XMP-xmpMM:PreservedFileName<${filename;s/\.[^.]*$//}" -execute "-filename<${DateTimeOriginal;s/://g;s/ /_/g}${SubSecTimeOriginal}_${model;s/(^.+ )(.+)/$2/}.%e" -common_args -r -overwrite_original \""C:\Users\User\Pictures\Directory\Test\_DSC6510.JPG\""' -RedirectStandardOutput 'C:\Users\User\AppData\Local\Temp\exiftemp.txt' -WindowStyle Minimized", 0, True
Ok, now I'm lost ...
No need to take this up, if you don't want to chew the bone. I'm completely fine with all your help given so far and I've the millisec and renaming problem solved perfectly. Thanks very much once again!
Copy link to clipboard
Copied
Using the command prompt on Windows is a PITA, you get the ugly command window. So I have a workaround where I write a temp file and execute it with Powershell to run commands silently. This may be a collision between the $ used in EXIFTool and the command run via VBS. Does your command work in a command window?
I'm not a Windows user unless I'm forced to be so this is all just painful for me 😕
Copy link to clipboard
Copied
PITA is confirmed. And no, didnt't get it to work in the Command Window.
But I did get it to work in the EXIFToolGUI, which means that it is perfectly scripted.
Is the preferable way to use the command line anyway.
Thanks Lumigraphics!
Copy link to clipboard
Copied
Although ExifTool is a CLI based tool, there are different options available to Windows or Mac users to make it easier to use.
Here is an example from the Mac where I have integrated it into the Finder, where I right click files and select the pre-made command that I wish to run. Or it could be an icon for drag-n-drop etc.
https://prepression.blogspot.com/2016/12/automator-diy-exiftool-gui-services.html?m=1
Copy link to clipboard
Copied
Add your votes to fix this bug at the (separate) Bridge User Voice forum:
There are 3 tickets that you can vote for with similar issues on the incorrect millisecond 000 value.
Copy link to clipboard
Copied
Ok, done.
Thanks for the links, Stephen.