| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| test_audition_loop.py | ||
| test_autotune.py | ||
| test_correlate.py | ||
| test_engine.py | ||
| test_grade.py | ||
| test_loops.py | ||
| test_naming.py | ||
| test_stempack.py | ||
| test_vox.py |
66318b6e's comment and test docstring both claimed PLN heard the polled-loop stutter. He did not. The Foundry server was not running: port 8765 was another project's http.server, established two steps after the fix landed. The bug is real and of exactly the reported shape, and it stays fixed - but attributing a fix to a symptom it did not cause is how a wrong diagnosis becomes documentation, which is this morning's -inf-faders mistake again. Both places now say where it came from. The commit message is history and is left alone. And check-mix's --arm table called an unarmed `Mix` route "not recorded, by choice" while --mix blocks on precisely that. Two modes of one tool must not disagree about the same route.
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| test_audition_loop.py | Loading commit data... | |
| test_autotune.py | Loading commit data... | |
| test_correlate.py | Loading commit data... | |
| test_engine.py | Loading commit data... | |
| test_grade.py | Loading commit data... | |
| test_loops.py | Loading commit data... | |
| test_naming.py | Loading commit data... | |
| test_stempack.py | Loading commit data... | |
| test_vox.py | Loading commit data... |