analyzer~ problems

Dec 11, 2007 at 9:08pm

analyzer~ problems

i am running max/msp 4.6 on a macbook pro. i have the correct objects for my computer in my cycling 74 folder, but more than half the time if i try to use the analyzer~ object it appears as a bogus object and the max window says “warning! object set to 44.1 khz.”

yet occasionally the object will work just fine.

anyone else have this problem?

thanks

#34983
Dec 11, 2007 at 10:28pm

Quote: fmmw wrote on Tue, 11 December 2007 13:08
—————————————————-
> i am running max/msp 4.6 on a macbook pro. i have the correct objects for my computer in my cycling 74 folder, but more than half the time if i try to use the analyzer~ object it appears as a bogus object and the max window says “warning! object set to 44.1 khz.”
>
> yet occasionally the object will work just fine.
>
> anyone else have this problem?
>
> thanks
—————————————————-

That’s an odd one. Is it version 1.3.1? Do you have something else called analyzer~ in your search path? That warning isn’t printed by the analyzer~ object.

mz

#118729
Dec 11, 2007 at 11:22pm

analyzer~ (as well as the other Tristan Jehan way cool objects) occasionally gives up on me, and produces minimum values.

Only solved by restarting Max.

Don’t know if this is a fiddle~ thing or not (haven’t tested it very thoroughly).

(Using the latest Intel versions)

#118730
Dec 12, 2007 at 1:07am

Quote: fmmw wrote on Tue, 11 December 2007 13:08
—————————————————-
> i am running max/msp 4.6 on a macbook pro. i have the correct objects for my computer in my cycling 74 folder, but more than half the time if i try to use the analyzer~ object it appears as a bogus object and the max window says “warning! object set to 44.1 khz.”
>
> yet occasionally the object will work just fine.
>
> anyone else have this problem?
>
> thanks
—————————————————-

OK, I lied. Actually, I searched for your warning, not “WARNING !!! Object set for 44.1 KHz only”

So the obvious question, is your sample rate set to 44.1 KHz? This actually how the object is programmed now; if the sample rate isn’t 44.1, then the new method returns 0.

That’s not so suave, maybe I can improve it. Ideally, it would be happy with any sample rate, and react properly if the rate changed.

mz

#118731
Dec 12, 2007 at 1:12am

> That’s an odd one. Is it version 1.3.1? Do you have something
> else called analyzer~ in your search path? That warning isn’t
> printed by the analyzer~ object.

actually it is the analyzer~ object, and i’ve seen it quite a bit. it
generates an error if you try to instantiate it in a patch when your
DSP is set to anything but 44.1k. however after instantiating it,
i’ve changed to 48k and the object still works and gives good
results. perhaps some legacy code from fiddle~ days which only worked
at 44.1k…if memory serves me right.

david

#118732
Dec 12, 2007 at 2:07am

Quote: David Beaudry wrote on Tue, 11 December 2007 17:12
—————————————————-

>
> actually it is the analyzer~ object, and i’ve seen it quite a bit. it
> generates an error if you try to instantiate it in a patch when your
> DSP is set to anything but 44.1k. however after instantiating it,
> i’ve changed to 48k and the object still works and gives good
> results.
—————————————————-

Luckily, the original author did not have it check the sample rate after instantiation.

So, here is analyzer~ 1.4:

http://www.mikezed.com/technology/analyzer~1.4.zip

It checks the sample rate whenever the DSP chain is built, and then does the right thing with that information. It seems to work for me. Let me know if there are any problems. If not, I’ll propagate this improvement through the rest of the Jehan Objects and pass them along to him for distribution.

Keep in mind that this is an FFT-base object, and the FFT is defined in samples. Changing the sample rate will have implications on the frequency resolution of the FFT.

mz

#118733
Dec 12, 2007 at 2:19am

I personally would love a version that would work at other sample rates.
thanks!
david

> That’s not so suave, maybe I can improve it. Ideally, it would be
> happy with any sample rate, and react properly if the rate changed.
>
> mz

#118734
Dec 12, 2007 at 2:33am

Yeah!
Fanfare required indeed! ;)
Thanks so much for doing this.
Best,
David

On Dec 11, 2007, at 6:07 PM, mzed wrote:

>
> Quote: David Beaudry wrote on Tue, 11 December 2007 17:12
> —————————————————-
>
>>
>> actually it is the analyzer~ object, and i’ve seen it quite a bit. it
>> generates an error if you try to instantiate it in a patch when your
>> DSP is set to anything but 44.1k. however after instantiating it,
>> i’ve changed to 48k and the object still works and gives good
>> results.
> —————————————————-
>
> Luckily, the original author did not have it check the sample rate
> after instantiation.
>
> So, here is analyzer~ 1.4:
>
> http://www.mikezed.com/technology/analyzer~1.4.zip
>
>

>
> It checks the sample rate whenever the DSP chain is built, and then
> does the right thing with that information. It seems to work for
> me. Let me know if there are any problems. If not, I’ll propagate
> this improvement through the rest of the Jehan Objects and pass
> them along to him for distribution.
>
> Keep in mind that this is an FFT-base object, and the FFT is
> defined in samples. Changing the sample rate will have
> implications on the frequency resolution of the FFT.
>
> mz

#118735

You must be logged in to reply to this topic.