phiol

here is a simple patch demonstrating my attempt to do a acceleration detector. It does work very well. I've searched the forum and the max objects list for an external that would do this but did not find anything. 

It's obvious that in order to accomplish this you need time based objects but I only know of [thresh][quickthresh][timer][clocker].

any suggestions would be greatly appreciated.

here is a simple patch demonstrating my attempt to do a acceleration detector. It does work very well. I've searched the forum and the max objects list for an external that would do this but did not find anything. 
It's obvious that in order to accomplish this you need time based objects but I only know of [thresh][quickthresh][timer][clocker].

any suggestions would be greatly appreciated. 

acceleration-recognition

I meant it doesn't work very well. Damn I should really reread myself more often. sorry about that.

Again, Since it DOESN'T work very well, would any of you have any suggestions.

I meant it doesn't work very well. Damn I should really reread myself more often. sorry about that. 

Again, Since it DOESN'T work very well, would any of you have any suggestions. 

Not quite sure what's going on your subpatch, will need to investigate further.

I just love simplified patching like that!

Not quite sure what's going on your subpatch, will need to investigate further. 

I just love simplified patching like that! 

It's a bit of a hack, but it works. Technically velocity = change in distance / time and acceleration = change in velocity / time. Since the values are always updated at a constant rate, I've just pulled time out of the equations and simplified velocity to change in distance and acceleration to change in velocity. So, a bit of a hack, but one that's proved useful for me.

After having a 2nd deeper look into you "gap calculator patch". My question is;for calculating gaps in between did you choose [bucket] because it does this (by mistake or not) anyways ??

If you look in the help file example; when you quickly change values on input slider, bucket creates a gap in it's output.

that's what your creating , a (calculate the gap between 2 values @ the rate of 50ms)

After having a 2nd deeper look into you "gap calculator patch". My question is;for calculating gaps in between did you choose [bucket] because it does this (by mistake or not) anyways ?? 

If you look in the help file example; when you quickly change values on input slider, bucket creates a gap in it's output. 

that's what your creating , a (calculate the gap between 2 values @ the rate of 50ms) 

here is a patch that illustrates what I mean with no metro @ all.

Bucket simply outputs the previous input, so its "speed" is entirely dependent on the rate of the data fed into it. Your second patch (the one without the metro) works because the slider object doesn't interpolate between values. Hook up [print] to the output of a slider, mouse around a little and you'll soon see plenty of "gaps" between values. Someone who knows much more than I do about how Max interacts with the OS can probably explain this behavior.

The advantage of using a metro to bang out incoming data at a constant rate is simply so you don't have to calculate the time between successive values in order to find velocity or acceleration.

Bucket simply outputs the previous input, so its "speed" is entirely dependent on the rate of the data fed into it. Your second patch (the one without the metro) works because the slider object doesn't interpolate between values. Hook up [print] to the output of a slider, mouse around a little and you'll soon see plenty of "gaps" between values. Someone who knows much more than I do about how Max interacts with the OS can probably explain this behavior. 

The advantage of using a metro to bang out incoming data at a constant rate is simply so you don't have to calculate the time between successive values in order to find velocity or acceleration.


thanks for the reply. Yes so my point stands that one can called the accel based on the gap/space between values. So if having a [number box] that outputs to slowly

I pressume it's totally based on scheduler speed/Overdrive/computer speed etc...

thanks again, for your little patch. It's very handy for interactive stuff

thanks for the reply. Yes so my point stands that one can called the accel based on the gap/space between values. So if having a [number box] that outputs to slowly 

I pressume it's totally based on scheduler speed/Overdrive/computer speed etc... 

thanks again, for your little patch. It's very handy for interactive stuff  

acceleration recognition