Forums > MaxMSP

[bug report] meter~ in bpatcher

Oct 14 2009 | 10:27 am

Dear Developer,

I have found also bug with [meter~].
In a bpatcher /led.maxpat/ I setteld many [meter~].

In order to save CPU, I’ve combined one more bpatcher /switch.on/ between the inlet of /led.maxpat/ and the input of [meter~].
I replace the bpatch /switch.on/ with / by a script when I don’t want to see the level meter.

It does not work.
Even if the input of [meter~] is not connected with a audio signal, the [meter~] display the actual peaklevel.
If I load one extra [meter~] or an independent patch which includes a [meter~], the /led.maxpat/ works shortly correctly.

Can it be fixed in the next version?
Do you need my patch?


Oct 14 2009 | 10:37 am

It would help if you could post a patch. I wouldn’t call an abstraction led.maxpat, because led is also the name of an object.

Oct 14 2009 | 12:16 pm

I am sending a similar patch.
The complete version is so complicate to find the problem.
I rebuild the same code with subpatches.
The Problem [meter~] in bpatcher is the same one in the following codes.
I think it is a bug of max.
In the following code, the [meter~]s must show peak meter only after pressing t.
When we press r, the [meter~]s should not show the peak meter.
There are 6 subpatchers with same algorithm.
Only one patch works well.
The other subpartches does not work correctly.

— Pasted Max Patch, click to expand. —
Oct 14 2009 | 12:56 pm

Is it perhaps a general problem in MAX?
I have tried with an other way (I replaced meter~ by slider. Of course for it, I converted the peak value by peakamp~)
Regretfully I encounter the same problem.

Oct 14 2009 | 1:00 pm

You need to restart the DSP chain in order to make it work. In other word you can’t create signal connections on the fly.

Oct 14 2009 | 1:06 pm

I have restarted the dsp chain.
However, the problem remains.
It is bug. isn’t it?

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

Forums > MaxMSP