PatchFerret
PatchFerret is a self-hostable utility that converts a mixing console show file into a patch list, specification sheet, and wiring topology diagram, exported…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
51/100 Fair
- Maintained
- 91last commit 17 days ago
- Popular
- 00 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 19 days ago
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2026-11-03
- License
- MIT
- Activity
- declining
Checked 6 days ago - source: GitHub (stoatworks-labs/patchferret)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Installing on Unraid Search for 'PatchFerret' in the Unraid Community Applications browser. The template is templates/patchferret.xml in the stoatworks-unraid repository, which the CA feed reads. source
- Rebuilding web/ is the committed browser build of the Rust crates, so there is no build stage; the image serves whatever is committed. Rebuilding it is the repo's own job - see the repository README. source
Fetched 45 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does the self-hosted image require a build stage?
No. The web/ directory is the committed browser build of the Rust crates, so the image serves whatever is committed and rebuilding is the repository's own job.
Does a show file leave the machine?
No. The browser build parses and renders entirely in WebAssembly, so there is no upload and no server.
Can the generated PDFs be loaded back into a console?
No. No output has ever been loaded back into a console, and no conversion between consoles exists yet.
How is the Behringer X32 adapter validated?
It is written against a real 2,104-line X32 scene file and asserted in CI. The X32 tests cover connector, slot, and channel composition, head-amp indexing across local and AES50 links, and output-source enumeration.
Answers sourced from github.com
Community
Collected 48 days ago - public community threads