SUMMARY Sometimes happens that BatchQueueManager is unable to change image Exif data with Time Adjust tool (I'm changing scanned pictures date and time). When It fails digikam notify with error and a red check symbol; It also generate images (in the same folder) with the right date and time (with a 'strange' filename) I investigated and I found some (2 or 3) Exiftool.exe digikam child processes; If I kill those processes and I retry the 'Run' It works. SOFTWARE/OS VERSIONS Windows: 10
Hmm, I can't reproduce the problem here in a quick test on Windows. ExifTool is not used here in the BQM. We need a DegugView (Microsoft App) log with active Debug environment variable if setting the date fails, as described here for Windows: https://www.digikam.org/contribute/ Maik
Created attachment 143705 [details] DebugView log Done. If fails on img454.
Created attachment 143706 [details] Fail screenshot
Log and screenshot added.
I can't see an error message. Only this is strange, a thumbnail cannot be created beforehand, is the file possibly defective? digikam.general: Thumbnail is null for "C:/Users/Riccardo/Pictures/V600 scans/img454.jpg" Maik
Can you make the image available if not publicly on my private mail? Maik
Maik, I can't sent my picture, are picture of my family. But, ... issue is not related of picture format or curruption because my test has been done with the same set of pictures (23 pictures) and sometimes the issue happens. When It happens I can try again, again, ... to run the batch with the same issue. In that situaton the only way is kill exiftool.exe process, and then the next run is without error (always !). As you can see from log the folder "C:/Users/Riccardo/Pictures/V600 scans" is where are the pictures, in the same place my scanner generate the pictures. But It does not depends on the generated pictures because during the last test (the attached log) those picture come from another folder, already processed from Digikam. Step to reproduce: - copy a set of pictures from elsewhere to C:/Users/Riccardo/Pictures/V600 scans - run Digikam (DigiKam has already an album on C:/Users/Riccardo/Pictures/V600 scans so at startup It recognize the new pictures) - select all pictures from C:/Users/Riccardo/Pictures/V600 scans - run Batch En. Mng - select a workflow with Time Adjuest module only - change date time of module (to set a new date time) - run the batch --> sometimes fails
Does the problem also occur if you have not opened Exiftool Tab in the right sidebar. Please test it when the Properties tab is open while the BQM is running. Maik
I've tried as suggested: no problems (10 tests). Then I switched to Metadata tab and run the same batch: no problems (5 test) Then I close Digikam and reopen: fail at the first time that I run the batch; next I kill Exiftools.exe, run again the batch: no problem. IMHO seems that exftools.exe **sometimes** keeps some images locked.
Hello, yesterday I restarted my scanning negative film roll activity. I left the Properties tab active. I've scanned about 12 rolls without problems.
RicDev, Can update this entry with some tests done with current digiKam 7.5.0 pre-release available here : https://files.kde.org/digikam/ Thanks in advance Gilles Caulier
(In reply to caulier.gilles from comment #11) > RicDev, > > Can update this entry with some tests done with current digiKam 7.5.0 > pre-release available here : > > https://files.kde.org/digikam/ > > Thanks in advance > > Gilles Caulier Hello Gilles, I can try but this pre-release changes the database structures or other configurations ? I'm asking in case of a rollback. I have not a test environment; I should replace my 'production' installation.
(In reply to RicDev from comment #0) > SUMMARY > Sometimes happens that BatchQueueManager is unable to change image Exif data > with Time Adjust tool (I'm changing scanned pictures date and time). > When It fails digikam notify with error and a red check symbol; It also > generate images (in the same folder) with the right date and time (with a > 'strange' filename) > I investigated and I found some (2 or 3) Exiftool.exe digikam child > processes; If I kill those processes and I retry the 'Run' It works. > > > > SOFTWARE/OS VERSIONS > Windows: 10 (In reply to RicDev from comment #12) > (In reply to caulier.gilles from comment #11) > > RicDev, > > > > Can update this entry with some tests done with current digiKam 7.5.0 > > pre-release available here : > > > > https://files.kde.org/digikam/ > > > > Thanks in advance > > > > Gilles Caulier > > Hello Gilles, > I can try but this pre-release changes the database structures or other > configurations ? > I'm asking in case of a rollback. I have not a test environment; I should > replace my 'production' installation. Hello Gilles I restarted my print scanning activity with 7.5.0 version. I change timestamps for about 50 pictures without exiv problems. Seems fixed. Sorry for huge late answer. Thank you very much .
Thanks for the feedback. I close this file now.