A folder labeled tou appears on a secondhand hard drive purchased at Akihabara. Inside: 14 files with names like tou001.wav, tou002.wav, and a single JPEG titled tou_cover.jpg. No artist name, no label, no year. The file dates are consistent – all from late 2004. The JPEG shows a blurred photocopy of a cassette shell with handwritten kanji partially obscured by wear. This is the reality of the Japanese noise archive: a world where meaning is encoded in fragments, and tou is one of the most persistent yet opaque three-letter codes circulating among collectors.
The Anatomy of a Three-Letter Code
In the trading circles of Japanese noise – especially the pre-torrent, pre-Stream era of the late 1990s and early 2000s – filenames often followed an informal shorthand. Labels, artists, and even specific releases were reduced to three or four characters to fit the 8.3 filename limitations of early storage media or simply to save space on floppy disks and CD-Rs. Tou appears in at least three distinct contexts:
- As a prefix for numbered tracks (
tou001,tou002…), suggesting a single release or compilation. - As a standalone folder name containing mixed media (audio, image, text).
- As part of a longer string like
tou520ortou_xxx, where the number may indicate a catalog code or a date.
The ambiguity is deliberate. Many of these files were created by anonymous uploaders on platforms like Tumblr, where the original context was stripped. The code tou could be an abbreviation for Toukyou (Tokyo), Touon (a sound-related word), or a truncated label name. Unlike the well-documented tesco series, which has been traced to a specific mail-order catalogue (see The Mystery of Tesco 3: A Ghost in the Japanese Noise Underground), tou lacks a clear origin point.
Decoding Through Context
When a collector encounters a tou file, the first step is to examine the accompanying metadata. The JPEG often holds the most clues. In the example above, the photocopied cassette shell shows a partial logo – a circle with two intersecting lines – that resembles the mark used by the label Toukyou Kikaku on certain limited runs in the late 1990s. But without a clear scan, this remains speculation. The audio files themselves, when playable, may reveal genre markers: heavy distortion, abrupt cuts, and the telltale hiss of Type I tape point toward a live recording or a bedroom session.
A more systematic approach involves cross-referencing the number suffix. The 520 suffix, for instance, appears in many orphan noise files – wasted05 2 520, tesuco520 bl, sludge520 – and has been linked to a particular batch of CD-Rs distributed through the Tesco network in the early 2000s. The tou520 variant might belong to the same cohort, but the link is tenuous. The sludge series, examined in Decoding sludge007 cv2: A Japanese Noise Archive Artifact, shows how a consistent prefix can help map a distribution chain; tou lacks that consistency across multiple sources.
The Role of File Extensions and Formats
File extension choices also provide information. .wav files suggest a direct rip from a CD or a digital master, while .mp3 at low bitrates (128 kbps or below) indicates an early internet upload. The tou folder described earlier contains only .wav files, which is unusual for a Tumblr-era post – most Tumblr noise uploads used compressed formats. This suggests the original source was a physical medium (CD-R or hard drive) rather than a streaming rip. The file dates (2004-10-12 to 2004-10-15) cluster tightly, implying a single ripping session. Collectors who have encountered similar tou folders report that the audio content tends to be extended drone pieces with heavy low-frequency feedback, a style associated with the Kansai noise scene of the early 2000s.
Practical Tips for the Collector
If you find a tou file in your archive, resist the urge to rename or reorganize it immediately. Preserve the original folder structure and file names. Create a text file with any contextual notes: where you acquired the drive, the date, any other files in the same parent folder. Use a hex editor to examine the JPEG’s EXIF data – sometimes the camera model or software used can hint at the original uploader. The Olympus C-4 Zoom, for example, appears frequently in early 2000s noise photography, and its metadata can help date a scan.
- Check for accompanying
.txtor.nfofiles – they are rare but occasionally contain tracklists or artist names. - Compare the file hash with known databases like the Noise Archival Project (offline, but mirrored in private collections).
- Post the filename (without the audio) on forums dedicated to Japanese underground music – community memory is the best resource.
One collector reported that a tou folder he had stored for years turned out to be a live recording of Masonna from a 2003 show at Koenji – the connection was made only after someone recognized the faint outline of a venue stamp on the JPEG. The code tou itself was meaningless; the meaning came from the surrounding fragments.
The Persistence of the Fragment
Why does tou persist? Because the Japanese noise underground was never concerned with clean metadata. Cassettes were traded without tracklists, CD-Rs were burned with Sharpie labels that faded, and digital files were uploaded with whatever name the uploader chose at the moment. The three-letter code is a residue of that carelessness – and it is precisely that residue that makes the archive feel alive. Every tou file is a question without a definitive answer, a node in a network that exists only in the gaps between hard drives. The next time you see tou in a filename, check the file dates, the folder hierarchy, and any accompanying text files. That metadata, however sparse, is the only map you have.