stoo

3 hours ago, Bklyn3 said:

Finally finished this project. 
Thanks Stoo for the idea. 
I added a feature to control YouTube which is super useful when practicing. 

Wow - that looks awesome!

15 minutes ago, warwickhunt said:

Pretty much their first overseas instrument was essentially a passive Stringray...

 

You sure?

 

The early OLP "Stingray"s were passive but they were named MM2 / MM3, not SUB...

 

Are YOU sure?  

 

IIRC the first overseas instrument was the Japanese Stingray EX (active) which was effectively the USA Stingray assembled overseas, which was 'exactly' a USA Stingray but doesn't have the made in USA legend on it.  

 

 

 

I hadn't assumed my list was exhaustive, but I think what I put was accurate - wasn't it?

Had definitely forgotten about the EX ones though...  

On 21/12/2023 at 15:43, Jack said:

And you can have a USA Sterling, but there is as of yet no Sterling Sterling.

There was - except they called it an SB14 and discontinued it again after a while.... presumably after getting fed up of having to explain what it was

On 21/12/2023 at 15:43, Jack said:

Pretty much their first overseas instrument was essentially a passive Stringray, they called it the SUB. They now use the SUB name for the whole line of cheapest basses they make. They are not passive.

You sure?

The early OLP "Stingray"s were passive but they were named MM2 / MM3, not SUB

