Jason Orri

Hi everyone, I have a idea which I cannot figure out how to impliment.

Basically, I want to be able to create a patch that will open a switch object when the frequency (the speed and amount) of incoming numbers goes above a certain threshold - this would then open the switch, however, as soon as it drops below that threshold number the switch closes the patch again...

I have had some basic muddling attempts and am unsure how I might measure the numbers coming so as to set a limit - or if there is something that will count the speed (frequency) of these incoming numbers...

It seems to me that measuring this could be done by counter (?) but i have no idea how as I don't want to 'count' up till a certain point ... If anyone could point me in the right direction this would be awesome.

Basically, I want to be able to create a patch that will open a switch object when the frequency (the speed and amount) of incoming numbers goes above a certain threshold - this would then open the switch, however, as soon as it drops below that threshold number the switch closes the patch again...
I have had some basic muddling attempts and am unsure how I might measure the numbers coming so as to set a limit - or if there is something that will count the speed (frequency) of these incoming numbers...

number-speed-gate

You could use [timer] to measure the interval of incoming numbers (ie. reciprocal of frequeny).

here is a quick example with [timer]. There is one slight bug here, when the patch is turned on the second time, [timer] outputs the time between the last output and the new session... easy enough to patch around though, but I will let you tinker with that one, I can't have all the fun here ;)

Funnily enough I started building a patch that does this the other day, I used:

[timer]->[if]->[counter]->[sel]->[switch]

Think about that and you should get some ideas ;-)

Funnily enough I started building a patch that does this the other day, I used: 

Think about that and you should get some ideas ;-)


Great ideas, thanks guys. I've had a go but there still seems a good few bugs....here's my patch

or connect your number stream to [t f f] (or [t i i]), connect each outlet to each inlet of [-]. This will give you the difference between successive numbers, the faster the number stream the higher the delta. Then add a [> whatever] -> [togedge] for your switch

Hi
an alternative:
search the forum for "delta";
or connect your number stream to [t f f] (or [t i i]), connect each outlet to each inlet of [-]. This will give you the difference between successive numbers, the faster the number stream the higher the delta. Then add a [> whatever] -> [togedge] for your switch

Thanks Brendan, I can't seem to get past getting a fool proof STOP or close of the switch as the higher number on the time often creates a new bang and opens the switches after its closed them....

I'll have a look at your most recent patch in the morning.

Can you post a patch that generates a typical sequence of your incoming numbers?

I think it would be helpful for finding a proper solution.

Can you post a patch that generates a typical sequence of your incoming numbers?
I think it would be helpful for finding a proper solution.


Sure, it's from a wii remote inputting data around 0.1 and -0.1 marks - the patch represents this as best as I could so you see without having a wii mote.

Sure, it's from a wii remote inputting data around 0.1 and -0.1 marks - the patch represents this as best as I could so you see without having a wii mote.
Thanks


So it seems the numbers arrive at constant speed but you want to do something depending on their *values* ?

Maybe you should try again explaining the goals of your project in more detail..

So it seems the numbers arrive at constant speed but you want to do something depending on their *values* ?
Maybe you should try again explaining the goals of your project in more detail..


Yes and no. Basically the numbers come in uniformly in the most part however there are times when a special event (the swinging of the wii remote's - and it's accelerometer) that I would like to map and create a way to open a path temporarily when this happens (so when 0.01 and -0.01 are crossed a higher amount of times in a shorter space of time - comparative to normal 'uniform' events/movements).

This may be the wrong way to do it but can't think of another approach...

Yes and no. Basically the numbers come in uniformly in the most part however there are times when a special event (the swinging of the wii remote's - and it's accelerometer) that I would like to map and create a way to open a path temporarily when this happens (so when 0.01 and -0.01 are crossed a higher amount of times in a shorter space of time - comparative to normal 'uniform' events/movements). 

Sorry to hijack this thread, but I this got me thinking about some things that would help in some projects I'll be working on in the near future.

I want to use incoming data (frequencies, etc...) to select different sound sources. In this example, I'm using the timing between metronome bangs and [if then else] to trigger them. It works except for the middle part [if ($i1 < 1000) || ($i1

Since I'm still relatively new to max, I also tend to make my patches overly difficult. So if you have any advice on how to do this with less stuff, please share.

@Aaron, you need to use "and" (&&) instead of "or" (||), because saying "$i1500" will be true for all numbers greater than 500. So one of these will always be true, hence you get 1's all the time.

You can also use [split] for these kinds of range-checks.

@seejayjames, Thanks! I honestly didn't even know what "||" meant.. was just doing my typical "jack stuff from the help files" technique.

I haven't messed with that object before.. seems like it will come in pretty handy.

On another note, is it just me or do some of the help files not seem as helpful as they were in max5? I can't think of a specific example off the top of my head, but it seems like some info that used to be in certain help files in max5 is no longer in max6...

@seejayjames, Thanks! I honestly didn't even know what "||" meant.. was just doing my typical "jack stuff from the help files" technique. 

I haven't messed with that object before.. seems like it will come in pretty handy. 

On another note, is it just me or do some of the help files not seem as helpful as they were in max5? I can't think of a specific example off the top of my head, but it seems like some info that used to be in certain help files in max5 is no longer in max6... 

Number SPEED gate