Ricardo

I'm making a Jamoma module of the CNMAT analyzer~object. In the discription it says that if your using more then one objects at a time you should change the delay argument, so that you don't have multiple FFT happening at the same time.

My question is: Is it possible to change this with a message? Or du you have to put it in as an argument in the object? The same goes for the other arguments as well.

Is there a way to dynamically change these arguments if you pack it in the Jamoma modular frame work?

Hi there.
I'm making a Jamoma module of the CNMAT analyzer~object. In the discription it says that if your using more then one objects at a time you should change the delay argument, so that you don't have multiple FFT happening at the same time. 

My question is: Is it possible to change this with a message? Or du you have to put it in as an argument in the object? The same goes for the other arguments as well. 

Is there a way to dynamically change these arguments if you pack it in the Jamoma modular frame work?


cnmats-analyzer-object

i believe there is only an [analyser~] object by tristan jehan.

http://web.media.mit.edu/~tristan/maxmsp.html

This is the one that comes with the CNMAT bundle. I think the only way to solve my problem is to script it some way. Thanks anyway.

Problem solved :) scripted the solution :)

seven years later i am using it (the original, third party max 4 object by tj) for the first time myself and running into the same problem.

scripting (or loading different wraps of the object, aka set "initial delay" to #1) seems to be the only two solutions.

seven years later i am using it (the original, third party max 4 object by tj) for the first time myself and running into the same problem.

scripting (or loading different wraps of the object, aka set "initial delay" to #1) seems to be the only two solutions.

I'm having this problem too but don't know how to get around it. Would you please detail your scripting solution?

[list script newdefault scriptingname 100 100 analyzer~ 0. 0. 0. 0. 0. 0. 0.]

under circumstances you need to recompile:

- for max 7 (i think) there is still only a 32 bit version.

- in max 4 you need to set the vectorsize to 64 for this object to work properly, best done using poly~.

- in max os 9 there is no "script newdefault", so you have to script it via a bpatcher-patch. (that just for those who might have read this thread already back in 2002. :D )

[loadbang]
[list script newdefault scriptingname 100 100 analyzer~ 0. 0. 0. 0. 0. 0. 0.]
[thispatcher]

under circumstances you need to recompile:

[t 1 0]
[dac~]

 - for max 7 (i think) there is still only a 32 bit version.

 - in max 4 you need to set the vectorsize to 64 for this object to work properly, best done using poly~.

 - in max os 9 there is no  "script newdefault", so you have to script it via a bpatcher-patch. (that just for those who might have read this thread already back in 2002. :D )

There is a 64bit version in the new distribution.

Which format are the 0. 0. 0. 0. 0. 0. 0. ?

@ Roman
There is a 64bit version in the new distribution.
Which format are the 0. 0. 0. 0. 0. 0. 0. ?


0. 0. 0. 0. 0. 0. 0. is where you enter the arguments you want to set it up with :)

 0. 0. 0. 0. 0. 0. 0.  is where you enter the arguments you want to set it up with :)

you mean f.e. @buffersize 2048 for the first 0. ?

yes of course, whatever you wish - including different vectordelays for different instances you create.

scriptingname (unique ID, you need that for the connect command to work, see thispatcher help)

then the arguments, just as you are writing them for the object when you create it manually.

newdefault  (creates an objectbox) 
scriptingname (unique ID, you need that for the connect command to work, see thispatcher help)
100 100 (position)
object~ (objects name)
then the arguments, just as you are writing them for the object when you create it manually.



(p.s. the objects you want to connect it to will also need to have a unique ID)

CNMAT's analyzer~ object