Create a virtual USB device for testing and also to intercept and change details sent to Fender Tone to hopefully be able to grab the firmware file.

Images and icons for the GUI

• background images for the DSP units (themable)
• images for each effect/amp in the dropdowns
• icons for buttons
• possibly use some from Fender's icon library

Integrated preset library to store an unlimited number of presets in the computer

• stored in profile and loaded automatically
• import and export to files
• allow tagging and organizing of presets in a folder structure
• drag and drop to presets on the amp

Events file to sync with an mp3 (or just a time code) to trigger effect changes automatically within a song

• documentation
• validation

• display current preset settings using sliders, knobs, etc
• change settings on the amp via those controls

https://github.com/AvaloniaUI/Avalonia

• three pane
  • left pane is list of presets on the amp
  • middle pane is controls for the effect units
    • switch between json view, property grid, sliders, and knobs
  • right pane is collapsible, and holds the VU meter/preset library
• menu
  • File
    • Import
    • Export
    • Exit
  • Preset
    • Save
    • Save As
    • Rename
    • Clear
    • Move
  • View
    • Preset Library
    • Footswitch Setlist
    • VU Meter
  • Options
    • Amp Settings
    • Preferences
• Status Bar
  • Current Preset
  • Footswitch Settings
  • USB Gain
  • Connection Status

ltamp <command> [options]

Commands:

• preset get <#>
  • gets preset in bank #; 0 for current preset
• preset set <#> [--file <filename>]
  • sets the preset at # from filename, or stdin; 0 for current preset
• preset list [-a]
  • list presets on amp
  • -a also lists amp and each effect
• preset rename <#> <name>
  • renames the preset in bank # to name
• preset swap <a> <b>
  • swaps the presets in a and b
• preset shift <a> <b>
  • moves preset a to b, and shifts the rest.
• preset clear <#>
  • clears the preset in bank #
• qa get
  • gets footswitch presets
• qa set <a> <b>
  • sets the footswitch presets to presets A and B
• gain get
  • gets the USB gain value
• gain set <dBvalue>
  • sets the USB gain to dBvalue
• term
  • terminal mode; can be used to script series of actions or just monitor the amp, outputting all messages received
• midi
  • translates midi messages to amp commands
• config
  • generate default config in user's home directory

Library of presets specific to a DspUnit to save for use with other presets

• ListView for presets
• dspUnit views
  • JSON editor
  • Property Grid
  • sliders
  • knobs
• vertical slider
• knob
• Vu meter
• docks

• view options
• preset library
• theme
• footswitch setlists

Test for each message through mock device; for regression testing of the library

Check value received in the mock device, and the response sent from the mock device.

• processorUtilizationRequest
• memoryUsageRequest
• presetJSONMessage
• loadPreset
• setDspUnitParameter
• presetEditedStatus
• replaceNode
• shiftPreset
• swapPreset
• currentPresetSet
• clearPreset
• saveCurrentPreset
• saveCurrentPresetTo
• savePresetAs
• renamePresetAt
• auditionPreset
• exitAuditionPreset
• auditionStateRequest
• productIdentificationRequest
• firmwareVersionRequest
• currentPresetRequest
• retrievePreset
• usbGainRequest
• qASlotsRequest
• qASlotsStatus
• modalStatusMessage
• usbGainSet
• qASlotsSet
• heartbeat
• connectionStatusRequest

NAudio.Midi is not cross platform

Maybe https://github.com/atsushieno/managed-midi

Found these in the binary of the Fender Tone app; still need to test them:

AudioPage
FrontPanelPagw
TonePage
AboutPage
AuditionPage
ChoosePresetPage
EditPage
FootswitchPage
FootswitchLT4BankEditPage
MenuPage
RenamePage
ReplaceBrowsePage
ReplaceConfirmPage
RestorePage
SavePage
SaveSplashPage
SelectionPage
SettingsPage
TitlePage
TunerPage

Keyboard shortcuts to control effect parameters; specifically to be able to set up conplex changes via macros

• prev/next preset
• switch to preset #
• For each DSP unit:
  • toggle bypass
  • param value up/down (for each param)
  • switch to effect x
• toggle tuner
• increase/decrease tempo

Create a "setlist" of presets to rotate through with each push of the footswitch.

1. A list of presets is created to rotate through and the first two are stored in the amp, as A and B.
2. When the footswitch is pressed, and the amp switches to the other preset, the preset setting that was switched from is updated to the next preset in the list.

Preset list: a b c d e f g h i j

Process (upper case means active):

Ab -> (press) -> cB -> (press) -> Cd -> (press) -> eD -> (press) -> Ef -> (press) -> gF -> (press) -> Gh -> (press) -> iH -> (press) -> Ij -> (press) -> aJ -> (press) ->

Remove code dealing with amp state from the library; let the application deal with it while they also deal with UI.

Web interface for running on a computer (like a raspberry pi) and using another device to control it.

• mobile UI
• local midi control

VU meter to help match volume across presets.

I only have a Mustang LT25, and I suspect there are differences among the other amps in the series.

The other amps are:

• Mustang LT50
• Mustang LT40s
• Rumble LT

To ensure compatibility, all that would be needed is a Wireshark dump. To make sure it covers everything, I would want the dump to include:

• power on and connection
• pressing the footswitch
• setting footswitch parameters
• setting line out gain (if applicable)
• turning all the knobs and pressing each button
• enabling and disabling the tuner

From that, it would be trivial to double check the protocol messages for any differences that need to be accounted for in the code.

Maybe in .NET MAUI?

Arduino library to allow for controlling bypass settings, etc, from an external controller.