Something weird happening with the open hihat/hi hat closing thing.
As an example, in Drumset Editor load default acoustic kit. You'll see that when hi hat is selected (highlighted), open hi hat is ticked so that open hi hat will be closed by hi hat (all good, understand that).
Now, in Rhythms, load base rhythms/dance/complex 01. In the 'additional' page turn off auto breaks, then choose a beat that has open hi hat in it (from F on the keyboard up).
Hit play...sometimes the open hats play, sometimes they don't, and this happens in a regular cycle. As far as I can see, this has nothing to do with velocities, layers, probability, cymbal variation mode, single instance, single sample etc etc.
Is this a bug, and something to do with the open hi hat and hi hat hits being at the same point in time, and the compatibility logic not quite working? Just guessing in the dark, I'm not a programmer, just a normal person (who loves MDrummer).
MDrummer bug?
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14325 posts since 15 Mar, 2008 from Czech republic
Actually this is kind of intentional - usually there is some "humanization" going on and the dance rhythms are created for the dance drumsets, which usually don't use hihat closing at all. There are often closed and open hihats at the same position, so it depends on which is first, but technically less than picoseconds matter here 
. If you disable humanization (and potentially inaccuracy for each note), you may get stable results, but easier is probably to disable the closing if you don't want it.
. If you disable humanization (and potentially inaccuracy for each note), you may get stable results, but easier is probably to disable the closing if you don't want it.-
- KVRian
- Topic Starter
- 975 posts since 10 Jan, 2007 from London
I guess my interest in this is academic rather than practical, because if I wanted 'closing' I wouldn't put Hihat and Open Hihat at exactly the same point in time. I can see what you mean re humanization giving unpredictable (and desirable) results, but the interesting thing here is that if all humanization parameters are disabled the results are not stable (athough there is a pattern to them). By the way, I've discovered that the overall humanization parameter has no bearing on this matter (it must be downstream ?) but the relevant parameter is 'inaccuracy' (which seems actually to always displace the note earlier rather than later). At the risk of being really tedious, if you set up this very simple experiment: one bar (loop) of 2/4..Hihat on beats 1 and 2..Open Hihat on beats 1 and 2..Open Hihat set to be closed by Hihat...inaccuracy of all notes zero..hit play...both drums play for one bar then only Hihat in the next bar and so on in that cycle. I'm just wondering why MDrummer deals with this (un-natural) situation in this way (and I wonder why he doesn't crash). I guess the answer is in some kind of mathematics that I wouldn't understand, and the pursuit of an answer is not practical anyway. If I was a lot younger maybe I'd get into mathematics and programming!