Scan time less than 2ms request
Posted: Sun Jun 16, 2024 5:04 am
Hi
Is there a reason for not allowing scan time less than 2ms? I am fighting for fractions of milliseconds because I play through PA sytem and speakers themselves add some latency so every single ms is golden for me. On my Roland TD-25 scantime settings I am succesfull with some pads setting scantime as low as 0,3 - 0,6 ms. I bought expensive RME card because I chase ms. Total measured latency from hitting pad to output from RME soundcard in Addictive Drums 2 (measured with microphone placed at drumhead and compared to output of soundcard to see difference in time response) with scantime at 0,0 (yes ! very playable although not 100% reliable) on PDX100 pad was..... 2.9ms. But extendig scantime to 0.6 makes it consistent with total laency 3.5ms . But with EDrumin whatever I do - connect through physical MIDI in port in my RME or going throug USB Midi of Edrumin, or even triggering TD25 through MIDI cable from EDRUMIN - any of these and other scenarios I can never go lower that 5ms (I also have 2box and ddrum4, also tried various combos) which makes EDRUMIN useless for me, because PA is adding another 2 ms and fast rolls feel sluggish. Is there any reason for not allowing less than 2ms scantime at the risk of mistriggering? It is probably super-easy feature to implement. Make it screen go red that mistriggering is possible for those less aware people if that's why its not possible less than 2 ms.
Is there a reason for not allowing scan time less than 2ms? I am fighting for fractions of milliseconds because I play through PA sytem and speakers themselves add some latency so every single ms is golden for me. On my Roland TD-25 scantime settings I am succesfull with some pads setting scantime as low as 0,3 - 0,6 ms. I bought expensive RME card because I chase ms. Total measured latency from hitting pad to output from RME soundcard in Addictive Drums 2 (measured with microphone placed at drumhead and compared to output of soundcard to see difference in time response) with scantime at 0,0 (yes ! very playable although not 100% reliable) on PDX100 pad was..... 2.9ms. But extendig scantime to 0.6 makes it consistent with total laency 3.5ms . But with EDrumin whatever I do - connect through physical MIDI in port in my RME or going throug USB Midi of Edrumin, or even triggering TD25 through MIDI cable from EDRUMIN - any of these and other scenarios I can never go lower that 5ms (I also have 2box and ddrum4, also tried various combos) which makes EDRUMIN useless for me, because PA is adding another 2 ms and fast rolls feel sluggish. Is there any reason for not allowing less than 2ms scantime at the risk of mistriggering? It is probably super-easy feature to implement. Make it screen go red that mistriggering is possible for those less aware people if that's why its not possible less than 2 ms.