Forums > MaxMSP

delay using HF sensor system from eobody, nobody??

May 23, 2012 | 9:59 am

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,
cheers,
Hubert


May 23, 2012 | 12:40 pm

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).

p


May 24, 2012 | 8:08 am

Hello Patrick,
Thank you.
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 .

Thank you
Cheers
Hubert

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…

– Pasted Max Patch, click to expand. –

May 24, 2012 | 9:21 am

Hello,
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?
thank you
cheers
Hubert


Viewing 4 posts - 1 through 4 (of 4 total)