Visit Preferences to set your user name
Notice: Spamming this wiki will have no effect on your Google page rank; all external links are passed through a redirect script.
== Etree.org Conventions for File Distributions == For many reasons, files distributed via etree.org should follow the etree.org naming system. When filesets are consistently named and organized, they are easier for downloaders to identify, catalog, archive and keep track of. Badly named files are confusing when they do not identify the artist or track properly. Worse, files with spaces or characters like ?s or 's do not always work on every operating system. There are other reasons for using the etree.org naming standard, which has developed over time to benefit the entire community. Please use this naming scheme along with our SeedingGuidelines when creating new filesets (aka "seeds"). The separate [http://www.archive.org/details/etree Live Music Archive] collection at the [http://www.archive.org Internet Archive] also asks for these naming standards for [http://www.archive.org/about/faqs.php#119 uploads] of [http://www.archive.org/about/faqs.php#100 allowed material] to their site. There are slight differences in naming between ((Shorten)) and ((FLAC)) sets. Both are covered below. '''New: ExtendedNamingStandards''' - Top directory names that hold even more information are quickly becoming a preferred convention for seeded shows. These standards are especially handy when multiple versions circulate for a date. Please read them after reading through this page. === Basic Naming Scheme for Both Shorten and FLAC Sets === Every file in a set (whether .shn, .md5, .txt, .flac, etc) and any directory for the set should have a name which starts like this: :{{bbyyyy-mm-dd}} :{{^^^^^^ ^^ ^^}} :{{|||||| || \\___ Day (with leading zero)}} :{{|||||| ||}} :{{|||||| \\______ Month (with leading zero)}} :{{||||||}} :{{||\\\\_________ Year (Full 4 digit year)}} :{{||}} :{{\\___________ Band Abbreviation, lowercase preferred (e.g. ph = Phish, see BandAbbreviations for examples)}} Use only letters, numbers, hyphens (-), and when necessary, periods (.) or underscores (_). '''Do not''' include spaces, ampersands (&), slashes or any other special characters. They cause problems in many cases. One [http://www.archive.org/about/faqs.php#216 list of disallowed characters] can be found in the [http://www.archive.org/details/etree Live Music Archive] FAQ. Shorten and FLAC sets will differ in what comes after this part, as follows: === a) ((Shorten)) Distributions === All files in a "shn set" must be enclosed within a directory (aka folder). This makes them easy to sort and transfer as a group. The directory name should follow the Basic Naming Scheme, but with a .shnf extension appended. The "f" is for "folder", to show that you're looking at a directory rather than a .shn filetype. (The difference would be obvious at a glance in Windows, but not necessarily in other operating systems like Unix.) Inside this directory, place the info file (.txt) for this seed, the .shn files each named by CD disc and track, and the .md5 checksums for the .shn files. See SeedingGuidelines for tips on writing a proper info file and generating .md5 files. Below is an example of what a shn set should look like: :{{ph2000-04-20.shnf <--- Directory for the set- the f shows it's a "folder"}} ::{{ph2000-04-20.md5 <--- md5 checksum file for all discs together}} ::{{ph2000-04-20.txt <--- Show info file}} ::{{ph2000-04-20d1t01.shn \}} ::{{ph2000-04-20d1t02.shn \ __ disc one .shn files }} ::{{ph2000-04-20d1t03.shn /}} ::{{ph2000-04-20d1t04.shn /}} ::{{ph2000-04-20d2t01.shn \}} ::{{ph2000-04-20d2t02.shn \ __ disc two .shn files}} ::{{ph2000-04-20d2t03.shn / }} ::{{ph2000-04-20d2t04.shn /}} ::{{ph2000-04-20wav.md5 <--- optional md5 checksum file for your original wavs}} '''Optional:''' Instead of ::{{ph2000-04-20.md5 <--- md5 checksum file for all discs together}} you may use ::{{ph2000-04-20d1.md5 <--- md5 checksum file for disc 1}} ::{{ph2000-04-20d2.md5 <--- md5 checksum file for disc 2}} '''Important:''' Place a 0 before any single-digit track number (1 to 9). Without the 0, 10 would come before 2 during file sorting. This can mess up track orders when the decompressed files are burned to audio discs. === b) ((FLAC)) Distributions === FLAC directory naming has an extra twist compared to Shorten. The FLAC codec supports both 16-bit and 24-bit content, in contrast to Shorten, which supports only 16-bit audio content. Because of these multiple bit-depths, we use the {{'''.flac16'''}} and {{'''.flac24'''}} naming convention to distinguish each type. '''Don't''' use {{'''.flac'''}} or {{'''.flacf'''}} when naming a directory. These distinction are important! Some reasons to care: *Using {{'''.flac'''}} as a directory suffix will confuse the upload checking software at the [http://www.archive.org/details/etree Live Music Archive], and may confuse regular users too. This extension makes the directory look like a file, instead of a whole directory. *Typical downloaders will want to watch for {{'''.flac16'''}} seeds. The 16-bit encoded FLAC files can be turned directly into traditional audio CDs, just like we do with Shorten files. *As the lossless audio community slowly adopts and purchases 24 bit capable gear (or FLAC-capable hardware decoders), the demand for higher-quality audio recording resolutions will increase. In addition, users without 24 bit audio support will want to know to stay away from {{'''.flac24'''}} folders because they won't be able to take advantage of the additional audio clarity that 24 bit recordings offer. *Tapers and seeders who want to archive their original 24 bit content, in addition to the 16 bit audio that they seeded for wider distribution, can use the {{'''.flac16'''}} and {{'''.flac24'''}} folder extensions to archive files easily on larger storage media such as DVD-R/RW and DVD+R/RW. All files in a "flac set" must be enclosed within a directory (aka folder). This makes them easy to sort and transfer as a group. The directory name should follow the Basic Naming Scheme. Inside the .flac16 or .flac24 directory, place the info file (.txt) for this seed, the .flac files (each named by CD disc and track if appropriate), and a file containing the FlacFingerprint (ffp.txt) of every .flac file. See SeedingGuidelines for tips on writing a proper info file. Below is an example of what a 16-bit flac set should look like, tracked for audio CDs. It's possible 24-bit flac sets* might be laid out differently, given archiving needs. :{{ph2003-04-20.flac16 <--- Directory for the set}} ::{{ph2003-04-20.txt <--- Show info file}} ::{{ph2003-04-20ffp.txt <--- FlacFingerprint file for the wav portion of the .flac files}} ::{{ph2003-04-20d1t01.flac \}} ::{{ph2003-04-20d1t02.flac \ __ disc one .flac files }} ::{{ph2003-04-20d1t03.flac / }} ::{{ph2003-04-20d1t04.flac /}} ::{{ph2003-04-20d2t01.flac \}} ::{{ph2003-04-20d2t02.flac \ __ disc two .flac files}} ::{{ph2003-04-20d2t03.flac / }} ::{{ph2003-04-20d2t04.flac /}} ::{{ph2000-04-20.md5 <--- optional md5 whole-file checksum file for your .flac files}} ```*```Mike Wren writes: "We still need someone to write up a seeding standard for 24bit audio (how do we track, how do we archive for DVD-A support, etc.). I'll be bugging people about this --MW" '''Important:''' Place a 0 before any single-digit track number (1 to 9). Without the 0, 10 would come before 2 during file sorting. This can mess up track orders when the decompressed files are burned to audio discs. === File Sorting Note === Prior etree.org standards called for the use of second-level directories within filesets, such as {{'''ph2000-04-20d1.shnf'''}}, with each disc's worth sorted into an individual folder. We now feel that is unnecessary. As long as each file denotes disc and track, that should be good enough. Likewise, prior Shorten naming standards called for each disc's worth of shns to have its own .md5 file. However, if all .shn files are sorted into a single directory as suggested above, it is natural to generate a ''single'' .md5 file for the whole bunch. You will still see many disc-sorted filesets and checksums in circulation. '''''Either way, sorted or together, is fine.''''' There is ''no'' need to change old directory structures or .md5 file arrangements. === Handling Mics Or Other Source Info === Often, it's convenient to include mic info or other important source information in the filename itself. That way, two filesets from the same date, but from different sources, won't conflict with each other. The best way to do this is to put the unique info after the date and track part of the filename, and before the extension. For example, these all work: :{{ph2003-03-01.dpa.shnf}} :{{ph2003-03-01-nak.shnf}} :{{ph2003-03-01cmc6.shnf}} '''Do not''' use the "&" character, because most operating systems [http://www.archive.org/about/faqs.php#216 won't accept it] in a filename. Naturally, individual files would be named the same way -- all extra info goes after the date info and before the file extension, like this: :{{gd1973-02-09d1t01bertha.shn}} :{{gd1973-02-09berthad1t01.shn}} Either way works OK, although the first example is better than the second. Done this way, files and directories will still sort correctly, two filesets from a single band and date won't conflict or overwrite each other, and users can tell the source at a glance. Also, FurthurNet will accept files shared this way. It won't accept them if you put the source information anywhere else in the filename. === Other Naming Resources === Related sites with sensible naming conventions for filesets: *[http://www.furthurnet.org FurthurNet]- As of version 1.7.2, uses an enforced [http://forums.furthurnet.com/viewtopic.php?t=7994 naming convention] similar to above. Abbreviations they use can be found on their [http://furthurnet.org/bandlist/ Bandlist]. *[http://www.archive.org/details/etree Live Music Archive]: **Naming conventions are enforced to exclude special characters, see [http://www.archive.org/about/faqs.php#216 FAQ item] and [http://www.archive.org/iathreads/post-view.php?id=8944]. **5/2006+, new upload system at LMA: In the first step of the "item creation" process for new-system uploads, you will be walked through creation of the "identifier" for the fileset. This will become the fileset's directory at the site, into which you will upload the files. The naming scheme for the identifier is based on these standards. **Normal ''all-letter'' band abbreviations should go right next to the year, ''no'' hyphen, like sciyyyy-mm-dd. In contrast, the few ''number-containing'' abbreviations (eg, sts9 or 311) can take a hyphen there for clarity, like sts9-yyyy-mm-dd. Some handy tools for renaming files are [http://hp.vector.co.jp/authors/VA014830/english/FlexRena/ Flexible Renamer], [http://www.rlvision.com/flashren/about.asp Flash Renamer], [http://www.herve-thouzard.com/modules/wfsection/article.php?articleid=1 THE Rename] (Windows free/shareware). Be careful not to rename all the files on your hard drive accidentally, though! ''See also: ExtendedNamingStandards, SeedingGuidelines, BandAbbreviations, BandAbbreviationGuidelines, LiveMusicArchive, FurthurNet'' ---- Thanks to [http://groups.yahoo.com/group/pcp/ People for a Clearer Phish] for developing the original standards.
Summary of change:
Add document to category: