Skip to content

ToneCommand 1.6.3

Latest
Latest

Choose a tag to compare

View all tags
@monzta1 monzta1 released this 05 Nov 03:34
v1.6.3
88173f4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

ToneCommand now only answers to your own computer, and Gig Lock no longer cuts off a change that is already being sent.

  • Only this computer can reach ToneCommand (#291). The local server now answers only to 127.0.0.1, localhost and ::1, and refuses a change sent from another website's page. A web page can no longer reach it through a name that points at your machine.
  • Gig Lock waits for a change that is already being sent (#291). Turning Gig Lock on waits up to a minute for that change to finish, and tells you if it is still going. Anything queued behind it is refused with nothing sent. A cab audition, a routing recovery or a debug poke waits until Gig Lock is off.
  • Fewer false firmware warnings on the Axe-Fx III (#305). A recipe tested on 33.01 no longer warns when your unit reports the full 33.01 build label. Different builds and betas still warn.
  • More groundwork for sound editing on the Axe-Fx III (#294, #296, #297, #298). ToneCommand now names the exact firmware build it sees (33.00 beta 5, 33.00, 33.01). A single Gain/Mid edit for one exact Mark II beta 5 setup can be switched on by testers. The rest are read-only building blocks. For players, ToneCommand stays read-only on the Axe-Fx III (#190).

Thanks to @Axelman8 for the Axe-Fx III work. 🤘

Details in CHANGELOG.md.

Assets 2
Loading