julien breval

fw-pluggo-filtergraph-saving-problem

i seem to remember having similar issues a while ago...

the trick (for me) was to control filtergraph via other max gui objects, which work fine in the pattr world. filtergraph just didnt seem to work, so i ended up using it in display mode just so the user can get some visual feedback.

not really a clean solution, more an easy way round the problem.

That's what I did too. In the final patch there are two filtergraph with two

cascaded filter each, so I have to use 12 sliders to control the parameters.

These sliders can then be saved and loaded with [pp]. The main problem of this

solution is the following: when you edit the filtergraph directly, the

> the trick (for me) was to control filtergraph via other max gui objects,

> which work fine in the pattr world. filtergraph just didnt seem to work, so i

> ended up using it in display mode just so the user can get some visual

> not really a clean solution, more an easy way round the problem.

That's what I did too. In the final patch there are two filtergraph with two
cascaded filter each, so I have to use 12 sliders to control the parameters.
These sliders can then be saved and loaded with [pp]. The main problem of this
solution is the following: when you edit the filtergraph directly, the
parameters are not saved.

> the trick (for me) was to control filtergraph via other max gui objects,
> which work fine in the pattr world. filtergraph just didnt seem to work, so i
> ended up using it in display mode just so the user can get some visual
> feedback.
>
> not really a clean solution, more an easy way round the problem.
>
> j
>

maybe not made my explanation quite clear enough...

dont use filtergraph~ for the controls, set it to display mode then send it coeffs through filtercoeffs~. it then just provides the user with some visual feedback, but no control.

not quite sure wot the scenario would be if u had more than one filter (cascade~) ...

That's more or less what I did, though not using filtercoeff~. In this project I

wanted to use filtergraph~ as *saved* control too, unfortunately this doesn't

seem to be possible yet (see in Pluggo 3.6). To sum up, there are 12 more

sliders in the GUI that are both unwanted and unhandy here, but at least

> maybe not made my explanation quite clear enough...

> dont use filtergraph~ for the controls, set it to display mode then send it

> coeffs through filtercoeffs~. it then just provides the user with some visual

> not quite sure wot the scenario would be if u had more than one filter

That's more or less what I did, though not using filtercoeff~. In this project I
wanted to use filtergraph~ as *saved* control too, unfortunately this doesn't
seem to be possible yet (see in Pluggo 3.6). To sum up, there are 12 more
sliders in the GUI that are both unwanted and unhandy here, but at least
everything works.

> maybe not made my explanation quite clear enough...
>
> dont use filtergraph~ for the controls, set it to display mode then send it
> coeffs through filtercoeffs~. it then just provides the user with some visual
> feedback, but no control.
>
> not quite sure wot the scenario would be if u had more than one filter
> (cascade~) ...


I think that the problem might be that whenever one of the pp send 

something to filtergraph~ it cause it to return output of freq, q and 

gain, thereby overwriting the other pp objects that were about to be 

See if the patch below helps you further. It use two filtergraph~ 

objects. One is used for display and user interaction only, while the 

other one is calculating actual coefficients, and is hidden from the 

user. For the first one gain freq and Q is updated using set messages.

> I have some problems for saving and loading the [filtergraph~] shape inside a

> plugin. I finally tried the patch that D. Grosse describes on this page:

http://www.creativesynth.com/MAXMSP/001-SynthBuildingMSP/sbm_08.html

> I'm working on Windows XP with Max 4.5.7 so instead of downloading the *.sit

> file I made a "dummy" version of this patch that contains only this :

> - the [pp] objects 1 to 4 with the same arguments

