I made a script:



But instead of copying all values from DISC tags to DISCNUMBER tags it only removed the DISC tags... why doesn't it copy the contents of the former tag field to the later?

Confirmed!
The copy field action does not function properly
I've done some tests:

1. Copy DISC to DISCNUMBER removes both fields
2. Copy DISC to PERFORMER () removes DISC and inserts DISCNUMBER (PERFORMER it is not written)

Oddest stuff I've seen in a while

I believe "DISC" and "DISCNUMBER" are treated as equivalent internally by foobar2000.

Copy field works just fine. However, the information for a song is reloaded from the file before the selected masstagger actions are applied, and depending on the file format, the latest version of the relevant decoder now uses DISCNUMBER as fieldname instead of DISC. In essence, merely reloading information from files would have done what you want, but additionaly applying this masstagger script has messed things up, because the DISC field no longer existed.

That's true but that has nothing to do with the problem (well obviously it has more to do with it than it should... I'm assuming that exactly this feature of foobar2000 is causing trouble with the Masstagger.)

Well foobar treats both tag fields equally I know, but so what? It doesn't help me at all and is not the solution to this problem. I want the real tag field to be changed from DISC to DISCNUMBER by the Masstagger. As a tagging tool I can expect it to do what I tell it, can't I? I don't care if foobar treats them equally, because I want all my tag fields named in a consistent fashion in order to make other applications work in an expected way, because they don't treat DISC and DISCNUMBER equally, they either accept the one or the other depending on what I tell them to accept.

Anyhow the "Copy <field> to <field>" seems to be broken when the first <field> is either DISC or DISCNUMBER: the contents of those tags don't get transferred and the old disc-tags get deleted. That can't be right.

EDIT: /\ posted before your reply, foosion




You mean foobar automatically renames the DISC tag to DISCNUMBER? I haven't notice that...

EDIT2: Nope, I can't comprehend what you are saying, I tagged a set of mp3s with a DISC tag "1" and did "Reload info from files" and the "1" was still stored in a tag named DISC, even "Update files" or "Rewrite tags" will retain the old tag names.

EDIT3: Or are you saying since the Masstager already translated the DISC tag to DISCNUMBER internally, I should do something like "Copy DISCNUMBER to DISCNUMBER"? Doesn't work either... DISC gets deleted although it wasn't even mentioned in the Masstagger script (I removed the Remove "DISC"). I'm confused, can you explain this behaviour again? I think I don't get what's happening here...

I am saying that the latest version of the input component for a particular file format probably reads the DISC tag written by an older version of this input component as DISCNUMBER. However, unless you tell us what file format you did this with, this is merely speculation.

Since both the %disc% and %discnumber% fields are remapped accordingly, you wouldn't notice this on the titleformatting level, unless you use $meta() to access those fields. The "Copy field" action in masstagger does however not use field remappings.

By the way, I tested the "Copy field" action and it works as expected.

Those are mp3 files with APEv2 tags written by Mp3Tag...

EDIT: Ok, I think I found the root of the problem. I tested the same Masstagger commands again with the same mp3 files except that I changed the tag format from APEv2 to ID3v2.4 and everything worked out fine.


EDIT2: Tested it with WavPack encoded files which have APEv2 tags and converting the tag names from DISC to DISCNUMBER and back also works flawlessly. Seems to be a mp3+apev2 only issue. (one more reason to finally switch back to id3v2.4... ^^).




I see, thanks for the clarification.