Skip to content

ToneCommand 1.6.2

Latest
Latest

Choose a tag to compare

View all tags
@monzta1 monzta1 released this 24 Oct 18:26
v1.6.2
148aa7a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

If ToneCommand ever fails to start in your browser, it now tells you so, and you can still send us a report.

  • A page that doesn't start says so (#282, from #281). A page whose buttons don't respond used to look perfectly normal. Now:
    • The version badge under the logo is filled in by ToneCommand itself, so it shows even on a broken page.
    • If the page doesn't finish starting, a red notice appears after a few seconds, naming the version and linking a problem report.
    • A new report page at http://127.0.0.1:8909/report works with no page script at all. It shows the same report as Report a problem: you add a note, read everything first, then open the GitHub issue yourself. It never contacts your device.
    • The terminal window prints the version and the report address when ToneCommand starts.
    • Settings has a REPORT A PROBLEM button, so you no longer need an error in the chat to send one.
  • Groundwork for sound editing on the Axe-Fx III (#280, #284). A developer-only component can change Amp 1's Gain or Mid on a Mark II, with every value read back. It is not reachable from the app: ToneCommand stays read-only on the Axe-Fx III for players. It gets a hardware check on a real Mark II before it is connected (#190).

Thanks to @Axelman8 for the Amp writer, and to kidney913 for the report that led to the new problem reporting. 🤘

Details in CHANGELOG.md.

Assets 2
Loading