I figured it out, It's stupid
Its my order or importing
Context
Path 1 = Root Folder "Database"
Path 2 = 2 Levels deep into Database: >Album Artist>Album
Path two is my final archival folder.
This action in total does the following:
- Export Current Album Art to a "Recycle Bin" (Spare Folder)
- Formulate Filenames for Front & Back Covers
- Import & embed Front & Back Covers from either Path 1 or 2
- Formulate my Archival Folder's Path (Path 2)
- Export Front & Back Covers to an Archive Folder (Path 2) Which is based on the Album Artist & Album name (all characters that cannot be in filenames on Windows are Removed)
The Problem:
My order of operations:
FrontCover - Path 1 - PNG
FrontCover - Path 1 - JPG
BackCover - Path 1 - PNG
BackCover - Path 1 - JPG
FrontCover - Path 2 - PNG
FrontCover - Path 2 - JPG
BackCover - Path 2 - PNG
BackCover - Path 2 - JPG
Solution 1:
New Order of Operations:
FrontCover - Path 1 - PNG
FrontCover - Path 1 - JPG
FrontCover - Path 2 - PNG
FrontCover - Path 2 - JPG
BackCover - Path 1 - PNG
BackCover - Path 1 - JPG
BackCover - Path 2 - PNG
BackCover - Path 2 - JPG
WHY
My import of front cover replaces the current Art, the import of back covers does not replace current art.
In my previous order the Back cover art was getting embedded VIA path 1 in (STEP 1) The Front Cover art was being embedded via Path 2 in (STEP 2) so the embedding of the Front cover in (STEP 2) was completely negating progress made in (Step 1).
I've been using the action for almost a year & a half & it was working flawlessly.
This was probably because when I tag new tracks the album arts, front & back are always in Path 1
When I tagged older tracks that already have their art Archived the covers are always in Path 2
Solution 2:
Alternatively I could have simply removed the setting so that when front covers import they are not replacing the current image.
In my case this would mean I'd need to delete the current art before or after running this action otherwise it would still be there as an extra cover afterwards
MP3TAG: ∞
ME: 1
I had a similar blunder a while back...
If you tried to export tags to a .txt file & in the same action group you attempt to import that .txt file your action will FAIL.
MP3TAG will run through the Steps of your action group faster than the time it takes for that .txt file to "materialize" & be recognizable on your Computer. So at the instant MP3TAG goes to import that .txt file it DOES NOT YET EXIST & therefore cannot be imported.
Simple fix, split up your action groups
Sorry for the wasted time...I pray this helps some poor frustrated soul one day