Hello, I’m doing a curated cleanup of my 560K song collection and would like to use the app to do some of the moving. Is there a way to disable the ‘can’t overwrite existing files exist’ message and allow the destructive move? I think MP3Tag’s move is quicker than the alternative of tag / file to a secondary location and then fileman moving them over the top of the original. Thanks!
I think that this happens only if the new name would lead to overwriting a different already existing file. After that process you would have 1 file less. Is that intended?
I would investigate why there is another file with that name.
Perhaps the tag data does not differentiate enough?
Is it really a duplicate?
I had some damaged ASF in my destination directories copies. I transcoded all the damaged wma files into the new different source directory where they were fixed. I wanted MP3Tag to read the new source and then tag → filename move them into the destination over the top of the bad ones (identically named, just repaired now), so I sought an override for the naming warning (I wished a destructive copy). The reason vs. just drag and drop from source to destination was taking too long for the amount of files I’m dealing w/. Appreciate the reply, I ended up building a Powershell script that initiated the transfer over the top a lot quicker. It would be interesting if there is a way in MP3Tag to do this procedure.