stoo

31 minutes ago, guillaumegart said:

Hello Stoo, I downloaded your file for the touch footswitch. I have an arduino mega2560, the Nextion screen, and buttons on my feet. I uploaded the INO files to the arduino (upload OK). I prepared the screen with the HMI file (with Nextion setup OK) and followed the connections of your diagram (without the expression pedals because no need ...) But I have a problem because nothing happens .... The footswichs do not transmit signals, the screen remains on Booting ... I do not know Arduino programming but I managed to make your first footswich (but without the screen ...) Are there other maneuvers to do? Could you say more about the procedures to follow? because here I am pulling my hair .... thank you so much Guillaume

Okay - so you have power to the Arduino and Nextion screen working OK if you see the Booting message.

If the code compiled and uploaded to the Arduino OK, then I would first concentrate on the serial connection pins between Arduino and the Nextion - TX2(16) and RX2(17). A common mistake is to connect the Nextion TX wire to the Arduino TX2 pin, and the Nextion RX wire to the Arduino RX2 pin..... but Nextion TX goes to Arduino RX2 and Nextion RX goes to Arduino TX2.

Hope this helps!

On 21/03/2021 at 17:54, Oliver70 said:

Hey there, i rebuild the switch, very cool, i make a mini-version. Can you give me a tip, how i can change the code to get 8 Programm Changes? Like Bank 1, Sound 4, in this way...

And i try to push two buttons, but the display and funktion dont change, if you hav a tip...

Thank you- best regards oliver

My Version: https://www.dropbox.com/s/8owr6oqfxwk46bj/Midi8.JPG?dl=0

Sorry - I've only just seen this - I'm guessing as your post is over 3 weeks old you've probably sorted it by now....... If not, give us a shout and see if I can help

Yep. - start as simple as you can, get something working and gradually add to it. 

And make regular backups so you can easily revert back to when it last worked!

If you do get stuck though, by all means give us a shout on here.... I'm no expert, but happy to try and help where I can

11 hours ago, bastoe said:

This is a great project Stoo, thanks for sharing it all. I'm building something similar, but with one dedicated page up switch, and 4 command switches. 

For keeping tabs on which Page I'm on, I have a simple 7 segment single number display LED, and the other switches have their own green 5mm LED. 

Would editing your code allow something like this, or am I looking at a from scratch build?

My controller will look like this one: https://www.youtube.com/watch?v=z4jOhp0Z0G4 

The way he has it set is just for presets, so i was banging my head against the wall trying to figure how to get the other pages to do other commands as he has it all defined just to do the presets.

Thanks!

 

There's no reason why you couldn't replace the OLED code in mine with some other code to run a 7 segment LED instead.

I'm not sure what you're expecting from the LEDs for each switch though.... If you're just changing presets then you can just have the MIDI controller light the LED for whichever footswitch you last pressed, and then as long as you don't adjust the preset on the Stomp (or whichever device you're controlling) then it should all match up. 

If you're planning on controlling block bypass / toggling effect parameters or anything else, then there's no way to get the current state back from the Stomp to the MIDI controller. Even if you added a MIDI IN port, the Stomp just doesn't relay that information out.

If the Stomp had different MIDI commands for turning FSx on and off then maybe you could come up with a workaround, but all its MIDI commands for FSx are just toggles. Maybe you could do something like that in Command Center, but it'd be a lot of work to set up, and you'd have to do it separately for each and every preset....

Not 100% sure without trying it, but I think the code should work fine as is without the screen being present.

If not, it'd be a really quick job to remove all the screen related bits.

The other thing to consider is that at the moment, the code has multiple pages of button configurations setup..... Without the screen you'd have no visual cue to let you know which page is currently selected. Easy enough to reconfigure it to lock it to a single page setup, which would probably make sense.

Going to less than 8 buttons will work fine with no code changes.... it will treat missing buttons exactly the same as buttons which are connected but not pressed...

1 hour ago, JIMHU26 said:

Hola Stoo, por favor podrías compartir nuevamente el código de Arduino que usaste para el controlador midi del Hx Stomp, ya que no aparece en el enlace que dejaste. gracias

Hiya - the best place to get my code for the first version (Arduino nano + oled screen) is on github - https://github.com/stoonoon/hxsMidiSwitcher/blob/master/hxsMidiSwitcher.ino

If you're after the other version (Arduino Mega + Nextion touchscreen) then start here - https://github.com/stoonoon/hxsMidiSwitchTouch - the code is split into several files but I think everything you should need is in there.

Cheers,

6 minutes ago, Bklyn3 said:

Hello all, 

 

Does anyone know if there is a MIDI CC code to mimic pushing the  view button ?

 

 

 

 

I don't think so.... All the CC codes are documented in the back of the owner's manual - https://line6.com/data/6/0a020a4112bbf5fb6a519e8b18/application/pdf/HX Stomp 3.0 Owner's Manual - Rev C - English .pdf 

I suppose it's possible there might be some undocumented extras, but I've not seen any mention of any so far....

10 hours ago, Bklyn3 said:

Hi Stoo,

After struggling for a few days I finally found some issue with the grounding. All works well.

Thanks so much for your original post.  

 

P. 

Nice one! 

If you want to check out what the effects are like, you can always get a free trial of helix native from the line 6 website. Won't give you much insight into which hardware version to get, but should at least give you a bit of a headstart as to what it can do before committing to an order...

6 minutes ago, la bam said:

Hi all, does the updated stomp now have input meters, and / or output meters?

I'm thinking of adding one after my preamp pedal so I can monitor levels easily - so it would go:

Bass - pedal - stomp - amp - cab.

Thanks.

Not exactly - there's a small coloured blob that acts as a signal present or clip indicator for both input and output, but no detailed level indication.

See page 23 in the manual for more info - https://line6.com/data/6/0a020a4112bbf5fb6a519e8b18/application/pdf/HX Stomp 3.0 Owner's Manual - Rev C - English .pdf

Well that's proper weird, eh?

Does it behave the same if the Arduino is disconnected from the computer and powered separately? I never had any issues with mine, but with the Nano, it uses the same Serial pins for the MIDI communications as well as uploading sketches... could be some sort of conflict there maybe causing weirdness?

Other than that - obviously do a search for 8 in your code and double check there's not any weird typos in there which could cause it to be sending anything in channel 8.

The Mega I used was one of these - https://smile.amazon.co.uk/gp/product/B06XKMZ3T9/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 - I've had a couple of them and both work fine. Not sure whether a sample size of 2 is really enough to justify much of a recommendation, but they've done me OK so far!

Hey - glad to hear you're at least making some progress!

I'm intrigued as to what might be happening to cause one button to flip back and forth between two presets like that though....

If the currentPage isn't changed, then each switch *should* send the same MIDI command each time (or whatever you've specified in the relevant case block in midiSend, in case you've changed things around at all in there)

If the Stomp is receiving the exact same MIDI message each time, then I would expect it to keep cycling through presets in the same direction each time instead of toggling between 2? Unless you've set up something specific in Command Center to do just that.... 

One thing that might be useful to try is to install a MIDI monitor on your computer.... if your Stomp is connected to the computer via USB, the computer should also be able to see all the MIDI messages sent to/from the Stomp's MIDI interface. I'm not too familiar with Macs, but I'd bet there's a free app you can get for it to inspect MIDI traffic. Might give you some extra clues as to what's going on

1 hour ago, Bklyn3 said:

Hi There ,

started the project this afternoon but somehow the hx doesn’t respond. The code goes to the right MIDI send statement  but nothing is changing. Is there something to set on the HX stomp side ? The voltage I got is not 5 v on the MIDI plug but 4.7v. Could that be an issue? 
 

thanks. 
 

pat. 

Shouldn't need to configure anything on the Stomp side. The +5V line won't need to be precisely 5V. I'm not sure what the tolerance is, but 4.7V is very unlikely to be a problem.

Okay - Let's start with the basics....

Which version are you building? The Nano/OLED one or the Mega/Nextion one?

What's your hardware setup so far? Are you building it up on a breadboard? Do you have a photo that you can post?

If you're using the Nano/OLED project then we can try some simplified code which ignores all the switches and screen stuff and should just test the MIDI output on its own

something like ..

#include <MIDI.h>
const int midiSendChannel = 1; // MIDI channel for outbound messages

// Creates and binds the MIDI interface to the default hardware Serial port 
MIDI_CREATE_DEFAULT_INSTANCE(); 
void setup() { 
  MIDI.begin(MIDI_CHANNEL_OMNI); // Listen to all incoming messages
} // end of setup 

void loop() {
  MIDI.sendControlChange(71,1,midiSendChannel); //Scroll Mode 
  delay(500);
  MIDI.sendControlChange(49,0,midiSendChannel); //FS1 
  delay(500);
} // end of loop

If you're using the Arduino Mega then you'd need to specify which of the Serial ports you're using - so on mine for example, I'd need to replace the

MIDI_CREATE_DEFAULT_INSTANCE();

line with 

MIDI_CREATE_INSTANCE(HardwareSerial, Serial2, MIDI);

If you get that code running on your Arduino and have the MIDI port wired up correctly, it should just automatically scroll down through your Preset list on the Stomp, once per second.

If it doesn't work, I'd be looking extra hard at the connections between the Arduino and the MIDI port.

Hope that helps - let us know how ya get on.... Good luck!

11 minutes ago, Bklyn3 said:

Hello Stoo,

I recently purchased a HX Stomp and I plan on building your MIDI controller. Thanks so much for sharing your design with the world. 

This will be my first Adruino project, so hopefully the learning curve won't be too steep.

A quick question, could you please send the reference of the bigger screen. Will the Adruino Nano (posted 2 years ago with the list of items) work with the bigger screen or do I need something else? 

Thank you

Hiya

The bigger screen I used for the 2nd version was a Nextion 3.2" Enhanced NX4024K032 - https://smile.amazon.co.uk/gp/product/B072FN3SFH/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 

It might be possible to use that screen with a Nano - I can't say for sure because I never tried it. Off the top of my head I would expect the main complications to be:

Power - I specifically chose that Nextion screen because I saw someone else had been using one powered directly from an Arduino Mega with no issues. It might power from a Nano just as well, but there is also a chance you may need to add an extra 5V supply for the screen if not.

Serial ports - The Nextion touchscreen uses a serial connection to the Arduino microcontroller..... and so does the MIDI communication. The Arduino Mega makes this easy as it has 3 serial ports built in. Unfortunately the Nano only has 1. It should be possible to workaround this by creating a SoftwareSerial connection using some other free pins on the Nano - but that's not something I've tried, so can't really advise you.

Coding - The OLED and Touchscreen versions of my footswitches share almost no code between the two projects. I don't know if you've got any programming experience, but if not, then please don't expect it to be a simple cut and paste job to move the touchscreen code into the Nano-based project. The Nano is very limited on memory space, and it took me a fair amount of work to get the first version to fit in it. All the touchscreen version code was written with the Mega in mind, and would likely be a nightmare to try and squeeze into the Nano.

If this is your first Arduino project, then I'd suggest - unless you're reasonably confident on the programming side of things - that you stick to either using an SSD1306 OLED with a Nano, or bump up & use a Mega if you want the Nextion screen. You can easily leave out the expression pedal input part if that's of no interest to you, and the price difference between Nano and Mega is only about £10 for the Chinese clones if you're on a really tight budget....

Hope that's of some help....

Sure - although it looks like it's all still available at https://github.com/stoonoon/hxsMidiSwitcher .... Is that link not working for you?

Are you sure you lost your old presets? The update process prompts you to take a backup before it proceeds with the update... If you just clicked through the menus without reading them, you might find you've got a backup ready to reimport all or part of....

2 minutes ago, dave_bass5 said:

What updates did the HFX get? Seems like the Stomp got quite a few new features (not bass specific). 

16 (I think) new effects, and Favorites/User Model Defaults. Looks like that might be it for HXFX this time....

https://line6.com/support/page/kb/effects-controllers/helix/helix-30-release-notes-r934/

58 minutes ago, PatrickJ said:

I used the same update approach and completely missed that although the HX FX unit was updated to 3 HX Edit remained on 2.92.  Thanks for posting this I'm now downloading HX Edit 3.00

One other issue I had - not sure if it's a side effect of the order I installed things in or whether I was just lucky - was that restoring Favorites didn't work for me... I could save a block's settings into the favorites list, but whenever I tried to create a new block using those favorites settings, it would fail with an error - "Failed to load favorite - Operation failed due to DSP overload. Code -8611" I'm pretty sure it wasn't a genuine DSP overload issue as it was happening even with an empty preset. I ended up doing a factory reset and restoring my presets/IRs/config backup from before the 3.00 update and it all works fine now.

Might be worth a test on yours just in case it's a problem caused by updating the hardware to 3.00 from an older version of HX Edit ...

1 hour ago, krispn said:

Hi Stoo

yeah the updating can be a tad unintuitive with the line 6 stuff as it would be better if every updated together but we struggle on. 
I have downloaded what L6 tells me is hx edit 3.0 but upon opening the file it’s 2.92. I have successfully updated the firmware and the hx edit is looking a tad lacking. None of the new features have appeared yet. I’m in no rush and can load my back up of 2.92 so no drama but still. As I mumble on guitar too it’s be nice to try the new Princeton as it is a fav amp (my old country band the guitarist used one- lovely amp)!

I don't have a Mac to test them on, but I've just downloaded the 2.92 and 3.00 versions of HX Edit for Mac to see if they'd unwittingly uploaded the same file twice.... HX Edit 2.92.dmg is showing up as 35,011KB on my PC and HXEdit3.00.dmg is showing as 26,651KB... so there goes that theory.

Is it possible that you've got both versions installed at once, and whatever shortcut you're launching HX Edit from is still pointing to the old one? Did you manually remove HX Edit 2.92 before installing 3.00? Might be worth a try?

2 hours ago, krispn said:

I’ve not been able to usage HX Edit from 2.92 -3.00.0 so can’t access the new stuff. Still working on it 🙄 each time I download the 3.00.0 version when I open the package it’s 2.92. I’ve raised it with Line 6. Im running Mac OS but haven’t updated to Big Sur as I have other stuff which won’t run until update patches are released. If anyone has HX Edit 3.0 for Mac and has successfully opened it feel Free to dm me and send me the package and I’ll try it!

Have you managed to get your Stomp updated? On the PC version, I was able to update my Stomp from 2.92 to 3.00 using the "Check for updates" button at the bottom of the HX Edit window.... which confused the carp out of me for a while as I had (wrongly!) assumed it would also update HX Edit at the same time. 

Obviously you'd need to get HX Edit updated to 3.00 as well for it to be able to control the new features and effects, but at least you'd be able to test them out directly on the Stomp while you're waiting for L6 support to resolve your issue with the HX Edit upgrade....

9 minutes ago, Al Krow said:

Interesting question - not one I've given any thought to as it's already got 8 stomp switches. Ok not all of these are for scrolling but you can still very quickly scroll through  banks of 4 patches, each of which can be a virtual pedal board of 6 pedals as we were discussing a page or so back. This would seem for most of us to eliminate the need to use an additional footswitch on the HX FX. Having a couple of extra foot-switches on the Stomp obviously has a bigger payback.

But HX Effects is midi enabled, which might give an option...I'm guessing if any of the HX FX users knows the answer to this, it might be @Woodinblack

Preset up/down might be a tricky one as the MIDI implementation only has preset recall by explicit preset number. 

On the Stomp there's 2 ways around it (1: dedicating FS4 + FS5 to preset down/up, and then using the MIDI commands for those, or 2: send a sequence of MIDI commands to change the stomp screen to the preset list, then send FS1 or FS2 to change preset, then another command to change back to the normal stompbox view) but I don't think either of those would work on the HXFX.

You could do it via MIDI if you have a MIDI controller that can keep track of the currently selected preset and adjusts which messages it sends accordingly, but I would think you'd probably need to build your own controller to achieve that (not as hard as it sounds as long as you're OK with a bit of soldering)

Maybe there's some scope for doing something via Command Center with a regular footswitch connected to the expression pedal inputs on the HXFX..... if you can send a PC message whenever the expression pedal value goes over any non-zero value, it should detect a footswitch press. Probably a bit of a long shot, mind.... and unfortunately I've not got an HXFX to test with.

59 minutes ago, Osiris said:

Inspired by @dave_bass5 I'm starting to think of doing something similar, i.e. using a midi controller with my Stomp which would then live on top of the amp out of the way. Now, I know absolutely nothing about midi, but like Dave I like the look of the Tech 21 midi mongoose, but from what you're saying you don't think it would work as a block on/off switcher? It'd be a shame if it doesn't as that's all I'd want it to do, just 2 or 3 footswitches to kick things on and off. 

From the Stomp manual it says on page 48; 

Block Bypass via MIDI

1. Press  PAGE and PAGE  together to open the Menu.

2. Press Knob 1 (Bypass Assign).

3. Turn the Upper Knob to select the block whose bypass you want to assign to incoming MIDI.

4. Press PAGE  and then Knob 3 (Learn). Send a MIDI CC message from your foot controller, keyboard, etc. The CC number appears above Knob 1 (MIDI In).

Incoming CC values 0-63 turn the block off; values 64-127 turn the block on. Note that some MIDI CCs are reserved for global functions and cannot be selected (see "MIDI CC"). NOTE: To manually select a MIDI CC, instead of step 4 above, press PAGE  and turn Knob 1 (MIDI In) to select the desired MIDI CC number.
 

