Apply a mastering pass to an already generated track, adjusting perceived loudness and limiting audio peaks. See before-and-after loudness measurements, then access the mastered audio through the dashboard.
Run a mastering pass (LUFS loudness normalization + peak limiting) on an existing production
Review the instructions the agent will receive before you install.
Applies loudness normalization (default target -14 LUFS, common streaming-platform standard) plus a peak limiter to an already-generated production.
The user wants a "radio-ready" or streaming-normalized version of a track they've already generated.
mcp__cogmusic__master({ id: "<production-id>" }).lufs_before and lufs_after — report both so the user can see the actual loudness change, not just "done."music-productions (if one exists) with the new lufs_before/lufs_after/has_mastered: true fields so later lookups don't need a round-trip.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.