delay using HF sensor system from eobody, nobody??
Hello Dear List,
We are using eobody HF and we try to trigger percussion sounds.
We would like to know if there is a delay over 50ms which is inherent to the system? We mesured 68ms as an average value using timer.
Did anyone of you tried with this system or with another one and did you achieve to get something "playable"?
The data treatments are reduced to the minimum, this means just having a peak detection.
Thank you for commenting,
I’m using an old LaKitchen Kroonde. I receive datas over Ethernet (thru OSC) every ±5ms. What type of analyse do you do? Maybe a patch would help!
What kind of sensors are you using? Some sensors (especially ultrasonic sensors) can have slow response (like 50ms).
We are triggering percussive samples in live. The band bought eobody HF sensor before they went into delaying troubles and called me.
We have piezo sensor like http://www.sparkfun.com/products/10293.
The only treatment we are doing is detecting peak velocity and sending a noteout message to trigger samples in live.
We use that patch picked up at interfaceZ website.
We don’t have any answer from eowave till now .
I have 2 wise boxes…if you say that Kroonde brings you down to 5ms i’ll give a try to my boxes. I never used them with piezo sensors…back to soldering…
----------begin_max5_patcher---------- 774.3ocyX1saaBCEG+ZxSgkulFYi4yosq2CvtbZZBHtIdALQfYKaU8ce3CPS Zaf.SDuzJYHFGy+yOe9vNOsxBmTbjWgQe.8Ujk0SqrrftzcX08YKbd7wzr3J XXXI+WEI+.a29HE+nB5NOdOWVn38O3wBopR7Gt9gTm0jttk04BYFWAyEqqyC wpzcB41uWxSUsZgR7Z9NHluu9hWnt0grlf9V22QrAdsMR4AlK9zrWTq5mdmt da6R86C714F+XVQrBa2eyKyoVyx3bXX3OKxxPeIVVg0O74UqzM1SDRoE44bo 5cTRUJ1tkW1XqnLwOOAqxsIsZinMzSMzyr3oPT5HDM..ZDLuA9iBT1kAJYw4 z.NS0xCwo6QgAHBdgr9Hvfib0W7iF05oyzcRHAmI8kafqz.HRGq0njkJbKpM ZCB5bGGOj+yNGGhmumgyU8L7fKdNiY5NQW1zoC4YbK7GRpUpBIdl9+NsFFkA YU75aunUNSiLIVtswPWtE3zcMyHeoB7ACmxfJHdzQ8rurgyFb009lG6WmmvK 6kUx1zhrhx9BEg9M+EXew6lPcilRQUowYP2j0QyDqc4HZoKK3cXc2aD6fU0N i+WoL9NsCxqIP.wKLz9h2c96XnL1cdtlJwUEOCQWprVst09fCMyaL2ZuYVNC nh8sI40.jQrPTg0RkPHXmMZvt+LyxY1p6e7SKW8sVlPgc7wbGiIA20LQgD5+ Wz5Bt.ObG83EgyrrvYkDL9tBSpS2yUKDhbfz59Pq6noXtG1Wz.D4gEMLJB1+ DiLFLnj65vnTUlPtratJ55mZvgYxnHXn3F67s+zFfMn6+0bqpntLs+M2eFPD 8k23FdkRHiUhlMde1fbe0f1I1rgKO+nP4hMGJZjdmHFXOxyRSjonIhY0zU4D 4NjSDixI8IGutlnFUS9SPRftM2RmNKwU0TnQozTV37mGjX9q8rQgs+fCr96M vpoYyM3MQxcesVRMaxpvIj+L59KsfYKxLAE4YTEELkr4FUQTxDjTfQkT3Ti1 9WkTyGdd0egB2+wg -----------end_max5_patcher-----------
So we have an answer from eowave.
They say it’s at least a delay of 16ms.
So the bottle neck is somewhere else. May be in the set of live???
I will try tomorrow morning on my computer!
I’ll give some news after.
If anybody has an idea from where we could get such a latency?