TranslationI now sold my TD17 and use 2 edrumins for my A2E Set: Works amazing! I am spreading the word everyhwere I can, hoping you have success with it and can go on implementing new features or future generations of this amazing product!
Question:
There is an issue with (every) moveable HiHat, moving the sensor down when hitting the Cymbal Pad hard. The modules seem to have it covered, the VSTs I use (SD3 and SSD5.5) not.
Explanation in the vdrums forum
There is a thing: the Toontrack hihat engine "issue". Their engine lacks the option of not triggering closer stages by foot movement after open strokes. And this sometimes causes annoying artefacts when the variable hihat is set up to many open-closed-stages (ok, you might say: reduce the stages - but sometimes I want them!) :
When I close an open stroke by a relatively slow foot movement I notice that the closer articulations are triggered by the increasing CC values over the course of the closing-process. This hihat behaviour causes jittery artefacts! Noticeable more or less: depends on the hihat model and the sound-settings and of course on the foot movements. And according to which samples of the round-robin engine take effect: noticable on my audio file with 2 sequences of events triggered by the same midi data: the events at position X do not sound the same regading the jittery or shaky amount.
Almost all other drum sampler manufacturers (except StevenSlateDrums that has got the same "feature"/"issue") offer a variable hihat engine that won't trigger closer stages only by increasing CC values.
One user suggested:The solution is that I achieve a hihat that works like e.g. BFD2/3, AddictiveDrums2, Ableton DrumSamplers and Roland internal module sound: an open sound won't be disturbed by foot movement until the "Chick" is reached.
Do you think it would be possible and make sense to implement something like that as an option in the edrumin?If you play semi-open hihat patterns right on the threshold of being closed; then the force of the sticks against the trigger would be enough to briefly transmute the articulation. Hence the need of a strong spring to reduce the chance of this. So in this case, the best option would be to block all transmutes down to closed levels, leaving just the chick note (which is a separate midi event) to determine the closed position.
PS: What I currently do is "recude the stages", because the RHH135 is not that sensible anyway. But especially with a ATV or Roland HiHat you could really make a difference with that feature, for every VST and every DAW.
