Hi Hat Artifacts: Possible Improvement?

[OftheSeven]

Thank-you. I think I might know what you are looking for. When the pedal is on its way down, only send the hihat position when the pedal is all the way down. Of course you would send the CC just before any hihat hits as well. Is that what you are after?

Hi Rob,
Did I read that you didn't have an issue using a VH10? Or is it still there just not very obvious?

[vandroiy]

Thank-you. I think I might know what you are looking for. When the pedal is on its way down, only send the hihat position when the pedal is all the way down. Of course you would send the CC just before any hihat hits as well. Is that what you are after?

Sounds good. Ist that something you can try?

[Rob]

I can hear it, but I wouldn't call it show stopping. If you go back 5 years ago, e-hihats hihats were a lot worse. I really think it's a necessary evil to be honest and better algorithms for stitching together hihat audio samples will fix it in the years to come.

I'll think about playing around with the idea I suggested, but I think most users would find it very strange to press the pedal down and not see the CC or hihat image in their software moving. And there's a good chance it'll cause more issues than it resolves.

[vandroiy]

I understand.

Would have to be optional, because many seem to be happy the way it is.

Maybe you get bored some day

[mprinz]

Hi Rob, hi Vandroiy,

that would be an nice option!

This option is similar to the screw that tilts the hihat bottom! Isn't it?
I its screwed out and the hats are perfectly parallel, you wont here anything, moving down the pedal.
If it's screwed in, you will...

Anyway, it the 21st century it should be way possible to smoothly "stitch"
some hihat samples together and play them without jitter.

I'm thinking of a methode that smoothly fades out and in the samples at a certain time,
depending on the first hit. Meaning just pulling the waveform to zero.

Code: Select all

hit            --> closing or openning cc04 ---->
sample 1
0000000000000000000 fate out
sample 2            fate in
000000000000000000000000000000 fate out
sample 3                       fate in
00000000000000000000000000000000000000000000000

At the moment, for me it is "a necessary evil".
But that was actually one reason, why I started playing around with force sensitive resistors. To have smoother transition.
I found out, that it's not the controller, it's the module. And the smoothest curve wont fix anything if you have just 5 samples and a
stupid hihat sampling engine.

Manuel

[vandroiy]

would it be possible to do a kind of MIDI CC Transformation like SD3 does?

Instead of a Trigger Curve, the ability to define Ranges.

Example:

127 - 120 -> 127
119 - 80 -> 100
80 - 30 -> 50
29 - 0 -> 0

[Mylo]

I’m not sure I understand what people are asking for here. If I read the problem statement correctly it seems that the SD3 hi-hat works exactly like a real hi-hat would work. Is it just the transitions to the different levels of closing causing jitters and glitches?

Edit: Never mind... I’m getting it now.

[Rob]

would it be possible to do a kind of MIDI CC Transformation like SD3 does?

Instead of a Trigger Curve, the ability to define Ranges.

Example:

127 - 120 -> 127
119 - 80 -> 100
80 - 30 -> 50
29 - 0 -> 0

Of course it's possible, but perhaps not convenient. While I admit that working with the Bezier curves in eDRUMin might not be as intuitive, they're pretty powerful. And besides, if applications like SD3 have already implemented this feature, would duplicating it in eDRUMin make a whole lot of sense? What's your use case? Why would you want to reduce 7 bit position data down to 2 bits?

[vandroiy]

would it be possible to do a kind of MIDI CC Transformation like SD3 does?

Instead of a Trigger Curve, the ability to define Ranges.

Example:

127 - 120 -> 127
119 - 80 -> 100
80 - 30 -> 50
29 - 0 -> 0

Of course it's possible, but perhaps not convenient. While I admit that working with the Bezier curves in eDRUMin might not be as intuitive, they're pretty powerful. And besides, if applications like SD3 have already implemented this feature, would duplicating it in eDRUMin make a whole lot of sense? What's your use case? Why would you want to reduce 7 bit position data down to 2 bits?

EZDrummer2 and SSD5. Because they (no VST) supports 127 open/close variations, not even 10. And with the Cymbal Pad pressing on the Motion Sensor every time you hit it you get those annoying artifacts. I switched back to a FD9 Pedal because of that.

Still, I understand this probably is an Edge Case, but I would need no bezier curve, but just steps.
There should be a DAW Plugin for that....but I did not found anything yet (except with bidule and personal support from a guy in germany).

[vandroiy]

Forget about it, it`s a stupid workaround.