Skip to content

Installed effect scanner and selector tab#19

Open
ttshaw1 wants to merge 3 commits intothammer:mainfrom
ttshaw1:main
Open

Installed effect scanner and selector tab#19
ttshaw1 wants to merge 3 commits intothammer:mainfrom
ttshaw1:main

Conversation

@ttshaw1
Copy link
Copy Markdown

@ttshaw1 ttshaw1 commented Dec 4, 2025

Partial solution for #18 . A button to scan all the possible effects that could be loaded on your pedal and see what really is installed, useful for people who've edited their effects with Zoom Effect Manager, Zoom Firmware Editor, or something else. When the scan is done, a tab is added to the effect selector containing only the effects installed on your pedal.

image

"all possible effects" means that on a gen 1 (non-plus) MultiStomp, the code looks for effects from other gen 1 MultiStomps. On an MS+ or G2Four, it looks for effects from other MS+ and G2Four.

Lots of room for improvement:

  • The installed tab is ugly. Color and category names would be huge
  • Some pedal names are repeated, like Dist 1, because there's a guitar and a bass version. The name on the pedal is Bass Dist 1. Some of the pedal names in the Installed tab could use a Ba or Bass prefix
  • the progress counter on the Scan Installed button is wrong. Mine counted up to like 335/232 or something like that before finishing
  • save the results to a cookie or localStorage, so on a subsequent visit we can just load that up instead of needing another scan

And does this actually work on pedals besides a non-plus multistomp?

@ttshaw1
Copy link
Copy Markdown
Author

ttshaw1 commented Dec 5, 2025

Added colors and category names for gen 1 pedals, i.e. looks good on my pedal. Also added saving results to localstorage. If someone owns multiple pedals the localstorage will confuse them. If the pedals have serial numbers the program can interrogate that's probably the best way to resolve that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant