filtergraph~ and pattr

yes, set $1 for each of the output boxes should work, these set the float boxes that [pattr] binds to. You can then hide the float boxes if all you want to use is the filtergraph~ part of the UI. If you have [line] ramps these can go into the float boxes too, etc. It's a case where you actually want to have an extra UI-type object, to give [pattr] a bridge to an object it doesn't directly support.

Try using [mtr] with filtergraph~ too, that's an easy wiring-together. The [mtr] has its own stack-overflow protection built-in, so that incoming messages (when recording) don't get sent out, while when playing back, messages don't get accepted in.

thanks for the very good advices ( [mtr] is too new to me )
would you be kind enough to provide a quick example
on 1 in/out of filtergraph~
for the [line] and the [mtr]

I am pretty new to max and it will avoid me a long tester on [mtr]
the pattr stuff is ok don't worry

thanks

just follow the [mtr] help file, the inlets and outlets correspond to playback of a number of "tracks". all you have to do is wire the same [filtergraph~] values like frequency through the [mtr] and then back into the [filtergraph~]. Or you can get fancier and have floats before and after, which is where [pattr] comes in.

muting individual tracks is easy, so you can block playback of whichever parameters you want and get UI control back for that element: playback the Q and the gain but manually move the frequency, or whatever combination during playback.

Hello Maa,

I don't see how [mtr] will solve your pattr problem but anyway.

Here's the way to go to store filtergraph~s freq/gain/q values :

léo

mtr is not related, but I learned a new object

I took the best of both examples, and extend

somebody complete to avoid clicks (smooth the change) ?

> I want to use filtergraph~ settings with pattr but filter graph can't be used directly

Unless I completely misunderstand, this appears not to be true.

even better
work with autpopattr too
how ro know if an object is compatible with pattr or not ?

> how ro know if an object is compatible with pattr or not ?

Don't know if there's a complete list, but easiest is just to try. All ui objects are candidates.

two more thing for the v6 wish list
a field in the documentation
obj parameter which expose in the inspector some properties like this one