Document the work. Share what you learn.
Bassilisk is an archive and community for DIY audio. Keep a project’s photos, parts, wiring, measurements and build notes together.
Browse other authors’ work, follow a guide or document your own prototype. Add detail as the project develops.
Choose English or German for the interface. Site help articles also have German translations. Language labels identify author contributions; they do not translate the work.
Find information and parts
A driver’s datasheet tells you what it is. An article helps you understand what that means for your enclosure, crossover, or measurement. Another build shows how someone put those decisions into practice.
Understand the problem
The Articles help hub starts with tasks: finding information, documenting a build and using the community. Technical articles explain concepts, methods and faults. Start with your question.
Find an explanation or a methodIdentify the actual part
The parts library keeps model codes, variants, specifications, and source links together. Your build references those shared records; one-off pieces can be recorded as custom parts.
Check a part’s identity and specificationsDocument a build
A build page separates what you made from the instructions to make it again. You can publish a Showcase on its own, or add a Build Guide when you have the details to share.
Showcase
What you made
- The project
- Photos, description, specifications and project status.
- The result
- Measurements with the equipment and capture method that give them context.
Build Guide
How to make it
- The ingredients
- Exact parts, quantities, tools and costs.
- The method
- Steps, system diagrams, dimensions, files and known issues.
A project can be Finished while its guide is still partial. Check both before committing to a build.
Discuss a project
If the crossover does not sum as expected, share the traces and describe how you took them. If a part rattles, show where it is mounted. The forum is where you can work through a question with other builders.
The context travels with the question.
A forum thread can link to a published build and appear in that build’s discussion section. The thread author can mark a reply as the answer. Solved points to that answer; the discussion stays open.
Record results and later changes
A published page does not have to be the last word. Record a repair, a revised crossover, or what you learned after months of use. Other builders can add experience from their own attempts.
- Journal
- A dated timeline keeps later changes and photographs together, with links to individual posts.
- Review
- After building or seriously testing a guide, explain the result, add your own photos, and say whether you would build it again.
- Remix
- A separate build credits the original and explains what you changed, where the source licence permits a remix.
- Competitions and exhibitions
- Keep event dates, results, photographs and sources with the build.
Follow the authors behind the work. Team profiles bring a group’s identity and member list together. An author can credit a Team on a build; the build stays theirs to edit.
Public Build of the Month selections are currently paused.
Leave enough for the next builder.
Name the exact part. Record the test conditions. Mark an unfinished step or a known issue. Credit the source, and state the permissions for your guide and files.
Build submissions go through review before publication. When you revise a published build, the approved version stays visible while your changes are reviewed. Access to a guide or download is separate from permission to reuse it.
From one boombox to an archive
Bassilisk started with the OG Bassilisk Boombox and the work of documenting it. The archive gives that same detail a place on other projects: what went into them, how they were built, and what changed afterward.
The site is maintained by Konstantin Bobylov. For maintainer contact, write to info@bassilisk.com. See the Impressum for operator details.