Repository navigation
ToneCommand 1.5.16
Unknown devices get named and learned, rigs are read the way players wire them, and the version is always on screen.
- An unknown device is named, and can be learned (#258, #261). Plugging in an instrument ToneCommand doesn't know used to produce no response at all.
- It now gets a card, e.g. "IK Multimedia ToneX One found".
- With your go-ahead, its button runs the first device-learning probe. The probe records what the device reports and sends it nothing.
- The result is a saved profile, so the device is recognised from then on. Nothing can be controlled from a profile yet.
- USB identity on Windows (#263): the same card on Windows, as on macOS and Linux.
- The version is always on screen (#264). A badge under the wordmark reads
v1.5.16; a branch or dev build adds its branch and commit. - A page with several rigs asks which one to build (#245), instead of silently taking the newest.
- The four-cable method is understood (#244). A multi-effects unit in front of the amp and in its loop is drawn as two positions with one signal chain.
- A delay or chorus wired that way lands in the loop; a drive lands before the amp.
- A rack unit whose effects aren't named is not built, and the card says so.
- Plugging and unplugging is seen however the app is started (#259). A server started a certain way used to keep its first view of the MIDI ports.
- A ToneX Pedal is recognised (#260).
Not yet proven on hardware: the ToneX Pedal card, and an instrument on Windows.
Details in CHANGELOG.md.