Am I right in thinking that you could use something like the midi mongoose to switch blocks on and off? As I understnd the blurb from the manual it looks like it should be possible (unless I've misunderstood it, as I said I know nothing about midi!) Ideally I'd also want the LED to indicate on and off but from what you're saying it wouldn't work like that. 

Any thoughts?

In case you missed my previous reply to Dave:

On 01/06/2020 at 17:56, stoo said:

I think you may have misunderstood the Mongoose's capabilities.... It basically ONLY* does preset changes (ie MIDI PC messages), and the LED and LCD on it are only there to remind you which preset you selected last. 

To switch individual effects on the Stomp, or change snapshots, or.... well, anything that's not a preset change - you need to be able to send MIDI Control Change messages, and that's not what the Mongoose is designed to do.

 

* apart from the expression pedal input part, but that's not really relevant to what you're asking about.

MIDI PC and MIDI CC are not the same thing.

Even if you have a MIDI controller which can send MIDI CC, then status indication on the controller is not really viable because there's no way for the Stomp to feedback the current state of the FS toggles to the MIDI controller. 

If :
- you're willing to build and program your own MIDI controller from scratch
- you're prepared to assume that every Stomp preset is saved with all the of the FS in an "off" state (or program the intial FS states for every Stomp preset into your custom MIDI controller)
- you're willing to accept that if you press the FS on the Stomp itself then the status light on the MIDI controller will be incorrect until you next change presets
then you could potentially make it work......  but realistically.... it's a no.

13 minutes ago, dave_bass5 said:

Well in a way this is why im asking. I’m not yet up to speed with what can and cant be done. I assumed you could change snapshots, but i guess you cant. WIth the LED”s i was just hoping for villa feedback that ive hit it. Quite other i might hit two stitches by mistake, or not tun it off. Be nice jus tot see the status light change. 

As far as Midi Control changes etc, I’m hoping the upcoming FW 3.0 with Control centre update will take care of this at the Stomp end, but appreciate the Mongoose still wont use these commands. 

Command Center seems to be more about controlling other devices from switches/pedals on a Helix device than the other way around - maybe they'll add more to it by the time it hits Stomp, but I wouldn't pin your hopes on that too hard.

1 hour ago, dave_bass5 said:

Any thoughts on this? USB rather than midi. Must admit ive not looked in to any of this side of the Stomp so maybe this just wont work anyway. 

https://www.dv247.com/en_GB/GBP/iCON-G-Board-Black-USB-MIDI-Floor-Controller-Black/art-PCM0012459-000?campaign=PSM_UK/kelkoo&ProgramUUID=MrLAqJarZEUAAAFobL.P7Dz7

It's designed to be connected to a computer, rather than to another USB MIDI device. You could connect both to a PC, and then use the PC to relay messages from the controller across to the Stomp..... but I can't think of a good reason why you'd want to.... it still wouldn't solve the status indication on the controller situation, and massively overcomplicates the setup...

1 hour ago, dave_bass5 said:

Thanks for the replies. 

I’m not really looking for any displays etc, just a LED to say the switch is on or off. Looks like the Mongoose can do that. The Stomp does show what blocks are on or off, but its not easy to see, especially if i have it on my amp behind me. I know how to use snapshots but i think only 3 is a bit limiting. 

The Keith McMillen looks fantastic, but overkill for me, and a bit expensive. All I’m looking to do is to turn one or two blocks on and off as and when i need to. I can do the patch change by hand on the Stomp itself. I’d never need to do this during a song, and i doubt I’d use more than 3-4 patches for a whole gig. Thanks anyway. 

I think you may have misunderstood the Mongoose's capabilities.... It basically ONLY* does preset changes (ie MIDI PC messages), and the LED and LCD on it are only there to remind you which preset you selected last. 

To switch individual effects on the Stomp, or change snapshots, or.... well, anything that's not a preset change - you need to be able to send MIDI Control Change messages, and that's not what the Mongoose is designed to do.

* apart from the expression pedal input part, but that's not really relevant to what you're asking about.