Tango.info track tagger: Difference between revisions
(→Bug3) |
(→Bug3: format_string=%dummy%) |
||
Line 103: | Line 103: | ||
07798108080255-1-1 | 07798108080255-1-1 | ||
gives three lines | gives three lines | ||
If the %year% is filled in case Bug2 is fixed, one can use format_string=%dummy% to test this bug. | |||
====Bug4==== | ====Bug4==== |
Revision as of 2012-07-03T17:13:39
To be used for tango.info music tagging.
Name
It was suggested to use the name "track tagger" instead of "music tagger", since a track may contain non-music [1].
Usage
The tagger has two input boxes
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.2.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.2.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=%2807798082984082 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
Development
Latest version: https://tango.info/tools/tagger1.3.2.php
- 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 music 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!
- looks good
- Chrisjjj
- output is customisable
- 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'
- Breaks back-compatibility of usage as FORM action: argument textarea with name 'input' now ignored
- puts warning text HTML code in tag list https://tango.info/tools/tagger1.3.2.php?track_references=http://chrisjj.com/notfound.html
- Chrisjjj
Bugs
Bug1
in URI mode (only), failure on track reference parsing
- fine
NOTE: Acceptance of URL in track references field is undefined behavior! Chrisjjj 2010-12-03T11:29:05 (UTC)
- fails
each tint contained thrice, source for one tint:
<a href="https://tango.info/00743212200621-1-2" class="external free" title="https://tango.info/00743212200621-1-2" rel="nofollow">https://tango.info/00743212200621-1-2</a>
Bug2
%year% can be missing, while page shows a year
On V1.3.2, %year% can fail, returning a null string instead of the year value e.g. track page shows year 1941:
http://img442.imageshack.us/img442/1194/trackbendigotunombretan.png
but using format string %year%, tagger tag list shows null:
http://img855.imageshack.us/img855/3026/tangoinfogooglechrome.png
This did not happen on a track the date of which had month and day.
Bug3
null output can cause a missing tag list line
On V1.3.2, null output from a field (such as caused by the %year% failure reported separately) can cause a missing tag list line, leading to misaligment of tag lines v. tracks and hence to severe mistagging. E.g. http://img163.imageshack.us/img163/3026/tangoinfogooglechrome.png
This did not happen where the track line generated other output e.g. from format string %year%; .
Not always missing:
07730725820029-1-1 07730725820029-1-1 07798108080255-1-1 gives two lines 07798108080255-1-1 07730725820029-1-1 07798108080255-1-1 gives three lines
If the %year% is filled in case Bug2 is fixed, one can use format_string=%dummy% to test this bug.
Bug4
Tag list and Process message layout
On V1.3.2, Tag list and Process message: are on the same line, as if a line break was missing.
http://img163.imageshack.us/img163/3026/tangoinfogooglechrome.png