[X] Filename-Filename failure on grandparent folder

[chrisjj]

Convert | Filename - Filename can give the wrong result, e.g.

Old filename pattern: %1\%2\%3
New filename pattern: %1\%2\%3

should give

"S:\TINDT ctango\02480002922629\1\1.wma" ->
"S:\TINDT ctango\02480002922629\1\1.wma"

but instead gives

"S:\TINDT ctango\02480002922629\1\1.wma" ->
"S:\TINDT ctango\02480002922629\02480002103028\1\1.wma"

i.e. duplicates %1.

%1\%2 does not suffer from this.

[Florian]

I don't see the problem.

[chrisjj]

The problem is that the operation gives an incorrect result. It duplicates the %1 part of the filename.

[Florian]

I don't think so.

The old file name pattern %1\%2\%3 in your example results in
%1 02480002922629
%2 1
%3 1.wma

Since the file name is always specified after the last directory separator \ the new file name will be 1.wma. But you also told Mp3tag to move this file into a directory structure %1\%2\ which is 02480002922629\1\ after replacing the placeholders.

[chrisjj]

you also told Mp3tag to move this file into a directory structure %1\%2\
which is 02480002922629\1\ after replacing the placeholders.

Sure, but I expected that directory structure to be at the position I specified in Old filename pattern. I.e. the new pattern is supposed to replace the old i.e. at the same position.

Experimenting more, I find that operation ignores the position of the old filename pattern, and uses instead the current directory. This looks like a fault to me. Certainly it is undesirable behaviour e.g. it makes it impossible swap %1 and %3 in this case.

Florian, I woinder if this is related to the V2.39->V2.40 change of behaviour reported in [X] Bug Or New Feature ? .

[Florian]

It's not the way it works

1. It's used to rename files, not directories
2. As a bonus feature it can be used to create new directories (using path separators in the new file name)
3. Using the current directory is not a fault but desired behaviour.

[chrisjj]

It's not the way it works

We sure agree on that!

Using the current directory is not a fault but desired behaviour.

Well, it is currently /undefined/ behaviour, so I REALLY think it ought to be mentioned in the Help. It is no fun at all to find out the hard way that that same Converter input can give totally different results another day just because the files were loaded in a different way, or because Add Directory was used, putting a completely inappropriate current directory on the previous files.

Thanks for your time, Florian.