Tango.info track tagger

To be used for tango.info track tagging.

Name

It was suggested to use the name "track tagger" instead of "music tagger", since a track may contain non-music [1].

The tool only delivers track meta data, it does not write tags into files, so "tagger" might be a misnomer.

In v1.3.3 the h1 tag for the tool was changed from "Tool: Tagger" to "Tool: Track tagger".

Usage

The tagger has two input boxes

• tango.info track tagger track references
• tango.info track tagger format string

Submit presents an output box:

• For each track reference
  • that is a TINT, one line
  • that is a TINP or TINS either
    • one line e.g. https://tango.info/tools/tagger1.3.3.php?track_references=07798082984082, OR;
    • multiple lines, each of which corresponds to a track of the album or disc e.g. https://tango.info/tools/tagger1.3.3.php?track_references=07798105811609
      • NOTE: this addition since 1.0 breaks compatibility - previously an inadvertent TINP would have given one line and no mistagging; now can give a multiple lines, causing subsequent misalignment an extreme mistagging.
    • NOTE: this one/multiple variation is despite that t.i search shows no variation e.g. https://tango.info/?q=07798082984082 v. https://tango.info/?q=07798105811609

Each line consists of

• starting with "Error:" - an error
• not - tag data from one track, in the Format String format

Change log

• tango.info track tagger change log

Development

Latest version: https://tango.info/tracktagger/1.4.0

• https://tango.info/tools/tagger0.5.php - for album-by-album tagging (TINP based)
  • Fails on accented characters e.g. https://tango.info/tools/tagger0.5.php?tins=00724354169229-1-1&sepa=%3B -> accented characters replaced by two-character garbage
  • Fails on empty track references list e.g. -> Query failed : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER BY tango_albums.album_tin,track_num' at line 3
  • Fails on single track reference e.g. https://tango.info/tools/tagger0.5.php?tins=00724354169229-1-1&sepa=%3B -> ;;;;;;;; not found:Array ( [0] => ERROR ) NO GENRE:Array ( [0] => )
• https://tango.info/tools/tagger1.0.php - for track-by-track tagging (TINT based)
  • Note: 1.0 is not back-compatible with 0.5 - it does not accept bare TINPs.
• https://tango.info/tools/tagger1.3.php - work in progress
  • output is customisable
    • Chrisjjj
      • looks good
        • Stress test with 16819 lines was successful
        • Documentation: tango.info track tagger format string 2009-09-01T12:12:24 (UTC)
        • Incompatibility with previous versions: %artist% orch-voc separator changed
          • from ", " to ", voc: "
          • No workaround known. Replace format string "%artist%" with "%track_orch%, %track_voca%" generates incompatible ", -"
      • Needed is
        • statement of tag names' source tracks.csv fields
      • Desired is
        • Formalisation of interface for other pages (e.g. Mp3tag export output) to call by FORM ACTION
      • "Tag list" label is missing!
      • https://tango.info/tools/tagger1.3.1.php?input=http://chrisjj.com/notfound.html puts warning text HTML code in tag list!

• https://tango.info/tools/tagger1.3.2.php - work in progress
  • Chrisjjj
    • Breaks back-compatibility of usage as FORM action: argument textarea with name 'input' now ignored
      • Workaround: change parameter textarea 'input' to 'track_references'
  • puts warning text HTML code in tag list https://tango.info/tools/tagger1.3.2.php?track_references=http://chrisjj.com/notfound.html

Bugs

• tango.info track tagger bugs