I really hate to be that guy but midi has been the most stressful/annoying thing about the NANO… not only is it limited but it doesn’t even work reliably…
So this weekend I had a big show with a Brazilian artist… I saved all the presets and was commanding the presets via HX Stomp. And since the other issue with TRS midi I reported hasn’t been solved yet… I didn’t use TRS midi as that switches of IR/cab block randomly, etc. I instead used a CME h4midi wc so that I could connect midi and then USB c to the nano…
Here’s what happened… Every now and then a preset got ‘‘bugged’’ and no matter how you saved, it would always open with ‘‘reverb’’ OFF … Or the pitch block ON instead of OFF… The weird thing is if you toggle the reverb ON to save the preset again, the save button is still greyed out… Because that’s actually how I saved the preset…
Another frustrating thing in the middle of a performance… There was one section where I had to turn on a drive and cut reverb for specific hits… And guess what… The preset switched ON fine except there was no DRIVE on FX2 …
For most of the show it worked fine but this is just sooo annoying… Like such a basic feature and it doesn’t work reliably…
I’m gigging and recording with many artists regularly and although I always get compliments on sound… the anxiety this has given me in the middle of shows is really something else. Absolute confusion… Granted its not as bad as the IR/amp block switching off with TRS midi but still quite annoying
Hopefully it gets fixed whenever the update comes out
I don’t want to be that guy either, but I think it’s very important that NDSP is aware of the problems We are having to take it seriously and develop a fix ASAP.
So We need to post here and there and make ourselves visible for them. It’s a little frustrating to just get an “email support” recommendation and actually not knowing if they’re doing anything.
We need this solved. The unit is excessively risky for gigging with any midi involved. It’s not a cheapo chinese pedal.
100% … I literally don’t care about extra sounds anymore… I just want to be able to control whats there reliably at least.
I emailed support as well a few times about midi issues… And it’s always the same reply. ‘‘they are aware but can’t comment on update releases’’… Like I get their pov but I also don’t get it… like I had an line 6 M5 which is an OLD unit… Never once had issues with midi and now there’s this fancy nice looking amazing sounding unit but the basic stuff lets you get run over by a train when you least expect it.
If I hand’t moved country I would’ve 100% returned it to the shop I bought, even though I love the sound… super frustrating but oh well
Yeah. I never had any MIDI issues in the past, ever, with any other gear. Used MIDI with several old Zoom units (through USB host adapters), Atomic Amplifire, Helix LT… always rock solid.
And I agree, that reply from the support team is not good. They told me the same “We can´t comment on future updates” several times. Hell, We just need them to tell us something to get some peace of mind. I know they can´t comment details, but We don´t ask them either. Simple info like “this winter” (for instance) would be fine. And by the way, I don´t know if other mates have the same experience as me, but I was useful to them pointing out some errors of the unit that they were not aware of… We had conversations, they were responsive and fixed some issues. I can´t understand why they don´t just have the same behaviour (even with a less detailed approach) regarding updates.
They´ve been doing it great with the Nano, regarding updates. The unit has improved vastly from the launch, no doubt about that. There´s a lot to thank NDSP for. But reliability matters should be a critical area to fix, and they should act like so and release fixes before We all sell our units because of inadmissible unreliability for gigging.
The detail in your post that stands out is the greyed-out save button when the preset is in the bugged state, because that suggests the unit thinks the preset is unmodified while the block state on screen says otherwise. That is a state-sync problem rather than a MIDI parsing problem, and it would explain why it happens across both TRS and USB paths, and why cardinal sees it on the noise gate while you see it on reverb and pitch: whichever block got toggled last is the one that goes out of sync. If that is right, then the trigger is probably a program change arriving while the unit is still writing or loading, not the specific block. Two things that might help you survive gigs until the firmware lands. Add a small delay between your PC messages on the HX Stomp if it lets you, so nothing arrives mid-load, and avoid sending a PC and a CC in the same instant. Also try saving each preset, power cycling, and reloading it once before the show, so anything that did not commit shows up in soundcheck rather than mid-set. For the bug report, the greyed-out save button plus the exact sequence of messages is the most valuable thing you can give support, since it is a reproducible symptom rather than a description of randomness. Worth adding that to the ticket if it is not in there already.
@HelenMarsh thanks for that input! What you’re saying makes sense even though it’s beyond my knowledge of how it works internally!
I will try to experiment with the delay, I’m pretty sure you can do it on the HX stomp for some messages.
There has to be something happening with that. Cause even when using TRS Exp pedal it can sometimes trigger the CAB/IR block to go off… So something with the toggle states of each block has some bug/coding error.
But then again, we buy pedals to play guitar… just tired of troubleshooting… appreciate your suggestion though, I will 100% try it out!