Translationwent back to 27 and it worked
went up to 29 and it stopped working
went back to 27 and it works
will not try again for now
if it works for rob, maybe someone else trying at would be nice, though
Hi Hat Artifacts: Possible Improvement?
Re: Hi Hat Artifacts: Possible Improvement?
went up to 29 and it stopped working
went back to 27 and it worked
went up to 29 and it stopped working
went back to 27 and it works
will not try again for now
if it works for rob, maybe someone else trying at would be nice, though
went back to 27 and it worked
went up to 29 and it stopped working
went back to 27 and it works
will not try again for now
if it works for rob, maybe someone else trying at would be nice, though
Re: Hi Hat Artifacts: Possible Improvement?
31 is out now. Check the Beta 1.1 thread. How about it?
Re: Hi Hat Artifacts: Possible Improvement?
works! 
This is a game changer. Again Thank you very much, Rob.
This is a game changer. Again Thank you very much, Rob.
Re: Hi Hat Artifacts: Possible Improvement?
Thanks for confirming. I realize this improvement does not address the original poster's request, but I'm still thinking about it and a few other possible improvements I can make. I'll leave those for version 1.2.
-
Karbonfaiba
- Posts: 2
- Joined: Sat Aug 01, 2020 1:15 am
Re: Hi Hat Artifacts: Possible Improvement?
I was just browsing this forum out of interest in eDRUMin and happened to recognise my writing in one of the quotes from the OP.
Very pleased to read that such attention is being paid to this hi-hat issue on here. You seemed to have coined it; Hi-hat (pedal) crosstalk? I also think this best describes the function we are looking a trigger module to cure... in short; a smart algorithm implemented on the trigger side to remove transmutation artefacts. As it's been correctly pointed out; VSTs don't seem to offer much in the way of finding a solution to this when "normal" drum modules have accounted for it.
So from the last few pages, I learn't that the issue isn't necessarily affecting all hi-hats - which makes perfect sense - prominently, we are mostly looking at any hi-hats where the trigger pad clutch is in direct contact with a motion controller, e.g. VH-10/11.
The data Rob collected also interests me; that it shows not only what I expected to see; the CC data fluttering with stick play, but what I did not expect, actually bouncing upwards too!
I previously suggested removing the transmitting of CC data during downward motion, and leaving upwards motion alone as a potential fix - but it looks like you might have worked out something better.
My only concern was not just adding a simple delay on reading on CC data after a note (to ignore movement for say 50ms) as that would introduce so much lag that it would spoil the point of transmutes in the first place - the key moment where you need it for natural hi-hat barking, from a closed position, without having to lead ahead of the beat with your foot to account for the flaws of most e-drum hi-hats.
Interested to see how exactly it works, hopefully in the not to distance future.
Very pleased to read that such attention is being paid to this hi-hat issue on here. You seemed to have coined it; Hi-hat (pedal) crosstalk? I also think this best describes the function we are looking a trigger module to cure... in short; a smart algorithm implemented on the trigger side to remove transmutation artefacts. As it's been correctly pointed out; VSTs don't seem to offer much in the way of finding a solution to this when "normal" drum modules have accounted for it.
So from the last few pages, I learn't that the issue isn't necessarily affecting all hi-hats - which makes perfect sense - prominently, we are mostly looking at any hi-hats where the trigger pad clutch is in direct contact with a motion controller, e.g. VH-10/11.
The data Rob collected also interests me; that it shows not only what I expected to see; the CC data fluttering with stick play, but what I did not expect, actually bouncing upwards too!
I previously suggested removing the transmitting of CC data during downward motion, and leaving upwards motion alone as a potential fix - but it looks like you might have worked out something better.
My only concern was not just adding a simple delay on reading on CC data after a note (to ignore movement for say 50ms) as that would introduce so much lag that it would spoil the point of transmutes in the first place - the key moment where you need it for natural hi-hat barking, from a closed position, without having to lead ahead of the beat with your foot to account for the flaws of most e-drum hi-hats.
Interested to see how exactly it works, hopefully in the not to distance future.
Re: Hi Hat Artifacts: Possible Improvement?
To the original poster, your request has been granted in version 1.3 BETA in the form of an option called 'Only Send CC on hit'.
viewtopic.php?f=29&t=680
viewtopic.php?f=29&t=680
Re: Hi Hat Artifacts: Possible Improvement?
Very looking forward to test it out.
Even the current implementation in 1.2 is providing a better HiHat response over MIDI than any module I ever used (Roland, ATV, 2Box). At this pint you realize that the edrumin is made for Trigger to MIDI, while with every other Module it is a feature that`s not top Priority.
It fits my playing style now so well that I would caution ambitioned players who switch between acoustic and electronic to be very sensible with such options. I personally play acoustic very rarely and the HiHat is the one thing I have trouble getting used to when I do (and that I actually have to lay into the kick drum to get a powerful sound )
With the powerful options of the edrumin you can hide your flaws, or very closely replicate the dynamic response of an actual drum. It is your choice.
Even the current implementation in 1.2 is providing a better HiHat response over MIDI than any module I ever used (Roland, ATV, 2Box). At this pint you realize that the edrumin is made for Trigger to MIDI, while with every other Module it is a feature that`s not top Priority.
It fits my playing style now so well that I would caution ambitioned players who switch between acoustic and electronic to be very sensible with such options. I personally play acoustic very rarely and the HiHat is the one thing I have trouble getting used to when I do (and that I actually have to lay into the kick drum to get a powerful sound
)With the powerful options of the edrumin you can hide your flaws, or very closely replicate the dynamic response of an actual drum. It is your choice.
Re: Hi Hat Artifacts: Possible Improvement?
The splash sound is generated but always after a chick sound... I hear "chi-woosh" I just want to hear "woosh", bummer...
Re: Hi Hat Artifacts: Possible Improvement?
Isn't that how other modules work as well? If you only wanted the splash, I would have to add about 30ms delay to the chck note. I don't think that's something most people would find acceptable.
Re: Hi Hat Artifacts: Possible Improvement?
in roland modules, when playing a splash, the chick sound is heard but very rapidly and then the splash sound comes in, it's almost like the 2 at the same time, like on a real hihat, it sounds "chwoosh", it's hard to differentiate both sounds so fast but they are there, the thing with the edrumin is there's a really long time between the chick and the splash sound, as I said, it sounds like this "ka-ching", instead of "chwoosh" with more emphasis on the woosh than on the ch if you know what I mean...