Patch panels: how the page shows a cord (2600, MS-20) #58

Open
opened 2026-10-13 02:11:00 +00:00 by bcox · 0 comments
Owner

Ben confirmed on 2026-10-12 that the patch cords of the 2600 and the MS-20 are .jack parameters (engine/patch_panel.h): 0 no cable, 1 a dummy plug, 2 and up a cord from an output jack. What was left open with that, and is this issue: how the page shows them.

Today web/page/app.js shows an input jack as a stepped control that reads "No cable:" and the name of the wire behind it, or the name of the output plugged in. Each instrument's page.js lists its outputs as kOutputs.

To decide:

  • Whether the page should draw the cords, on a picture of the panel or between two lists, and let one be dragged from an output to an input.
  • Short of that, whether a jack should be a menu of output names and not a slider that steps through them.
  • How a cord from an output that feeds several inputs is shown, and how a dummy plug is.

The protocol need not change for any of it: a cord is a set. It goes with #7, and with #24's patch panel when the PS family is built.

Ben confirmed on 2026-10-12 that the patch cords of the 2600 and the MS-20 are `.jack` parameters (`engine/patch_panel.h`): 0 no cable, 1 a dummy plug, 2 and up a cord from an output jack. What was left open with that, and is this issue: **how the page shows them.** Today `web/page/app.js` shows an input jack as a stepped control that reads "No cable:" and the name of the wire behind it, or the name of the output plugged in. Each instrument's `page.js` lists its outputs as `kOutputs`. To decide: - Whether the page should **draw the cords**, on a picture of the panel or between two lists, and let one be dragged from an output to an input. - Short of that, whether a jack should be a **menu of output names** and not a slider that steps through them. - How a cord from an output that feeds several inputs is shown, and how a dummy plug is. The protocol need not change for any of it: a cord is a `set`. It goes with #7, and with #24's patch panel when the PS family is built.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
bcox/mini-800#58
No description provided.