If you want to understand fully just try writing out the simplest algorithm for it.
Is that a late peak in the transient or is the drummer doing a fast double stroke roll? Figure that out and you’re well on your way to understanding all of this.
Bezier velocity curve
Re: Bezier velocity curve
Hi guys, hi Mylo,
that's what I said in the Hall effect thread.
The "cheap-module" users, dont know a "scan time". I even dont know how to interpret the "Sensitivity" of my module.
In the end, it was the Gain. "Treshold" clear. "Head/Rim sens" ... If you know how all that stuff works, the parameters a quite clear.
I found this, this morning.
This guy has 3D printed his own pads, and build an optical hihat controller (I guess with non-linear response, as well ,
I think a soft-pot voltage divider is the simplest and cheapest way - and linear. )
https://github.com/RyoKosaka/HelloDrum-arduino-Library
The piezo sensing code unfortunatly is capsuled in libraries.
Anyway, nice pics here.
that's what I said in the Hall effect thread.
The "cheap-module" users, dont know a "scan time". I even dont know how to interpret the "Sensitivity" of my module.
In the end, it was the Gain. "Treshold" clear. "Head/Rim sens" ... If you know how all that stuff works, the parameters a quite clear.
I found this, this morning.
This guy has 3D printed his own pads, and build an optical hihat controller (I guess with non-linear response, as well ,
I think a soft-pot voltage divider is the simplest and cheapest way - and linear. )
https://github.com/RyoKosaka/HelloDrum-arduino-Library
The piezo sensing code unfortunatly is capsuled in libraries.
Anyway, nice pics here.
Re: Bezier velocity curve
I messed with that library about a year ago. WOW! It looks much more fleshed out now. Nice work.mprinz wrote:https://github.com/RyoKosaka/HelloDrum-arduino-Library
The piezo sensing code unfortunatly is capsuled in libraries.
Anyway, nice pics here.
-
- Posts: 173
- Joined: Mon Aug 31, 2020 11:25 pm
Re: Bezier velocity curve
That's exactly what I was looking for. I come from an Alesis Nitro and there's no mention of scan time or decay. Only threshold, sensitivity, volume and xtalk. I was not aware of the terms.mprinz wrote:Hi guys, hi Mylo,
that's what I said in the Hall effect thread.
The "cheap-module" users, dont know a "scan time". I even dont know how to interpret the "Sensitivity" of my module.
In the end, it was the Gain. "Treshold" clear. "Head/Rim sens" ... If you know how all that stuff works, the parameters a quite clear.
I found this, this morning.
This guy has 3D printed his own pads, and build an optical hihat controller (I guess with non-linear response, as well ,
I think a soft-pot voltage divider is the simplest and cheapest way - and linear. )
https://github.com/RyoKosaka/HelloDrum-arduino-Library
The piezo sensing code unfortunatly is capsuled in libraries.
Anyway, nice pics here.
This page explains really well in context what each settings do.
If I understand the scan time is the time the module takes to find the peak of the hit and see for example if there's a choke on cymbal ?
For those like me, I found a video of 65drums with other good explanations : https://m.youtube.com/watch?v=SX7K0veLMJQ
Is hold or decay the equivalent of mask time?
Last edited by thenewdrummer on Wed Sep 23, 2020 11:22 pm, edited 1 time in total.
- dsteinschneider
- Posts: 415
- Joined: Sun Sep 15, 2019 11:17 pm
Re: Bezier velocity curve
I spent a lot of time studying these topics while getting my MegaDrum dialed in. It has probably every parameter adjustment needed but they interact with each other and I don't believe it has much in the way of top level algorithms to help deal with those interactions. The parameters are all in a database style presentation and you're left to guess what the wave form from the piezo is doing. I got mine working pretty well but there always remained small imperfections in the sensing, for me it was mostly missing hits which is very disconcerting when you're playing. The bezier curve with two handles is so much nicer than picking a preset curve. You can play a little - pull the curve, play some more until it feels natural.
Re: Bezier velocity curve
The mask time is the hold time + decay, that's how it's looks like for me. He didn't separate those.thenewdrummer wrote: I come from an Alesis Nitro and there's no mention of scan time or decay. Only threshold, sensitivity, volume and xtalk. I was not aware of the terms.
This page explains really well in context what each settings do.
If I understand the scan time is the time the module takes to find the peak of the hit and see for example if there's a choke on cymbal ?
For those like me, I found a video of 64drums with other good explanations : https://m.youtube.com/watch?v=SX7K0veLMJQ
Is hold or decay the equivalent of mask time?
Justin from 65Drum, you mean. Yeah.
That's it, we Alesis user just got: Sens, Head/rim sens, tresh, xtalk, and retrig cancel.
You can listen to the audio output ... What those settings change.
eDrumIn: Gain for the two inputs, treshold can be adjusted, xtalk , and you ALWAYS can have a visible
"feedback" what those settings do. Great for all the settings... Fast and accurate. Because - you see, what you HAVE TO
set for a good trigger result!
What is the analog setting for the retrigger cancelation. On the eDrumIn we set the Scan, Hold and Decay to adequate values.
I could imagine that at an Alesis Module the scan time is fixed an they set the Hold/Decay with the retrigger cancel? So, the Snare was the first pad I used with the eDrumIn. Especially, due to the possibility to get a side stick triggering.
Not possible with my Millenium/Alesis/Medeli/Fame ...
AND those nice Bezier curves for velocity AND CC scaling... beautiful!
-
- Posts: 173
- Joined: Mon Aug 31, 2020 11:25 pm
Re: Bezier velocity curve
Yeah I don't know why I wrote 64 instead of 65 heheh. I know I had to rewrite the sentence because of the bad copy paste of the phone. It might have introduced the typo Hehehe. I fixed it.mprinz wrote:The mask time is the hold time + decay, that's how it's looks like for me. He didn't separate those.thenewdrummer wrote: I come from an Alesis Nitro and there's no mention of scan time or decay. Only threshold, sensitivity, volume and xtalk. I was not aware of the terms.
This page explains really well in context what each settings do.
If I understand the scan time is the time the module takes to find the peak of the hit and see for example if there's a choke on cymbal ?
For those like me, I found a video of 64drums with other good explanations : https://m.youtube.com/watch?v=SX7K0veLMJQ
Is hold or decay the equivalent of mask time?
Justin from 65Drum, you mean. Yeah.
That's it, we Alesis user just got: Sens, Head/rim sens, tresh, xtalk, and retrig cancel.
You can listen to the audio output ... What those settings change.
eDrumIn: Gain for the two inputs, treshold can be adjusted, xtalk , and you ALWAYS can have a visible
"feedback" what those settings do. Great for all the settings... Fast and accurate. Because - you see, what you HAVE TO
set for a good trigger result!
What is the analog setting for the retrigger cancelation. On the eDrumIn we set the Scan, Hold and Decay to adequate values.
I could imagine that at an Alesis Module the scan time is fixed an they set the Hold/Decay with the retrigger cancel? So, the Snare was the first pad I used with the eDrumIn. Especially, due to the possibility to get a side stick triggering.
Not possible with my Millenium/Alesis/Medeli/Fame ...
AND those nice Bezier curves for velocity AND CC scaling... beautiful!
-
- Posts: 173
- Joined: Mon Aug 31, 2020 11:25 pm
Re: Bezier velocity curve
Since you said that alesis modules are different I decided to take a look at the manual of a Roland TD12.mprinz wrote:The mask time is the hold time + decay, that's how it's looks like for me. He didn't separate those.thenewdrummer wrote: I come from an Alesis Nitro and there's no mention of scan time or decay. Only threshold, sensitivity, volume and xtalk. I was not aware of the terms.
This page explains really well in context what each settings do.
If I understand the scan time is the time the module takes to find the peak of the hit and see for example if there's a choke on cymbal ?
For those like me, I found a video of 64drums with other good explanations : https://m.youtube.com/watch?v=SX7K0veLMJQ
Is hold or decay the equivalent of mask time?
Justin from 65Drum, you mean. Yeah.
That's it, we Alesis user just got: Sens, Head/rim sens, tresh, xtalk, and retrig cancel.
You can listen to the audio output ... What those settings change.
eDrumIn: Gain for the two inputs, treshold can be adjusted, xtalk , and you ALWAYS can have a visible
"feedback" what those settings do. Great for all the settings... Fast and accurate. Because - you see, what you HAVE TO
set for a good trigger result!
What is the analog setting for the retrigger cancelation. On the eDrumIn we set the Scan, Hold and Decay to adequate values.
I could imagine that at an Alesis Module the scan time is fixed an they set the Hold/Decay with the retrigger cancel? So, the Snare was the first pad I used with the eDrumIn. Especially, due to the possibility to get a side stick triggering.
Not possible with my Millenium/Alesis/Medeli/Fame ...
AND those nice Bezier curves for velocity AND CC scaling... beautiful!
The advanced triggers section is also really helpful to me to better understand all this stuff.
In case someone is a trigger setting noob like me : https://www.roland.com/ca/support/by_pr ... 8498fe545/
Re: Bezier velocity curve
I was told that all those brands
Millenium
Medeli
Fame
XDrum
etc.
are using Alesis modules.
And I was told, that they have a huge latency of
8/9 ms, no advanced scan settings are and more or less not usable for a real musician.
Nevetheless I still use my Millenium module for the toms, effects, some cymbals. But xmas is near and have to discuss with my
chief financial officer to get a eDrumIn 10.
But I have to say:
The bigger problem are those bad samples... As we all know here, the physics of any drumpad and triggered cymbal is the same,
and together with a VST is quite they are quite usable to some friday night drums and beer fun, or a quick record of new drumparts.
Ok, you have less advanced scan settings but it works with they standard pads.
Millenium
Medeli
Fame
XDrum
etc.
are using Alesis modules.
And I was told, that they have a huge latency of
8/9 ms, no advanced scan settings are and more or less not usable for a real musician.
Nevetheless I still use my Millenium module for the toms, effects, some cymbals. But xmas is near and have to discuss with my
chief financial officer to get a eDrumIn 10.
But I have to say:
The bigger problem are those bad samples... As we all know here, the physics of any drumpad and triggered cymbal is the same,
and together with a VST is quite they are quite usable to some friday night drums and beer fun, or a quick record of new drumparts.
Ok, you have less advanced scan settings but it works with they standard pads.