Stereo dual-amp builds: DSP-budget-aware placement and parallel-path topology
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Start by locating add_block and reading how it handles block insertion, routing, and read-back on the FM9. The issue identifies DSP-budget refusal, replacement-based swaps, cable inheritance/redraw, and amp panning as parts of the work; verify each against the reported loaded and light preset behavior. Done means a stereo dual-amp path can be planned and placed on a loaded preset, with likely DSP-budget failures reported.
Written by the indexing model from the issue text.
Description
Attempted the WT creator's stereo Matchless pair (DC-30 left / Chieftain right) on a loaded preset (152). Findings, all hardware-verified 2026-08-21:
- Shunt insert via sub 0x32 does not exist (eid 2 lands nothing); a unity VOLUME block works as a pass-through hop for multi-hop diagonal routing (1-row diagonals are the only verified cable geometry for new draws).
- Amp2 (eid 59) insert is SILENTLY refused on a DSP-heavy preset but places fine on a light one: the FM9 refuses over-budget inserts with no error. add_block should detect this (insert, read back, report 'likely DSP budget' when nothing lands on a verified-free cell).
- A real stereo pair on a loaded preset therefore needs a plan: budget check, sacrificial block choice (surfaced to the owner), replacement-based mid-chain swaps (IN-cable inheritance + the new outgoing-cable redraw), and amp panning params.
Parked as a fresh-session task; 152 gigs without it.
- Dominant language
- Python
- Stars
- 7
- Forks
- 3
- Avg merge
- 2h 28m
- Merged PRs (30d)
- 51
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from monzta1/ToneCommand
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
monzta1/ToneCommand#268 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
monzta1/ToneCommand#269 ·
Maintainers usually reply within 1 day
-
bug device
Difficulty 4/5 3-5 days Newbie friendliness 12/100
monzta1/ToneCommand#250 · 1 comment ·
Maintainers usually reply within 1 day
-
bug device
Difficulty 4/5 3-5 days Newbie friendliness 18/100
monzta1/ToneCommand#241 · 2 comments ·
Maintainers usually reply within 1 day
-
device enhancement epic
Difficulty 5/5 Over a week Newbie friendliness 12/100
monzta1/ToneCommand#239 ·
Maintainers usually reply within 1 day
All issues in monzta1/ToneCommand
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 65/100
EclipseFdn/open-vsx.org#15057 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
FinanceFlash/unvibecode#349 ·
-
Mission statement: why this is free, in the README, Why This Exists and the wiki HomePossibly taken @ChiefGyk3D claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ChiefGyk3D/Clouds-Against-Humanity#348 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
vllm-project/vime#508 ·
Maintainers usually reply within 4 days