-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exif-renamer uses the wrong time for ctime fallback on Mac #10
Comments
Hey @bbugh, thanks for the thorough description of the issue. I'll look into it when I get a spare moment. |
dylansmith
added a commit
that referenced
this issue
Nov 24, 2017
@bbugh can you checkout this branch and see if this fixes your issue? |
This works perfectly! Thank you so much for fixing this. |
Great, I'll bump the version and release it |
Merged
dylansmith
added a commit
that referenced
this issue
Jan 15, 2018
* fixed #9 by adding sequential filename generation for conflicting filepaths; reduced test/demo images * #9: added support for globs in rename_dir and --glob flag * improve detection of file creation time (#10) * fix file creation calc, add better test * updated deps, removed Grunt for tooling * remove grunt dep, updated exif-parser * updated README * updated README
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have some files that don't have exif data but have the correct Mac created time. However,
exif-renamer
is using the wrongstat
value (at least for Mac) to get the created time.Using Mac's built-in
GetFileInfo
command, you can see here that the created time is as expect (05/04):However, the stat in
lib/exif-renamer.js:173
results in this:The ctime here is what Mac uses as "Date Added" which was created by
cp -p
, which preservesctime
(which Mac stores inbirthtime
).Here's what it looks like in Finder:
I was able to fix this by changing it to use
birthtime
as the fallback instead ofctime
. I know Mac stores different times and such, but I don't know the implications of this on other platforms.The text was updated successfully, but these errors were encountered: