Hi Joe,
Thanks for the info, yes I did try Act/Byp (M) first but when it did not work properly, I decided to try Act/Byp as well.
Joe wrote:
To be clear, the program change should happen “on press,’ while the CC value should be delivered ‘on release.’ In my experience, after the initial press, hold it for like a second before releasing in order to give the program time to load. I know this is not optimal, but we are looking at improving this process, nonetheless.
That’s good to know, I just tried holding down the button longer, however it still did not switch correctly (tried in both Switch Modes). I also hooked up my ES5 and got the same results for all these issues. I’m happy to try other workarounds or help if I can.
Joe wrote:
First off, it would be ideal to save the Space Spiral program in the active state it needs to be in from the start, which by default is “active.” If you need it to start out in a bypassed state, load the program, bypass it, and save it that way; now every time it loads the program it loads it bypassed.
As a Short term workaround I realize this is something that can be done (note that in this second case, it does start in the desired state). However I have to respectfully disagree that this would be a manageable solution. Many gigs I am using the same simple program with a basic reverb and a delay for 10 or 15 songs where I want to make minor changes (1, 2 ,3 parameters) for each and that may include starting in bypass or not or more often using preset bypass (M). I think it would be unrealistic to think I should make 10 or 15 separate version of the same program and try to manage remembering which one has which setting, not to mention eating up my user list. These are just a couple of examples but this issue is not at all limited to these 2 examples. There is not much point in offering CCs if you can’t use them to be efficient and effective . Making separate patches for small variations would be somewhat analogous to changing guitars every time I want to change my volume or tone on my guitar and that’s really not practical.
Anyway, I’m not trying to be a dick here, I love the sounds the H90 has and it is a very powerful box and I really want it to work for me. I just need to access that power via MIDI and am will to help bring issues I find to light. I have spent a good amount of time in the last 5 weeks trying to understand the H90 and make it a useful tool for me. I understand that probably most people don’t have that same workflow as I do but it is a very valid workflow and a good one. I get the sense that you might be belittling these issues (I hope not). I guess it would be important to me to know if these are considered important issues or not to your development team?
Thanks,
Kevin
