Search the Community

Hello, I am working on a MIDI controller with LED displays and I would like to use a backup file (format .hls) to retrieve the name and footswitch default status (i.e. what FS is on/off for each snapshot when I go to the preset or change snapshot etc). Since I don't change my setlist that frequently I am not trying to read directly from the unit but instead hard code the names and behaviors based on the .hls. I use a JSON parser to decode the .hls file and see there is a section called footswitch Here is an example (see full file in attachment) 'footswitch': {'dsp0': {'block0': {'@fs_enabled': True, '@fs_index': 5, '@fs_label': 'Volume ' 'Pedal', '@fs_ledcolor': 65408, '@fs_momentary': False, '@fs_primary': True}, 'block1': = etc.. Based on that, I originally assumed that each @fs_index would refer to a footswitch with @fs_enable for the status. However, that doesn't seem to be the case because I have a few setups with @fs_index > 5. To make things more confusing, I also see some presets without the 'footswitch' blocks though there are setup in the unit. Has anyone be able to understand how the hsl file work for the foot-switches assignment ? Any guidance on how to interpret the structure of this file ? Thank you. Pat. Test.txt

Hi, this is a little DIY project I built: It's a small Arduino based two button MIDI foot switch for the Helix HX Stomp. It is more flexible and more powerful than the "normal" foot switches connected via TRS cable and as a bonus you can still use an expression pedal hooked up to your HX Stomp. The MIDI Muppet HX can scroll through presets (normal mode) scroll through snapshots (snapshot mode) act as FS4/FS5 (fs mode) bring up the tuner (in any mode) To cycle through modes, press and hold the right (up) switch. To toggle the tuner, press and hold the left (dn) switch. If this is something you are interested in building please check out more information at https://github.com/mattzzw/midi_muppet_hx_2btn Other ideas are integrating tap tempo, looper control, ... Feedback and ideas are welcome! Cheers, /Matthias

This is a project I've been messing around with. It lets you really open up the possibilities of your FBV3 and /or FBV shortboard MkII. It allows for full color functionality of FBV3 as well. It requires some basic know-how with an Arduino at present, though with very little effort on Line 6's part, that may not be necessary in the future. Check it out: https://github.com/kquann/FBV_MIDI

I made a two-button footswitch for changing Helix patches up and down, using a generic (Elegoo) Arduino Nano board. It sends MIDI program change messages, and is endlessly customizable. Complete parts list: Hammond 1590a enclosure Elegoo nano (set of three for cheap https://www.amazon.com/Arduino-Elegoo-ATmega328P-without-compatible/dp/B0713XK923 ) two SPST momentary (normally open) switches LED and 220 ohm resistor (optional) panel-mount MIDI jack panel-mount 9v jack (optional, easy to power from 9v battery--Nano draws only 25mA, and only 37mA while LED is lit) hookup wire My code is pasted below. Entire project took less than two hours, and cost less than dinner. // midi.controller // Sends midi program change // Aaron Lyon April 2018 #include <MIDI.h> MIDI_CREATE_DEFAULT_INSTANCE(); byte patchNum = 0; #define BUTTON_PIN_1 2 #define BUTTON_PIN_2 3 #define LED_PIN 13 void setup() { pinMode(BUTTON_PIN_1, INPUT_PULLUP); pinMode(BUTTON_PIN_2, INPUT_PULLUP); pinMode(LED_PIN, OUTPUT); MIDI.begin(MIDI_CHANNEL_OMNI); } void loop() { if (digitalRead(BUTTON_PIN_1) == LOW && patchNum < 99) { // Next Program digitalWrite(LED_PIN, HIGH ); patchNum++; MIDI.sendProgramChange(patchNum, 1); delay(200); digitalWrite(LED_PIN, LOW ); } if (digitalRead(BUTTON_PIN_2) == LOW && patchNum >= 1) { // Next Program digitalWrite(LED_PIN, HIGH ); patchNum--; MIDI.sendProgramChange(patchNum, 1); delay(200); digitalWrite(LED_PIN, LOW ); } }