(windows) command line m4a tagger?

[skeptic Mike]

(21-11-2017 09:10)simoncn Wrote:  What exactly do you mean by "putting the different data atoms under the same atom path"?

using AtomicParsley with -T option to dump the information. First this is three PERFORMERS as written by AtomicParsley:

Atom ---- @ 1355513 of size: 147, ends @ 1355660
Atom mean @ 1355521 of size: 28, ends @ 1355549
Atom name @ 1355549 of size: 21, ends @ 1355570
Atom data @ 1355570 of size: 27, ends @ 1355597
Atom data @ 1355597 of size: 34, ends @ 1355631
Atom data @ 1355631 of size: 29, ends @ 1355660

This is the same as written by mp3Tag:

Atom ---- @ 1361620 of size: 87, ends @ 1361707
Atom mean @ 1361628 of size: 28, ends @ 1361656
Atom name @ 1361656 of size: 21, ends @ 1361677
Atom data @ 1361677 of size: 30, ends @ 1361707
Atom ---- @ 1361707 of size: 86, ends @ 1361793
Atom mean @ 1361715 of size: 28, ends @ 1361743
Atom name @ 1361743 of size: 21, ends @ 1361764
Atom data @ 1361764 of size: 29, ends @ 1361793
Atom ---- @ 1361793 of size: 84, ends @ 1361877
Atom mean @ 1361801 of size: 28, ends @ 1361829
Atom name @ 1361829 of size: 21, ends @ 1361850
Atom data @ 1361850 of size: 27, ends @ 1361877

so, each tag has it's own hierarchy of atoms for one data atom (i.e. actual Performer name). Logically the AtomicParsley version conveys the same information by putting all the data atoms in the same hierarchy.

Presumably Paul Taylor will know how he handles this in his java library. My guess would be the same way that mp3Tag does. It's possible that the mp4 standard would tell which is more formally "correct".