The EBMM SUBs came as both active and passive (I've got an active one from 2003 and a 2004 one that was originally passive) but were made in USA

Then OLP came out with the active HH models in 2007.... named MM22 / MM32, not SUB

I think the Sterling by Musicman SUBs were always active, weren't they? I had one of the early ones not long after they came out and don't remember there being a passive option at the time? Was a while ago though - might be misremembering

On 28/08/2023 at 04:30, stringvelocity said:

Is there a way to add an expression pedal to this code??

Sorry - I was sure I'd already replied to this... must have closed the window before the post got submitted.

The nextion/mega version has an expression pedal input, but the oled/nano original version didn't.

If you wanted to add an expression pedak to the oled/nano version, you'd need to add the extra bits in yourself depending on how you want yours to work.

My implementation was a bit odd because my "expression  pedal" was actually a converted wah pedal - so it had a audio taper pot instead of linear, and a latching footswitch instead of momentary. If you have a linear pot expression pedal and a momentary switch (or no switch at all) then you could probably simplify things a lot

3 hours ago, Bklyn3 said:

Hello All,

 

I am upgrading my version of this pedal with several .96 OLED screens and I was wondering if anyone has a way to retrieve the names and settings of a preset by reading it from the HX Stomp directly. Either via MIDI or USB (similar to what HX Edit does). 
currently I hard coded them but that’s ideal. 
 

Thank you 

 

P. 

Nice - it looks like Heiko has made some decent progress on cracking the USB comms between his Stomp and HX Edit... In his project he uses Python scripts on his computer to get the info from the Stomp - 

https://line6.com/support/topic/60839-another-lockdown-project-talk-to-your-hx-stomp-over-usb/

https://github.com/kempline/helix_usb 

I'd planned to see if I could get something similar working on Arduino with a USB host adaptor.... life keeps getting in the way though!

13 hours ago, stringvelocity said:

How would I go about making a button or buttons programmable?

That would require some extra code to be written to support it.... As mentioned above, I had originally intended to, but found I didn't need it.... And so that part never got finished.

Feel free to have a go though!

On 13/02/2023 at 01:28, DaveHx said:

sorry, maybe was the euphoria of the moment 😆 i just want to go on the other two NexPage(program_page and Other_Page) , but i see here i can change only the menu on the main page with the switch, i need to push the combo for the Macro, right? again thank you stoo for you patience 😁

Ah ok I see... The extra pages in the Nextion file were just a placeholder for future functionality that I intended to implement. I had initially planned to make everything re-programmable from the touchscreen without needing the computer......

But once I got the first prototype built and working, I found I didn't need to reconfigure the pages and so didn't do any more work on that functionality.

48 minutes ago, DaveHx said:

Oh god yessss it work 🥳🥳🥳🥳🥳 i don't know even what I do 😆 just makes all the ground again 🫣 thanks for everybody gives me help 🥳🥳🥳🥳 i just only have one question, how i can use the other two pages? Just because I want to use a relay for switch the od on or bypass, but really thank youuuu🤩🤩🤩🤩

Nice one! Frustrating that you don't know exactly what the issue was - hopefully just a loose connection that needed to be reseated.

What's the issue with the other pages? Sorry - I don't understand your question.....

12 hours ago, DaveHx said:

yup but the electronic connection are ok even because i used the tra cable for the midi connection i checked the pin on the Midi connector and everything is ok, i put the 220 ohm resistor on 5 volt and 220 on tx cable so for this reason i was thinking there was a problem with the screen cause is the only different thing from your project 🥴 and i mean i made a switcher before with the ssd1306 and it worked a lot! 🙄 but just for ask, on serial monitor here on arduino IDE i don't have the possiility to check if it work?

 

I don't understand why you are so confident that you've got everything correct with the midi output.... If that was the case, then the simple midi output test sketch I posted should change presets on your HX.....

Been a while since I used serial monitor, and i only used it on the default serial port.... Arduino Mega has several, so you may need to change the monitor to the one used for the midi output... Not sure if that's possible - not in front of a computer to check

Aaaah - just found a link to someone who has had some success decoding the usb communications between stomp and hx-edit. I think I saw them mention it before on Facebook but never saw any further details. There's a link to some stuff on GitHub and their demo with an FBV3 - https://line6.com/support/topic/60839-another-lockdown-project-talk-to-your-hx-stomp-over-usb/

Guess I might have to start work on a v3 controller with scribble strips and RGB footswitch LEDs....

1 hour ago, DaveHx said:

it doesn't work yet even with this, noting changed, so i checked on nextion editor, maybe there's something wrong there, and i thinked my version of N.E. was the last so i checked again everything and the editor basically re arranged the code for the new versione, so a part the id he changed the program page as you can see on the screenshot, and so i wanted to ask you if was there another code or it's the same for you, maybe this is the error i have when i start the serial monitor! thank you stoo!

Ignore the nextion for now. You've already shown that you have that part working and communicating with the Arduino.

If you don't have the midi output part working correctly, any further testing with the nextion is impossible as you have no way of knowing if its doing anything. 

On my switcher, I can press the FS1,FS2,FS3 etc buttons on either the screen or the actual footswitches..... And if the midi cable is not correctly connected, nothing will happen. There is no visual indication on the screen to confirm the button press.

13 hours ago, stringvelocity said:

Is there a way in your code to set a couple of buttons to toggle?

Yep - look at the looper fwd/rev button part as an example

3 hours ago, DaveHx said:

so, maybe, but maybe and i don't know yet,  i found the problem! i saw when i charge the sketch on Arduino this kind of message for every single midi message CC PC and other, but always on midi, soooo i think this errors can compromise the normal functioning of the midi side... so did you have any idea of how i can fix it? by the way i'm sure the midi connection are absoltely ok (wiring i mean), thank you man i am so really grateful for your help

 

 

I don't think that'll be it.... 

It's a warning that I've sent a "string" type value as an argument to a function that has a "char*" type value as its parameter. This is something that used to be allowed - it didn't throw up any errors for me when I built my one 3 years ago. They've since changed the rules.... but I think this is still just a warning that can be ignored. Not totally certain - but I can't easily test with mine at the moment to confirm....

What you could do to test your MIDI output is to use some simpler code that tests only the MIDI output part... I think something like this should work... If it does, it will just change back and forth between 2 presets every second

#include <MIDI.h>

MIDI_CREATE_INSTANCE(HardwareSerial, Serial2, MIDI);

void setup() {
	MIDI.begin(MIDI_CHANNEL_OMNI); // Launch MIDI and listen to all incoming messages
	}

void loop() {
	if (MIDI.read()) // If we have received a message
	{
		MIDI.sendProgramChange(1, 1); // Send a PC1 on channel 1
		delay(1000); // Wait for a second
		MIDI.sendProgramChange(2, 1); // Send a PC2 on channel 1
		delay(1000); // Wait for a second
		}
	}

58 minutes ago, DaveHx said:

Okok, thank you stoo, i checked every switch, every pin and every single wire, everything is fine, and now something changed, when I press the switch for change the page it work! But not the single switch 😮‍💨 but at the least something on the switchpin work! 

I noticed even something strange when I open Serial Monitor, "recvRetCommandFinished ok

 recvRetCommandFinished ok

 recvRetCommandFinished err" 

And  i don't understand what it means 😅

 

 

the "recvRetCommandFinished" messages look to be something that the Nextion library generates...  (see line 187 here - https://github.com/itead/ITEADLIB_Arduino_Nextion/blob/master/NexHardware.cpp) - looks like it's probably a message from the Nextion back to the Arduino to say that it's recieved a command and confirm it's completed it OK.

I'm not sure why the 3rd one reports an error - it doesn't give much information to go on - but the first two report as "ok"... so I would think the basic communication between your Arduino and Nextion is probably OK.

If your footswitches can change the page on the Nextion - then you've definitely got communication between the footswitches and the Arduino, as well as between the Arduino and Nextion..... so you're most of the way there now!

Next thing to investigate is the MIDI connection to the HX...

19 hours ago, DaveHx said:

In this photo i tried only the switches connected like your schematic, but it was the same yesterday, it's d0 to d7 but it's not on analog pin... by the way i tried on the analog pin and nothing happen 🥲 i think i'm at the dead point... but even with this problem i try every day, just to understand where i'm wrong 🙄 always thank you stoo!

I'm not sure I understand what you're attempting here..... if you only have the footswitches connected, but not the screen or the MIDI output...... then not much is going to happen!

If you're using the code from my project, then the switches will need to be connected to the 0-7 switches as shown in your picture.... the Analog pins at the bottom can be used for inputs, but you'd need to change the code to listen on different pins.....

In the video you posted above, it shows you pressing the >> button, and then the screen changing the menu page.... That shows that you had the connection between the Arduino and the Nextion working OK. (The Nextion sends a notification to the Arduino that you've pressed the button on the screen, and then the Arduino updates the menu page and then sends an instruction back to the Nextion to change the display to match)

Once you have the Nextion working, it's easier to test the MIDI next. Hook up the MIDI socket and your HX device and then press the FS1 button on the Nextion screen..... something should happen on the HX (as long as you're in a patch that has an action assigned to FS1!)

Once you know that's working, then try the switch inputs on the Arduino. If you're not 100% confident in your footswitches, leave those disconnected and just use a test wire - Connect one end of it to a spare GND pin on the arduino, and then try touching it on any of the 0-7 pins (NOT the ANALOGIN A0-A7 pins!) and see if that does anything. If that works, then you know you need to investigate the wiring for your footswitches

Good luck!

18 hours ago, DaveHx said:

i tried with and without midi out, nothing happen... as you can see in the video when i press something on the screen there's a little blink, and the switch doesn't work in every pin (strange cause i checked all the connection) i noticed even the previous page button doesn't do nothing, so this makes me think probably can be something wrong on nextion? i used this link https://nextion.ca/portfolio-items/nextion-iteadlib-and-mega-step-by-step/ as you said, and there i put on my nexConfig.h

/** 
 * Define DEBUG_SERIAL_ENABLE to enable debug serial. 
 * Comment it to disable debug serial. 
 */
#define DEBUG_SERIAL_ENABLE

/**
 * Define dbSerial for the output of debug messages. 
 */
#define dbSerial Serial

/**
 * Define nexSerial for communicate with Nextion touch panel. 
 */
#define nexSerial Serial3

 

and i changed   
    dbSerialBegin(250000);
    nexSerial.begin(115200);

on NexHardware.cpp

i changed only this in your code for now, i'ts the second switcher i made based on your code, the oled was mooooooore easy 😆 maybe cause i never used a Nextion and Mega before 😅 thank you stooooo🤗

 

 

 

Do you have your switches connected to A0-A7 ?

Doesn't look like anything is connected to pins 0-7 on the Arduino at all.... that's where I had my switches connected....

37 minutes ago, stringvelocity said:

This is great but I have found an issue with pressing two buttons at once… not sure if the bounce needs to be change or if it’s my buttons… it seems to either go on/off or skip to the next depending on what it’s set too.. any thoughts??

I think I know what you mean..... If you have, for example,

- switch 0 set to toggle FS1,

- switch 1 set to toggle FS2, and

- switch 1+2 set to scroll to next page,

then when you press switches 1 and 2 it might trigger FS1 or FS2 before eventually also triggering the next page.

If so, then that's a limitation of the way it was written. When the Arduino scans the buttons, as soon as it detects a button press it does the action assigned to that button straight away. Then it continues to scan the button states, and if it detects another button is pressed down before the first button was released then it checks if there's an action assigned to that combination of buttons.

Another way of doing it would be to wait for either the first button to be released, or a second button to be pressed, before triggering the action. This would allow you to prevent accidental triggers of the single switch function when you only wanted the combo function..... but it would have a really bad side effect. If you just wanted to trigger FS1, and so stepped on switch 0.... nothing would happen until you lift your foot off the switch again. This delay might not be too noticable if you instinctively tap and release each switch very quickly all the time..... but I definitely don't do that. If you have buttons configured for looper controls instead of just effects on/off toggles then the problem gets even worse.

Hope that makes sense

On 29/01/2023 at 22:57, DaveHx said:

Hey @Stoo i was making the hx stomp switcher 2 , i was havin the same issue of Guillame, on page 6 of this topic, i followed your instruction and woah he nextion work but, yes there's another terrible issue, when i press the switch nothing happen but when i press The switch on pin 0 and pin 1 this makes the rx and lx led blink, soooo did you have any suggestion about? what can be wrong about? thank you stooo you are super!

So.... if you press the buttons on the Nextion screen, the MIDI commands get sent to the stomp as you would expect? that bit works OK?

Do the other switches work as you would expect on pins 2 thru 7 ?

Pin 0 and Pin 1 on a Mega can be used as either regular digital pin inputs, or as a Serial channel as RX0/TX0 - I'm not entirely sure if it would be expected to see TX/RX lights illuminated when using Pins 0 and 1 as digital inputs.... I never noticed it happening on mine when I was building/testing it, but I wasn't particularly looking out for it at the time. I can't easily get to mine to check it at the moment. I think if you have somehow got the nextion or the midi trying to talk on Serial0 then strange things might happen, but if you're using a Mega and your code is the same is mine, then I can't see how that'd happen....?

3 minutes ago, tauzero said:

 

From arduino.cc: "If you used Arduino Nano in your projects in the past, the Nano Every is a pin-equivalent substitute. Your code will still work, and you will NOT need to re-wire those motors you planned in your original design. The main differences are: a better processor, and a micro-USB connector."

Bit more info on why I thought that might not always be the case:

https://emalliab.wordpress.com/2021/12/15/getting-to-know-the-arduino-nano-every/

Might be worrying about nothing for most use cases, but suspect it'll just depend on which libraries you end up using...

13 hours ago, stringvelocity said:

Is there a big difference in programming the nano vs the nano every?

Dunno - I haven't used the Nano Every, but it looks like it's the same form factor as an original Nano, but with a different processor.

I would guess they've tried to make it backwards compatible with code written for the original Nano, but there's always the risk that a library has tried to refer to specific parts of the hardware directly to maximise speed or efficiency.

4 hours ago, stringvelocity said:

Is it possible to change the 2 switch press to send a CC instead of pageup or down?

Sure - just look for this bit:

void changePageUp() {
  currentPage++;
  if (currentPage >= pageCount) { // we have gone past the last page
    currentPage = 0; // reset to first page
  }
}

void changePageDown() {
  currentPage--;
  if (currentPage > pageCount) { // we have scrolled back past the first page
    currentPage = (pageCount -1); // reset to last page
  }
}

And change it to something like :

void changePageUp() { // function adapted to send MIDI CC instead of controller Page Up
  const byte controlNumber = 49; // MIDI CC# number to send - CC49 is FS1
  const byte controlValue = 0; // MIDI Value to send - can be any 0-127 for CC49 -> FS1
  const byte midiSendChannel = 1; // MIDI channel to send this message on
  MIDI.sendControlChange(controlNumber,controlValue,midiSendChannel);
}

void changePageDown() { // function adapted to send MIDI CC instead of controller Page Down
  const byte controlNumber = 68; // MIDI CC# number to send - CC68 is tuner on/off
  const byte controlValue = 0; // MIDI Value to send - can be any 0-127 for CC68 -> tuner on/off
  const byte midiSendChannel = 1; // MIDI channel to send this message on
  MIDI.sendControlChange(controlNumber,controlValue,midiSendChannel);
}

Ideally you'd also also go through and change all the PageUp and PageDown functions, variable names and comments elsewhere to make things easier to follow / troubleshoot when you next come to look at the code. I'll leave that up to you to decide whether to bother though...

4 minutes ago, stringvelocity said:

So I should technically be able to use this program with either 4 or 8 buttons and with or without a LED?

The arduino definitely won't care if you have less buttons..... it can't tell the difference between a button you aren't pressing and a button that doesn't exist.

I think you'd probably be fine with no OLED, but you'd have to test it and try.... I know the display startup sequence will flash an error LED if it doesn't correctly detect the OLED, but can't remember if it just flashes and moves on, or keeps blinking until you fix the problem. Either way, would only need to remove the display related bits of the code for it to work again.

2 hours ago, stringvelocity said:

I’m working in doing this build with just the four buttons and no led… 

Fair enough - but the two different versions I've made and posted the details for use completely different codebases - so if you're asking questions about the code, we'd need to work out which one you're starting from as the answers will probably be different depending on which you've chosen.

1 hour ago, stringvelocity said:

I really just want to make sure my hx is on the right channel to communicate with the pedal or vise versa

Ah in that case - both of the ones I wrote send on channel 1 by default. And the HX stomp listens on channel 1 by default as well....

36 minutes ago, tauzero said:

 

I think they're probably using the https://github.com/stoonoon/hxsMidiSwitcher version which wouldn't have that bit in it though.....

11 hours ago, stringvelocity said:

Is there a line in the code somewhere that says what channel it’s sending on?

If you're using the Nano/OLED version, I didn't really consider changing the MIDI channel at the time.... No reason why it can't be changed, but it'll take a bit more effort than just changing one value, unfortunately....

In the mega/touchscreen version I fixed this by declaring the "midiSendChannel" constant using the line that tauzero mentioned before:

const int midiSendChannel = 1; // MIDI channel for outbound messages

and then whenever I called the MIDI library to send a message, it references that constant to decide which channel to send on.

MIDI.sendControlChange(controlNumber,controlValue,midiSendChannel);
MIDI.sendProgramChange(programNumber,midiSendChannel);

On the earlier version though, the channel number is just hard coded into each MIDI send call's parameters, like these:

MIDI.sendProgramChange(0,1);
MIDI.sendControlChange(68,68,1); //tuner

You could go through and replace each of those with your new channel number, but I'd be tempted to do a find and replace for

,1)

to

,midiSendChannel)

and then add the 

const int midiSendChannel = 1; // MIDI channel for outbound messages

somewhere near the top... then you could just change that 1 to whatever channel you wanted to use, and if you decided to change again in the future it'd be that much easier to do.