Scanning and renaming creates wrong filenames

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Scanning and renaming creates wrong filenames

Re: Scanning and renaming creates wrong filenames

by Lowlander » Fri Jun 11, 2021 10:05 am

Either way works.

Re: Scanning and renaming creates wrong filenames

by Zonky » Fri Jun 11, 2021 3:14 am

Lowlander wrote: Thu Jun 10, 2021 11:06 am <Track#:2>
...obviously with a space between Tack and #

Thanks again!
Michael

Re: Scanning and renaming creates wrong filenames

by Lowlander » Thu Jun 10, 2021 12:41 pm

No, it was <Track#> with MediaMonkey 4 too. Maybe <Song#> was still available from older versions or from using a different language.

Re: Scanning and renaming creates wrong filenames

by Zonky » Thu Jun 10, 2021 12:38 pm

Thank you!

Did this change with MM5? It perfectly worked with MM4 before...

Re: Scanning and renaming creates wrong filenames

by Lowlander » Thu Jun 10, 2021 11:06 am

Scanning and renaming creates wrong filenames

by Zonky » Thu Jun 10, 2021 10:38 am

Hi!

I've activated rescanning and using auto-organizing to move my files from a download folder to specific folders and subfolders.
The template for mp3 files is: G:\michael\Music\MP3\<Album>\<Song#:2> <Artist> - <Title>

While this worked perfectly for MM4 it still does for MM5, however, today I noticed that some files did get the wrong filename.
E.g. .\VA\Song#2 Aced Of Base - Bad Dad.mp3 or .\Bummerland\Song#2 Ajr - Bummerland.mp3.

The properties of those files do show a track number though.
While adding about 70 files today, using the same procedure as always, I did not see such a behavior.

So what did go wrong?

I cannot say for sure if this is due to a missing track number formerly. Maybe I re-tagged those files and the track number got filled up. However, I guess this was not the case.

Michael

Top