The user manual and developer documentation for the Monolith HTP-1 home theater processor.
Read the documentation »
User Manual
·
Report a Problem
·
Suggest an Improvement
Table of Contents
The HTP-1 is a 16-channel home theater processor. What started as an effort to bring Dirac Live Active Room Treatment to the platform grew into a community-driven project, and the processor has gained a great deal along the way including Dirac Live ART, a redesigned front panel, a redesigned web interface, Seat Shaker, Channel Levels, and more.
This documentation is part of that effort: a living manual that keeps pace with the software, and open for any owner to improve it.
- Written for owners. Plain language, with settings chapters organized to follow the web interface's sidebar.
- Current. Covers firmware V2.x.
- Open. Corrections and additions are welcome from anyone who owns the hardware.
The manual is only as good as the corrections it gets. If something is wrong, out of date, or unclear on your unit, please say so — you do not need to be a developer to help.
Open an issue. Say which page you were reading, what it says, and what you see on your own unit. Screenshots help. That is a complete contribution — someone will make the edit.
This is the best route for anything you noticed while using your processor: a setting that has moved, a value that does not match, a step that no longer works, or an explanation that left you guessing.
Chapters are Markdown files in docs/user-guide/, images live in docs/user-guide/images/, and the
navigation is set in mkdocs.yml. For a small fix, use the pencil icon on any page of the
documentation site and open a pull request — no tools required.
To preview a larger change, you need Python 3.12 or newer:
git clone https://github.com/htp1-app/htp1-docs.git
cd htp1-docs
python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -r requirements.txt
mkdocs serve # preview at http://127.0.0.1:8000Run mkdocs build --strict before opening a pull request. It fails on broken links, missing images,
and pages left out of the navigation — the same check that runs on your pull request.
A few conventions keep the manual readable:
- Plain, direct language; short sentences; explain a term the first time it appears.
- One chapter per page of the interface, matching the name shown on the device.
- Say what the current firmware does. If you are unsure, say so in the pull request rather than guessing.
mkdocs build writes a plain static site to site/, which any static host will
serve if you want to keep a copy of your own.
Distributed under the Apache License 2.0. See LICENSE for details.
Project home: https://github.com/htp1-app
Questions and discussion: open an issue
- The HTP-1 core team, for the incredible ongoing work
- The HTP-1 owners' community, whose findings and testing inform much of this manual
- Best-README-Template