F34.us
Menu
ACTIVEPROJECT 05

SYSTEMS ENGINEERING RECORD

MixMan Server

Turns a music collection into a library you can understand and explore. Analyze tracks, review suggestions, and plan what to play next.

RoleCreator · music systems architecture, media ingestion, and recommendation design

ImpactBuilt a review-first music library that combines layered audio analysis, curation, playback, and inspectable recommendation policies into one lifecycle.

  • Python
  • FastAPI
  • MariaDB
  • Audio Analysis
  • Recommendation Systems
  • Music

andrew Project record ·

MixMan: Navigating a Musical Space IMAGEMixMan: Navigating a Musical Space

PROJECT README

README

MixMan turns a personal music library into an explainable, reviewable system rather than a folder of opaque files.

It ingests uploads and external sources, preserves acquisition and metadata provenance, runs deterministic Queen Mary audio analysis, and supports search, recommendations, maintenance, and session planning. Human review remains part of the loop so automated enrichment can improve the catalog without silently overwriting trusted decisions.

SYSTEM DOSSIER

Project signals

7 ITEMS · 2 CONNECTIONS

ARTICLE

A Music Library That Learns How Tracks Belong Together

An overview of the review-first library, layered analysis, player experiences, and multiple discovery strategies.

FORGEJO / 26 WEEK ACTIVITY

MixMan Server repository

713 commits across 82 active days, 2026-05-11 through 2026-11-08 UTC.

Project pulse

Latest activity

  1. F34 How We Want MixMan Sessions to Develop
  2. WAKE Preserved the MixMan session-behavior design discussion as a reviewed, versioned reference.
  3. WAKE Prepared the MixMan epic feature workflow; child integration awaits hosted admission support.
  4. WAKE Completed the first code-based assessment of MixMan recommendation and session-policy learning.
  5. WAKE Established the MixMan recommendation and session-policy research epic and isolated dev-based workspace.
  6. WAKE Merged independently reviewed session discovery across five repositories and closed all five implementation issues under user-authorized acceptance.

FORGEJO / REPOSITORY PULSE

MixMan Server repository

Commits
890
Files
611
Code bytes
5,834,862
Branches
92
Issues
50 open / 93 closed
Python
72.5%
JavaScript
20.2%
HTML
6.7%
CSS
0.3%
Shell
0.1%

ARTICLE

How MixMan writes tags and preserves curation

Follow metadata from ingestion through analysis, shared tags, personal preferences, and review.

PROJECT TIMELINE

Activity

View all 14

WAKE ·

Session discovery implemented and independently reviewed across five repositories; delivery awaits required CI and Unity validation.

Impact: No PR has been merged or deployed. C++ compilation, Unity tests and the server MariaDB discovery contract remain unverified. Existing issues retain acceptance and next actions.

WAKE ·

MixMan Pi candidate promotion has no compliant ARM64 release path.

Impact: The Pi cannot automatically build or deploy the requested current candidate because the automation-owned branch cannot be advanced safely.

WAKE ·

Removed the deprecated Mixripper integration and deployed the current MixMan dev head.

Impact: SoundCloud acquisition now uses the supported yt-dlp path only, obsolete Mixripper artifacts and configuration are gone, and repository-integrity checks protect future submodule inputs.

WAKE ·

Researched MixMan issue 87 Authlib OIDC cutover and posted durable findings to Forgejo.

Impact: Defined a no-schema-change migration boundary that preserves DB-backed OIDC state, browser-session refresh fencing, MixMan roles, and Mesh ownership/mTLS policy; identified privacy-safe diagnostics and staged rollback gates.

WAKE ·

MixMan Mesh QA gates passed after HTTPX2 2.12.0 remediation; live rollout held before mutation

Impact: Firestorm node A and VPS node B remain unstarted and no transfer occurred

WAKE ·

Repaired Mixman v3 session steering without introducing a new engine or contract version.

Impact: Controller-scoped complete steering snapshots, deterministic policy ranking, typed steering propagation, lenses, participant pressure composition, BPM and progressive guardrails are now on dev at ba9c076ea9f642fd52a85a76cb6e2507ba290228; 739 tests passed and 10 skipped.

TECHNICAL RECORD

Documentation

View all 3

Article · Friday 28th of August, year 2026

What the Analyzer Knows—and How MixMan Knows It

Analysis architecture

Explainable music intelligence stays useful by preserving provenance, confidence, and human authority.

Open record

VISUAL AND AUDIO RECORD

Media

View all 1

The current overview mosaic features this collection’s latest evidence.

COMPLETE PROJECT INDEX

All material

View all 7

Article · Friday 28th of August, year 2026

What the Analyzer Knows—and How MixMan Knows It

Analysis architecture

Explainable music intelligence stays useful by preserving provenance, confidence, and human authority.

Open record

Article · Friday 28th of August, year 2026

The Inbox Before the Library

System design and implementation

Review-first ingestion turns uncertain media into a trusted, traceable catalog.

Open record

Article · Thursday 27th of August, year 2026

Beyond Similarity: Teaching a Jukebox to Choose Its Next Move

Technical explainer

A musical policy engine chooses the kind of transition before it chooses the track.

A technical look at pressures, move types, candidate evidence, path planning, and inspectable decisions.

Open record

CONNECTED PROJECT SYSTEMS

Connected systems

WAKE · CACHED NOV 2, 2026

MixMan Server work log

Event Count: 11

Open wake
F34.us Background Image