Just wanted my 2 cents in here even though I know it’s been said before. It’s a huge drawback that the H90 cannot receive ccs after a PC, but even if that issue got fixed, the current midi implementation leaves something to be desired. A very common use case for the H90 is that one of the algos is people’s main delay and they use the second algo for secondary effects that aren’t always on (modulation, pitch, etc.). The problem arises when you can’t reliably set a button that always affects delay unless you only ever put the Delay algo in the same program through (I.e program B).
This is unfortunate because then if a different program required the delay to be first in the chain, the current midi implementation would render your button that turns on and off the ancillary effect now turning off the delay. It seems the only way to fix this would be if Algo A and B stayed assigned to A or B, and when you change routing you would see it as A -> B and B -> A instead of the current implementation where it actually moves the algorithms into the alternate spot (A or B) when you change routing.
I’m obviously not a Designer but just want my voice out there because this is a huge hinderance right now for many people I know that also use an H90, and it’s making me consider getting rid of mine because it is so convoluted to use with midi. It is for sure the best sounding delay and mod pedal on the market right now, and I would love to include it on my rig build that I’m dong right now, but it’s hard to justify with the workflow in the current state.
I’d love to know if there is any ETA at all on when midi will be fixed in this pedal, because I feel like I’ve heard it mentioned for months that eventide is continually working on it but this is a pedal that is multiple years into it’s lifespan at this point.
.
