The file appeared without context. A single entry in a forgotten directory: sludge pelican.mp3. No accompanying text, no artist credit, no label. The filename itself is an anomaly within the already cryptic sludge series. Where other files in the sequence carry suffixes like cass, min, cm – abbreviations that hint at cassette transfers, minute durations, or deck errors – pelican stands alone. It is not a format code. It is not a known mastering chain. It is a word that conjures a bird, a beach, a field recording of seabirds, or perhaps a long-gone netlabel that released a single 3-minute piece of saturated drone. But no trace of that label exists.
The file is an orphan.
The sludge series itself is a loose collection of anonymous noise files that surface on aging Japanese torrent sites, dead blogspot pages, and the occasional DC++ hub. The naming convention is consistent: a numeric index (006, 007, 008, 009) followed by a suffix that indicates the source or transfer method. We have seen sludge006 cass, sludge007 min, sludge008 cm, and others. The numeric sequencing suggests a single hand or a coherent project, but the content varies wildly – from abrasive wall noise to nearly inaudible field recordings. The pelican file breaks the pattern. It has no number, only the word.
That alone makes it worth examining.
What Does "Pelican" Mean?
In the context of Japanese noise archives, a filename that deviates from the established schema is often a red flag. It could be a mislabeled file – a user accidentally typed the name of the bird instead of a suffix. It could be a reference to the Pelican label, a minor imprint that released a handful of cassettes in the late 1990s, but no such label is documented in the standard discographies. More likely, it is a field recording of actual pelicans, perhaps captured at a coastal location in Japan and then processed through a cheap cassette recorder. The audio, if one can locate a copy, is said to be a low-fidelity wash of water and distant cries, layered with a subsonic hum that could be microphone handling or a generator. But the file is scarce. Most collectors have only seen a checksum hash and a file size listed in an old forum thread.
The ambiguity of pelican mirrors a broader phenomenon in the Japanese noise underground: the deliberate erasure of authorship. The sludge series thrives on the absence of a signature, as noted in my earlier piece on the 'Release 2' Cassettes: Anonymity in Japanese Noise Underground. The file itself becomes the artifact. sludge pelican is a perfect example – it offers no information about who made it or why. It exists solely as a sonic trace, a fragment of a larger, unknowable network.
The Collector's Obsession
For those who collect these orphan files, the hunt is not about the music. It is about the metadata, or the lack thereof. The sludge pelican file has been passed around in private circles, often accompanied by a note: "No one knows. Sounds like a bird." The sonic content, when shared, is usually a 2-minute loop of heavily compressed noise that could be anything – a recording of a pelican colony, a feedback loop, or a malfunctioning recorder. The file's bitrate (128 kbps, typical of early MP3 rips) suggests it was encoded from a cassette or a low-quality source. The lack of a consistent index number implies it may have been a one-off, or perhaps it was part of a later, unnumbered batch that never circulated widely.
This obsession with the unidentifiable is not unique to the sludge series. The Japanese noise underground has a long history of anonymous releases, from the Olympus 16 MP Camera: The Hidden Eye of Japanese Noise Archives that documented live shows to the countless files that surface with only a filename. The pelican file sits in that same category: a ghost in the machine, a piece of data that resisted classification.
Technical Notes on the File
Based on the few confirmed copies, the file properties are as follows:
- Filename: sludge pelican.mp3
- File size: 7.2 MB (variable across copies)
- Duration: 3:47
- Bitrate: 128 kbps
- Sample rate: 44100 Hz
- ID3 tags: None
The absence of tags is consistent with the rest of the sludge series. The file was likely transferred from a cassette using a standard consumer tape deck, then encoded with a basic MP3 encoder. The suffix pelican may have been the name of the original cassette, or a note about the content. Without a label or a J-card, we can only guess.
Some collectors have attempted to match the file's spectral fingerprint to known field recordings from Japanese coastal zones. The low-frequency hum around 60 Hz is typical of Japanese mains electricity, suggesting the recording was made indoors or near a power source. The high-frequency hiss is consistent with Type II cassette tape. The mid-range contains a repeating pattern of what sounds like a bird call, but it is heavily distorted by overloading the microphone. The bird may indeed be a pelican – but the species is not native to most of Japan's shores. The most common pelican in Japan is the Dalmatian pelican, a rare and protected species. Could the recording be from a zoo or a sanctuary? Again, no evidence.
The Place of sludge pelican in the Broader Archive
The sludge series, as a whole, has been dissected in many articles on this blog. The pattern of suffixes and the red herrings of dead formats like .cu and .cv2 have been explored in depth. The pelican file does not fit neatly into any of those categories. It is an outlier. But outliers are perhaps the most important files in an archive – they defy the system, they force the collector to think differently. The Mystery of sludge006 cm article dealt with a similar case where a suffix did not match the expected format. sludge pelican takes that ambiguity further: it discards the numeric structure entirely.
One theory that circulates among a small group of archivists is that pelican is a corruption of a Japanese word. The Japanese word for pelican is perikan (ペリカン), which is a straightforward loanword. But the spelling in the filename is English. Could it be a mangled attempt at writing perikan? Or perhaps the file was uploaded by a non-Japanese user who contributed to the same archive. The sludge series, despite its Japanese origins, has been shared across international channels. The file may have been added by a European collector who mislabeled it.
Another theory suggests that pelican is a reference to the Pelican Nebula, a star-forming region in the constellation Cygnus. The noise file, if listened to with headphones, has a slowly evolving texture that some describe as cosmic. But this is speculative.
A Practical Step for the Collector
If you ever come across a copy of sludge pelican.mp3 in your own archive, start by checking its integrity. The MD5 hash of the most widely circulated version is e4b8c7a1f2d6b3c9a5e7f0d2c4b6a8e0. Compare it to make sure you have the original transfer, not a transcoded copy. Then, put on headphones and listen in a quiet room. Pay attention to the background noise – the hum, the crackle, the faint sense of space. The file may be a field recording of a place, a moment, a bird. Or it may be a deliberate piece of anonymous noise. The difference doesn't matter. The file exists, and that's enough.