hi @paultaylor,
I notice that the report creation percentage helped a lot when running my AutoKong script.
but look :
Report Creation 78%
Report Creation 79%
Report Creation 80%
Report Creation 86%
Report Creation 89%
Report Creation 92%
Report Creation 95%
Report Creation 98%
Report Creation 100%
Report Created:/songkong/Reports/FixSongsReport00656/FixSongsReport00656.html
Summary:
Processing:0
Songs loaded:479
Songs fingerprinted:478
Songs ignored because already matched:0
Songs matched to MusicBrainz release:137
Songs matched to MusicBrainz song only:13
Songs matched to AcoustId release:0
Songs matched to Acoustid song only:11
Songs matched to Discogs release:92
Songs matched with artwork:163
Songs saved:0
Completed:479
Errors and Warnings:0
Sending Pushover notification: 🎵 SongKong Processing Summary for folder: /mnt/user/MURRAY/Music/Music_dump/11-2023/30-11/ 🎵
Report Created:http://songkong.phospho.ovh/FixSongsReport00656/FixSongsReport00656.html (0.00%)
Songs loaded:479 (100.00%)
Songs fingerprinted:478 (99.79%)
Songs matched to MusicBrainz release:137 (28.60%)
Songs matched to MusicBrainz song only:13 (2.71%)
Songs matched to Discogs release:92 (19.21%)
Songs saved:0 (0.00%)
Completed:479 (100.00%)
Errors and Warnings:0 (0.00%)
⏱ Total Time Taken: 0:02:27.796385 ⏱
📊 Overall Progress: 1/59 folders processed (1.69%). 58 folders remaining.
🔗 Report URL: http://songkong.phospho.ovh
🔍 Estimated Time for Next Folder: -1 day, 23:59:59.968628
❗ Error Count: 1
📊 Efficiency: 3.24 songs/second
💾 Disk Usage: Total: 183574745720, Used: 98321179236, Free: 85253566484
Executing the delete duplicates command: docker run --rm --name songkong_delete_mnt-user-MURRAY-Music-Music_dump-11-2023-30-11 -v /mnt/cache/appdata/songkong:/songkong -v /mnt/user/MURRAY/Music:/music songkong/songkong -d "/music/Music_dump/11-2023/30-11/"
Sending Pushover notification: 🎵 SongKong Delete Duplicates Summary for folder: /mnt/user/MURRAY/Music/Music_dump/11-2023/30-11/ 🎵
Processing:0
Songs loaded:479
Duplicate groups found :0
Duplicate songs deleted:0
Errors and Warnings:0
Executing the rename command: docker run --rm --name songkong_rename_mnt-user-MURRAY-Music-Music_dump-11-2023-30-11 -v /mnt/cache/appdata/songkong:/songkong -v /mnt/user/MURRAY/Music:/music songkong/songkong -f "/music/Music_dump/11-2023/30-11/"
Sending Pushover notification: 🎵 SongKong Rename Task Summary for folder: {current_folder} 🎵
Songs loaded: 479
Songs renamed: 163
Completed: 479
Errors and Warnings: 0
Sending Pushover notification: 🎉 Script has finished processing the folder. 🎉
a deeper look here shows that, whie the fix task do implement this % display, the duplicates task ends like this :
Errors and Warnings:0
Executing the rename command: docker run --rm --name songkong_rename_mnt-user-MURRAY-Music-Music_dump-11-2023-30-11 -v /mnt/cache/appdata/songkong:/songkong -v
It jumps directly from the dupicates task to the rename task, without generating anything.
The rename task as well, doesn’t seem to generate a proper report. Problem is, when this happens, sometimes, the DB seems to be locked for whatever reason, and the next task will simply NOT detect any files to rename.
Do you think it would be possible to add this feature to all types of tasks ?
Thanks !