> - the |capture $1( and |recall $1( system

> * If I open it as a Max patch, saving and loading with 'capture' and 'recall'

> works normally for creating some "factory presets"

> * Building the *.dll plugin works correctly

> * When I load the plugin to either Cubase or to the [vst~] object inside Max,

> loading a "factory preset" only affects the [umenu] : the cutoff, level and

> quality factor are displayed correctly in the "Parameters" GUI but in the

> "Interface" GUI the filtergraph is not modified. 0ther Max UI objects that I

> tried work normally inside plugins. What's the problem here ?

I think that the problem might be that whenever one of the pp send 
something to filtergraph~ it cause it to return output of freq, q and 
gain, thereby overwriting the other pp objects that were about to be 
sent new values to it.

See if the patch below helps you further. It use two filtergraph~ 
objects. One is used for display and user interaction only, while the 
other one is calculating actual coefficients, and is hidden from the 
user. For the first one gain freq and Q is updated using set messages.

julien breval wrote:
> Hello,
>
> I have some problems for saving and loading the [filtergraph~] shape inside a
> plugin. I finally tried the patch that D. Grosse describes on this page:
> http://www.creativesynth.com/MAXMSP/001-SynthBuildingMSP/sbm_08.html
>
> I'm working on Windows XP with Max 4.5.7 so instead of downloading the *.sit
> file I made a "dummy" version of this patch that contains only this :
> - the [filtergraph~]
> - the [umenu]
> - the [pp] objects 1 to 4 with the same arguments
> - the |capture $1( and |recall $1( system
>
> (behaviour)
> * If I open it as a Max patch, saving and loading with 'capture' and 'recall'
> works normally for creating some "factory presets"
> * Building the *.dll plugin works correctly
> * When I load the plugin to either Cubase or to the [vst~] object inside Max,
> loading a "factory preset" only affects the [umenu] : the cutoff, level and
> quality factor are displayed correctly in the "Parameters" GUI but in the
> "Interface" GUI the filtergraph is not modified. 0ther Max UI objects that I
> tried work normally inside plugins. What's the problem here ?
>
> Regards,
>
> Julien Breval
>


I recently ran into this same issue with my own lcd interface. Some 

parameters would trigger other parameters in order to cause a redraw 

in lcd. It worked fine in max, but those that were triggered by a pp1 

preset change stuck at 0. I was able to fix this (at least for DP) by 

rearranging the pp number order. I doubt this is an option for filter 

graph, however. Just pitching in for completeness' sake.

On Jul 28, 2006, at 1:22 PM, Trond Lossius wrote:

> I think that the problem might be that whenever one of the pp send 

> something to filtergraph~ it cause it to return output of freq, q 

> and gain, thereby overwriting the other pp objects that were about 

> See if the patch below helps you further. It use two filtergraph~ 

> objects. One is used for display and user interaction only, while 

> the other one is calculating actual coefficients, and is hidden 

> from the user. For the first one gain freq and Q is updated using 

I recently ran into this same issue with my own lcd interface. Some  
parameters would trigger other parameters in order to cause a redraw  
in lcd. It worked fine in max, but those that were triggered by a pp1  
preset change stuck at 0. I was able to fix this (at least for DP) by  
rearranging the pp number order. I doubt this is an option for filter  
graph, however. Just pitching in for completeness' sake.

> Hi,
>
> I think that the problem might be that whenever one of the pp send  
> something to filtergraph~ it cause it to return output of freq, q  
> and gain, thereby overwriting the other pp objects that were about  
> to be sent new values to it.
>
> See if the patch below helps you further. It use two filtergraph~  
> objects. One is used for display and user interaction only, while  
> the other one is calculating actual coefficients, and is hidden  
> from the user. For the first one gain freq and Q is updated using  
> set messages.
>
> Best,
> Trond

On Jul 28, 2006, at 8:22 PM, Trond Lossius wrote:

strangely, looking at this patch i find that the second filtergraph's 

q is contrained to 1.0 or less...? in fact looking at the message 

boxes being sent from both graphs, they aren't the same at all....? 

but the inspectors for both look the same. am i missing something?

Jonathan Segel -- 4014 Brookdale Ave. Oakland, CA 94619

On Jul 28, 2006, at 8:22 PM, Trond Lossius wrote:
> See if the patch below helps you further. It use two filtergraph~  
> objects. One is used for display and user interaction only, while  
> the other one is calculating actual coefficients, and is hidden  
> from the user. For the first one gain freq and Q is updated using  
> set messages.

strangely, looking at this patch i find that the second filtergraph's  
q is contrained to 1.0 or less...? in fact looking at the message  
boxes being sent from both graphs, they aren't the same at all....?  
but the inspectors for both look the same. am i missing something?

         Jonathan Segel  --  4014 Brookdale Ave. Oakland, CA 94619
                 MAGNETIC -- http://www.MagneticMotorworks.com


FW: [pluggo] filtergraph saving problem