Feature Request & Feedback: Centralized Preset Management and LED State Sync

[enang84]

Hello Greg,
 
I am a huge fan of the incredible system you’ve built. Thank you so much for creating and sharing such a wonderful tool with the community.
 
Because your system is so excellent, the more I use it, the more I find myself thinking, "It would be even more perfect if it could do this." I have a few suggestions/requests I’d like to share. I would be grateful if you could consider including these in your future roadmap, or perhaps offer some advice if I were to attempt modifying the code myself.
 
My Current Setup:
Hardware: JC3248W535
Signal Chain: Tonex One and HX One
Controller: M-VAVE Chocolate Plus (connected to JC3248W535 via Bluetooth)
Routing: I control both pedals simultaneously by connecting the Chocolate Plus to the JC3248W535 and the HX One via USB MIDI.
 
1. Centralized Preset Management (OneController as the Hub)

As I use the Tonex One and HX One together, I find myself wanting more flexible control. It would be amazing if OneController itself had its own presets, where each preset defines which Tonex One and HX One patches are called.
 
For example, if we call OneController's presets "OP," Tonex One's "TP," and HX One's "HP":
OP1: TP1, HP1
OP2: TP1, HP3
OP3: TP4, HP1
OP4: TP3, HP2
 
In this way, OneController would act as the "brain" of the entire rig. I realize this would likely require implementing MIDI output functionality for the HX One (which I believe isn't supported yet), a fundamental restructuring of preset management, and UI additions. I understand this is a major undertaking, but it would open up so many possibilities.

 
2. Syncing External LEDs with Tonex One Colors
While the first point is the "ideal" scenario, I have a more immediate hardware project in mind to improve my current setup. I am planning to build a custom add-on for my Chocolate Plus with four LEDs placed near the footswitches. I want these LEDs to be controlled by TonexOneController.
 
My goal is to use RGB LEDs and have them match the current LED color of the Tonex One. Is it possible for the TonexOneController to retrieve the current LED color state from the Tonex One unit?
 
Thank you for your time and for all your hard work on this project. I look forward to hearing your thoughts.
 
Best regards.

[Builty]

Hi, Thanks for the kind words.

1. The controller actualy has support for Midi output right now, but its set to pass-through whatever arrives on the input to the output.
   There have been a few requests for general Midi control, but its a bit of a tough one. Everybody needs different things, and making the system flexible makes it also a lot of work.
   There are a lot of existing Midi controllers around and I'm not really planning to try to complete with them, but I understand the appeal of having one thing to it all.
   Can you suggest some kind of configuration system? E.g. I guess it would need selection of Midi PC or CC and the values to send, plus some kind of linking of Tonex preset with the Midi send.

2. Yes the controller code is already reading the Tonex led colors. I've been working on some led support recently, working with Polar Midi guys on a model with leds above footswitches, controlled by the common WS2812-style of RGB led control.
   The Waveshare 4.3B wouldn't have enough IO pins spare for this but the JC3248 should have.

The current led code may well be OK as it is. If the footswitches are used for FX switching, the leds show as off/on, but when used for preset switching the Tonex One colors are used (and green for big Tonex/GP5.)
Check the config build items CONFIG_TONEX_CONTROLLER_LED_CONTROL_DISABLED and CONFIG_TONEX_CONTROLLER_LED_NUMBER.

[enang84]

Hello Greg,
 
Thank you for the detailed explanation. It is very helpful.
 

1. MIDI Requirements and Preset Management
   I completely agree that user needs are diverse and that building a flexible system is a major challenge. My image is more like creating a wrapper layer above the current preset management.
    
   In this idea, each "Controller Preset" (let's call it OP) would hold its own mapping for a Tonex One preset number and a MIDI PC number. These mappings could be configured—perhaps in a settings screen—for each OP. Then, the footswitches would be assigned to call a specific Controller Preset (OP) rather than directly triggering a Tonex One preset.
    
   Regarding MIDI output, while I might eventually want CC support for deeper effect control, being able to output PC numbers first would be a huge step and sufficient for my current needs. I’ll keep thinking about how this could be implemented simply as well.
    
2. LED Support
   Thank you for the specifics on this too! It’s great to know that the features are already built-in. I will experiment with the config build items you mentioned and see how it works.
    
   Thank you again for all your help. As a token of my appreciation, I’ve attached a photo of the pedalboard I’m currently building.

[Builty]

Pedal board looks great.
I'm still thinking about Midi support.