RandoloWiki

Too much of everything is just enough!

User Tools

Site Tools

Trace:
audiodb:gat

Jump to a different year? Take your pick! ☸ 2000 ☸ 2001 ☸ 2002 ☸ 2003 ☸ 2004 ☸ 2005 ☸ 2006 ☸ 2007 ☸ 2008 ☸ 2009 ☸ 2010 ☸ 2011 ☸ 2012 ☸ 2013 ☸ 2014 ☸ 2015 ☸ 2016 ☸ 2017 ☸ 2018 ☸ 2019 ☸ 2020 ☸ 2021 ☸ 2022 ☸ 2023 ☸ 2024 ☸

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
audiodb:gat [2019/09/02 21:30] – [Basic Tag Definitions] randoloaudiodb:gat [2020/06/14 23:54] (current) – external edit 127.0.0.1
Line 1: Line 1:
-====== Guidelines for Audio Tagging (GAT), version 2.4 ======+====== Guidelines for Audio Tagging (GAT), version 2.5 ======
 The goal of this document is to provide a logically consistent framework for tagging both commercial and noncommercial audio recordings in a relatively simple fashion (hah! fitting both needs together is a somewhat complex task that will require resolution of competing needs and exceptions!). This system grew out of frustration with the incompleteness/inconsistency of standard tagging systems (see [[http://wiki.hydrogenaudio.org/index.php?title=Tags|Hydrogen Audio]]'s terrific primer page for additional background). The goal of this document is to provide a logically consistent framework for tagging both commercial and noncommercial audio recordings in a relatively simple fashion (hah! fitting both needs together is a somewhat complex task that will require resolution of competing needs and exceptions!). This system grew out of frustration with the incompleteness/inconsistency of standard tagging systems (see [[http://wiki.hydrogenaudio.org/index.php?title=Tags|Hydrogen Audio]]'s terrific primer page for additional background).
  
Line 89: Line 89:
   ; [COUNTRY] : Full name of country, native (romanized) spelling preferred if location is a non-English speaking locale.   ; [COUNTRY] : Full name of country, native (romanized) spelling preferred if location is a non-English speaking locale.
  
-  ; CCODE : [[http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3|ISO-3166-1 alpha-2 three-letter country codes]] such as _USA_ and _DEU_. For CRM, this field can be used to indicate the release country for a particular media item (eg., to differentiate between US and British releases of the same alblum).+  ; CCODE : [[http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3|ISO-3166-1 alpha-2 three-letter country codes]] such as _USA_ and _DEU_. For CRM, this field can be used to indicate the release country for a particular media item (eg., to differentiate between US and British releases of the same album).
  
 ==== Date Tag Definitions ==== ==== Date Tag Definitions ====
Line 109: Line 109:
 ==== Detail Tag Definitions ==== ==== Detail Tag Definitions ====
  
-  ; PERFORMER : An alphabetized list where each entry is in the form +  ; PERFORMER : Ideally, this is an alpha-ordered list where each entry is in the form 
-  "name: instrument[, instrument2[,instrument3...]];<CR>"+  "name: instrument[, instrument2[,instrument3...]];"
   eg.,    eg., 
    "Jerry Garcia: guitar, vox;    "Jerry Garcia: guitar, vox;
Line 116: Line 116:
     Ron Tutt: drums."     Ron Tutt: drums."
  
-The final list element ends with a period instead of semicolon+<CR>. This field may be modified on a per-track basis. The field may also include conductors, choir-masters and any other contributors deemed worthy of note by the tagger, where the job function appears as an "instrument". This mode of usage obviates the need for specialized but little-used tags such as CONDUCTOR, LYRICIST, REMIXER and so on. +The final list element should terminate with a period instead of a semicolon. This field may be modified on a per-track basis. The field may also include conductors, choir-masters and any other contributors deemed worthy of note by the tagger, where the job function appears as an "instrument". This mode of usage obviates the need for specialized but little-used tags such as CONDUCTOR, LYRICIST, REMIXER and so on. 
-<WRAP important>While the preceding layout is designed for ease of readability, it doesn't make for ease of entry.\\ +<WRAP important>When viewed in a JSON editor, this sort of list will automatically be decomposed into it's individual elements. But as a raw tag, things are not so readabile, as each list element follows the next without whitespace (a newline would be terrific!), and asking for the list to be alpha-ordered doesn't make for ease of entry.\\ 
-Far better would be an unordered array {[name1, instrument1],[name2, intrument2],...} where alphabetization and consolidation of multiple entries is performed by the software rather than the user.\\ +Far better would be an unordered array {[name1, instrument1],[name2, intrument2],...} where alphabetization and output-formatting of multi-element entries is performed by the software rather than the user.\\ 
-However, sorting a list of names in a manner that catches all of the weirdness allowed in English usage has stymied many a programmer. If anyone knows how to program Foobar 2000 to accomplish this task, please let me know!+Unfortunately, sorting a list of names in a manner that catches all of the weirdness allowed in English usage has stymied many a programmer. If anyone knows how to program Foobar 2000 to accomplish this task, please let me know!
 </WRAP> </WRAP>
 Also, as of v2.4, this field _may_ include markdown formatting (most likely initial bullets: "* "), but such visual markup is **NOT** required. Also, as of v2.4, this field _may_ include markdown formatting (most likely initial bullets: "* "), but such visual markup is **NOT** required.
 +As of v2.5, use of markdown formatting is discouraged -- a tag is considered raw content, not formatted data.
  
   ; CREDITS : Free-form field giving the name (and possibly email address) of one or more persons involved in recording, transferring, encoding and sharing of this recording. New references/comments should appear on new lines. Samples follow.   ; CREDITS : Free-form field giving the name (and possibly email address) of one or more persons involved in recording, transferring, encoding and sharing of this recording. New references/comments should appear on new lines. Samples follow.
Line 175: Line 176:
   ; [NOTES] : Optional free-form field for any other comments or information about the recording. COMMENT should map to this field (NOTES was chosen over COMMENT for brevity).   ; [NOTES] : Optional free-form field for any other comments or information about the recording. COMMENT should map to this field (NOTES was chosen over COMMENT for brevity).
  
-  ; TAGSYS : The string 'GATvN.M = where N.M version number of this tagging system -- 2.4 at present! This field is used to provide backwards compatibility in foobar string coding - ie., to let the software to know to process v1 tags differently than v2.+  ; TAGSYS : The string 'GATvN.M = where N.M version number of this tagging system -- **GATv2.5** at present! This field is used to provide backwards compatibility in foobar string coding - ie., to let the software to know to process v1 tags differently than v2.
  
   ; ISO639-2 : 'eng' unless you are tagging in another language, in which case that [[http://en.wikipedia.org/wiki/ISO_639-2|ISO code]] goes here instead. The goofy fieldname arises because that's the ISO standard reference number for these codes.   ; ISO639-2 : 'eng' unless you are tagging in another language, in which case that [[http://en.wikipedia.org/wiki/ISO_639-2|ISO code]] goes here instead. The goofy fieldname arises because that's the ISO standard reference number for these codes.

Jump to a different year? Take your pick! ☸ 2000 ☸ 2001 ☸ 2002 ☸ 2003 ☸ 2004 ☸ 2005 ☸ 2006 ☸ 2007 ☸ 2008 ☸ 2009 ☸ 2010 ☸ 2011 ☸ 2012 ☸ 2013 ☸ 2014 ☸ 2015 ☸ 2016 ☸ 2017 ☸ 2018 ☸ 2019 ☸ 2020 ☸ 2021 ☸ 2022 ☸ 2023 ☸ 2024 ☸

audiodb/gat.1567481426.txt.gz · Last modified: 2019/09/02 21:30 by randolo

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki