[bug report] meter~ in bpatcher

prko's icon

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 /switch.off/ 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?

Best,
prko

Emmanuel Jourdan's icon

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.

prko's icon

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.

Max Patch
Copy patch and select New From Clipboard in Max.

prko's icon

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.

Emmanuel Jourdan's icon

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.

prko's icon

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