Bug 387004 - Rename on import is inconsistent jpg to raw
Summary: Rename on import is inconsistent jpg to raw
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: AdvancedRename-Import (show other bugs)
Version: 5.7.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-16 20:53 UTC by Mick Sulley
Modified: 2020-08-04 11:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.1.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mick Sulley 2017-11-16 20:53:52 UTC
Running 5.7.0 app bundle on Linux Mint
I have import set to rename on date and time
When I import pictures from my Canon EOS 550D the jpg seem to rename as expected but the .CR2 files get a different name.
During British Summer Time the difference is one hour and a few seconds, now we are back on GMT it is just a few seconds.
If I select the .CR2 files which have been imported and select rename, it renames them to what I expected.  
It would seem that the rename logic is different between .JPG and .CR2
Happy to provide more info or test stuff if it helps
Thanks
Mick
Comment 1 Maik Qualmann 2017-11-17 20:12:42 UTC
Yes, that is a well-known behavior. If the camera is connected via gPhoto2 device, we can not read metadata from RAW files. The date/time then falls back to the file date and this can be different from the metadata. I plan to change the renaming in the next versions so that it will be done after the download of the files from the camera.

Maik
Comment 2 Mick Sulley 2017-11-18 11:13:21 UTC
Thanks Maik, looking forward to the next release!
Comment 3 Mick Sulley 2017-11-18 11:54:22 UTC
Just noticed something else whilst renaming.  If I select several images where some can be renamed and for others the name is already correct, the 'renames' show black and the 'already correct' show red, but the 'OK' button is greyed out, so I have to select just the ones which need to be renamed, which is a problem as I don't know which ones they are until I try to rename them.

Should I create another bug for this?
Comment 4 Maik Qualmann 2017-11-18 13:06:32 UTC
This is not a bug, the red filenames indicate that a rename problem would occur. Either the file names are duplicated by the renaming syntax or a file with the name already exists in the directory.

Maik
Comment 5 Mick Sulley 2017-11-18 13:23:23 UTC
I agree that the red ones will not be renamed, but I would have thought it should be possible to rename the black ones.
Comment 6 Maik Qualmann 2019-09-10 07:23:41 UTC
*** Bug 411780 has been marked as a duplicate of this bug. ***
Comment 7 caulier.gilles 2020-08-04 08:07:42 UTC
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Best Regards

Gilles Caulier
Comment 8 Mick Sulley 2020-08-04 08:51:33 UTC
I think this was fixed a while back.  Just tested in DK7 and it looks fine.  I suggest that you close it.
Comment 9 caulier.gilles 2020-08-04 11:34:02 UTC
Thanks for the feedback