As for the chick note: I'm going to get a little philosophical here so please don't get mad at me. I was think about this issue. I don't see this as an Alesis "problem". There is no standard on how a variable hi-hat controller should work. Just because we may have used a Roland first doesn't mean that is the way it should be. I also noticed like audiopat the midi note that is generated as soon as you touch the pedal. I wrote to someone close to BFD and asked if these were "problems" and the response was basically that their software can handle any standard HH control signal and thought that the Trigger I/O works just fine with their software. I then was directed to a video on how to set-up a variable hi-hat controller. Here's the link:
http://www.fxpansion.com/fxvideoplayer/videoplayer.php?id=1088.
At least on BFD there is no need for extra software to get the HH controller to work well. Something tell me that it is all about learning the ins and outs of a VST to get it to trigger the way we want. Unfortunately, that is sometimes easier said than done.
What VST are you using? You might want to ask them how to set-up a variable HH controller in their software using an Alesis Trigger I/O. Just a thought. I hope this helps in some way.
Thanks for the info Hellfire. I won't get mad, I'm glad you're trying to help.
Of course there's nothing saying that Alesis has done something wrong or that "The Roland way" or any other brand sets the standard. Remember that one of my questions to Alesis was why they made Alesis Trigger IO the way it is and if they are aware of that it might scare potential customers away from it. Most people are lazy. They want to plug it in and get things done with as little tweaking as possible.
I'm aware of all the tutorials and I've tried my Alesis with both Superior Drummer, Addictive Drums and BFD2. (BFD2 has a very smart way of controlling and manually tweaking where you want your articulations to appear in the cc-range without extra software, and it also has an auto pedal down and splash event)
As I've explained before I can get everything to function, a fully variable hihat with chick sound...but that is with all the workarounds. If the CC wasn't backwards and the chick note didn't trigger in the middle, people could use their Alesis Trigger IO with almost all vsti's without much tweaking and extra software and that's a strong selling point. A patch or something similar that at least made it possible to choose between how Alesis Trigger IO handles the cc-data would be awesome. The same goes for the built in X-talk you've mentioned in another thread. If it would be possible to bypass that (maybe an on and off-setting on each input) you could for example split two stereo inputs and have 4 single zone toms(crashes or whatever) connected to those 2 inputs and all toms could be struck at the same time without any built in crosstalk. That would also make Alesis Trigger IO a very flexible unit that could attract even more customers. And I don't think my suggested features are very hard to implement either.
I just realized I drifted away here and almost wrote a book..sorry
But I see so much potential in this nifty unit from Alesis.