Help with drumgizmo UI

Moderators: MattKingUSA, khz, muldjord, deva

Post Reply
hdr
Established Member
Posts: 138
Joined: Sun Feb 03, 2019 1:47 pm
Has thanked: 1 time

Help with drumgizmo UI

Post by hdr »

Hello,

can someone explain the meaning of the controls in the dg ui?
What is the effect the different ones like attack, release, stddev, tightness, timing regain, laid back-ness?
I also don't really get what the visualizer wants to visualize :)
What effect does it have if I increase or decrease the disk streming/cache limit?
I couldn't find any information on the dg website.

In this tutorial https://www.youtube.com/watch?v=PFOUnyH3irU the humanizer is turned off and the velocity is altered manually in muse. Why? Doesn't the humanizer change the velocity of the individual beats to make them not all sound the same?

What if I change the velocity of the beats in the midi file AND activate the humanizer in drumgizmo? Is it 'humanized' twice then?
OS: Debian 10 DAW: Ardour 6.2
User avatar
deva
Established Member
Posts: 285
Joined: Sun Oct 23, 2016 10:15 am
Has thanked: 3 times
Been thanked: 31 times
Contact:

Re: Help with drumgizmo UI

Post by deva »

The humanisation controls are split into two groups:
- Velocity humanisation, which modifies the velocities of the input notes.
- Timing humanisation, which moves the note position in time.
On top of that the StdDev knob is used for the sample randomisation, which, the greater the values of the knob, allows the engine to select samples with a power further away from the input velocity. StdDev is visualised by the width of the horizontal bar. A broader bar means that the sample randomiser is allowed to select samples further away from the centerpoint (the center line)

The velocity and timing humanisations sections can be disabled entirely (as is done in the video you are referring) but the StdDev is always active, since it is an integral part of the way the engine works.

Velocity humanisation tries to emulate the way a drummer plays when playing fast single notes on the same drum. The first hit is hard and then the following hits will gradually get more and more soft. Attack controls how quick this slope will fall and the Release will control how quickly the drummer regains power. In the visualiser this is indicated by the vertical movement of the horizontal line (power is on the Y-axis).

Timing humanisation tries to emulate how the "internal" perceived metronome of a drummer can drift compared to the perfect metronome. At each hit the drummers internal metronome is allowed to drift slightly back or forward. How much is controlled by Tightness. Greater value means less drift. How quickly the timing is catching up to the perfect metronome is controlled by Timing Regain. the timing is visualised by the vertical line and the breadth of it indicates how untight the engine is.
The last knob in the timing controls can be used to set laid-backness. It moves the reference metronome point slightly back or forward and makes the drummer play up-beat or back on the beat.

Enabling the timing humaniser will add some latency to the plugin in order to make it possible to move notes forward in time. So when using it with for example a midi drumkit this should be disabled.

Changing the input velocities directly in the miditrack will change the input velocity of the engine which will then take it into account when doing its randomisation and velocity-humanisation. In other words they are accumulative.
Post Reply