Retrigger and MinScan (an other equivalent parameters)
Posted: Sun Oct 05, 2008 10:03 am
Hi dmitri, I have been reading Roland modules manuals. I have found interesting info on which are the default values Roland takes for the retrigger and minscan equivalents in megadrum.
Roland modules have a "Scan Time" parameter (the time a signal is watched till the module decides to trigger it). For all pads they default it to 2.0ms. In megadrum you set MinScan to 20 (2ms) so that parameter is fine.
The other parameter is "Mask Time" (since a signal is trigger, it is the time that lasts till it start sampling again). The megadrum equivalent is the missnamed Retrigger. In Roland modules "Mask Time" is set to a default value of 4ms.
The case is that in megadrum I haven't been able to find out which is the relationship between values and real time.
Could you explain me that relationship? To set megadrum retrigger time to 4 ms, which is the value I have to set in the screen?
Thanks
PD: in roland modules there is a third parameter: Retrigger Cancel. As I have read this parameter is a bit more advanced processing. It inhibit triggering fluctuations in a decreasing wave. If the decreasing wave suddenly increases a bit its amplitude and then follows decreasing again, the module doesn't let that fluctuation to be considered a hit in the pad
PD2: the last parameter of a roland module is Xtalk cancel. I don't know which is the megadrum equivalent, maybe a combination of Xtalk and DynLevel
PARTS OF ROLAND MANUALS:
Scan time:
Since the rise time of the trigger signal waveform may differ
slightly depending on the characteristics of each pad or
acoustic drum trigger (drum pickup), you may notice that
identical hits (velocity) may produce sound at different
volumes. If this occurs, you can adjust the “Scan Time” so that
your way of playing can be detected more precisely.
Mask Time:
Once a pad has been hit, any additional trigger
signals occurring within the specified “Mask Time” (0–64
msec) will be ignored.
Retrigger cancel:
Important if you are using acoustic drum triggers. Such
triggers can produce altered waveforms
This occurs in particular at the decaying edge of the
waveform. Retrigger Cancel detects such distortion in and
prevents retriggering from occurring.
Roland modules have a "Scan Time" parameter (the time a signal is watched till the module decides to trigger it). For all pads they default it to 2.0ms. In megadrum you set MinScan to 20 (2ms) so that parameter is fine.
The other parameter is "Mask Time" (since a signal is trigger, it is the time that lasts till it start sampling again). The megadrum equivalent is the missnamed Retrigger. In Roland modules "Mask Time" is set to a default value of 4ms.
The case is that in megadrum I haven't been able to find out which is the relationship between values and real time.
Could you explain me that relationship? To set megadrum retrigger time to 4 ms, which is the value I have to set in the screen?
Thanks
PD: in roland modules there is a third parameter: Retrigger Cancel. As I have read this parameter is a bit more advanced processing. It inhibit triggering fluctuations in a decreasing wave. If the decreasing wave suddenly increases a bit its amplitude and then follows decreasing again, the module doesn't let that fluctuation to be considered a hit in the pad
PD2: the last parameter of a roland module is Xtalk cancel. I don't know which is the megadrum equivalent, maybe a combination of Xtalk and DynLevel
PARTS OF ROLAND MANUALS:
Scan time:
Since the rise time of the trigger signal waveform may differ
slightly depending on the characteristics of each pad or
acoustic drum trigger (drum pickup), you may notice that
identical hits (velocity) may produce sound at different
volumes. If this occurs, you can adjust the “Scan Time” so that
your way of playing can be detected more precisely.
Mask Time:
Once a pad has been hit, any additional trigger
signals occurring within the specified “Mask Time” (0–64
msec) will be ignored.
Retrigger cancel:
Important if you are using acoustic drum triggers. Such
triggers can produce altered waveforms
This occurs in particular at the decaying edge of the
waveform. Retrigger Cancel detects such distortion in and
prevents retriggering from occurring.