interpolating filtergraph's filtertypes
I am trying to interpolate between different filtergraphs-filtertypes with a textobjects feeding another filtergraph with coefficients. it works – but not very well, because during interpolation, the first filtergraphs-params (freq, type – pattr aware) are banging the filtergraph-object to output its "non-interpolatet type" again… and interpolation is gone…
perhaps somebody has a more smarter/simpler solution?
here’s the test patch:
----------begin_max5_patcher---------- 1363.3ocyZssjahCD8YOeETT6iDW5BHf8s7cjJ0TXirMYwfCHRljTY91WcAv XarQdPiFO0TXiPHN8oacT2x7mmV3tp7EZsqy+57EmEK9ySKVHaRzvh1yW3tO 4k04I0xt4xJ2tMm55otTQy9rhbJSdMXaiYoxdVt5aexOXPOKaXm2UUSrecfp vfaVAy04qsW8PBa8trhsOWQWyTc.GFrD34ff.4G8Gc9p3V96SOIN3oosrpgw JKz1V.2osrJoX6MMFerzXvDSXLEzexQYGDYzWjOD2sIrdu0lxBVQxdI9b+bU VR9n1N5RaGGdaaWLx0Y+VNxPD2NtBkba5.n7sAxOff4wG6o00IaoWPHf4yFn .KvFQgfArQf7DXzajL1jWxg5cZ4iLG.BG2xQ2okywSBy0Si4HQsQCwCnASOG Y8NNJnNfkymfHiyO36MxvSIE5MshXWbBRRPwnYQPM6oEMclvORp5IAI1lM63 GdGzCbYPb.LJ7VKU3onpiDj35sqmowxHP4wvAAUcXlQ22NLtoY0GxS9k343I NjW9yCB9p67cYa2cRC7X5zKZnlUdnugCzj+qnjipgCZ8NZ9lSF0SaohVWVjn LZYCI44xGiYkGWh.AQXemOAV5Ch8wQNGaBtLBFEER3MEgPHRu6LOqfttrofc tXvab4lHKHv1traPWpDQx0hQevJrXhsUXCaEU8AlPgsY+JZkAnArYngVQhII AhRPHHJ3QhDP1kDZiDLDIL9Zsqx9dSR5q2I4PFIILrYzHpy1Vvep2hWhiU7h ZFxbSLk96zj0upqTH7JRgfogqxM52ezjtwhxrZ5qFHgRh07hPfpBKruQpuvX B9VOk51TEIlPu+.OqDJSWaEck7+7ulQ0M78ZXm1vsc2QCWWq0c6OLKO9cwp3 IlUIRDRlkKsl49AFKfr9h+crTrIBFtVNk7GGOWUm+A9NktHx2BoKBADktAZ. U8lSW7TY0SpzRDCdNCNLR0YXOlQrFxljF4RM216pN4Gzzm4HheSOKLyrUMLU MbK5IOd2TF+PYLfbn3Gh.RGR+XtvccdFsfcBPTOdY+DZestMkeybduFHhCI. 7X1I89vjFdIfBCz.9N3s0QumsY3xZnGaSFhFrjwXdQtrL2AQO2qstjtosN5t pH8NVYo2vF6pszqu3xityMUzu2VzVP7wlOZIv43MMl5Mv5ktolVgMg3sw1hv XayBD0hWPyW51vY1xXv4yNgVttVn4hPtRo.UbvIVT5ECrnDLvLzyjBZsEGgi MRIcBimllwFKtQIAZlsYaFDK13aLsV7qJviqZK42PyF4wbV4ja.twPayhbx3 TDiemjsQB71jkynUaqRNr60gzy5x7xpy1F7SngnKogqnae08eOOqVFGzKTei uz02oJZqaOKvs+RfDUF2QCxznPYym3L4kDpZsMUCOw+PutuDQhWhCCBwHtF3 RXbHDhDoYP7I7+DeCb0Ce3tEzCfaoMnMFLSuBbfWoUS.uDDiB7U4BhfjP+2A +w68dQBs1lX0taFS7ajKGAYU1m8tcHGQQ6mRV0kMUq6PQ26sgyQuaJO69rhD VVYwfNIdo.FzocYoozhg6M49rzCk7Xq9ePtQcc5hIgL8jXR7RZXQLgd.4oyd biioyHy2cdRWZBZMH4e5iabLYYVhnimCZULoCjNaVv6tP.TCLQrqmCnCMw6S n8XoXMgDwdPJTSHE7PILAsptjVh.hc71lg295fI6JVB0Yo2X6BIrNQSAOdYM cFvsBlfOXXRqoc1ESw5BIKpNoUHdjcUmzFSPq557mJgWj0illZRGFa8xBHSA IxC2bN7bhk3m72m9e3wVVpC -----------end_max5_patcher-----------
if I understand well, you should try and have a look a the subpatcher
called [p cascade] in the filtergraph’s help patch.
Since the svf~ object outputs the results
of lowpass/highpass/bandpass/notch filtering
simultaneously, why not use *it* and then
pattrize the *~ objects that handle the output
amplitudes for each filter output type? The
only thing there that might require rubbing
a few neurons together would be setting up the
three/fout-way crossfade [and no, there isn't a
single Max object that does N-way fades]. It’s
quick and dirty and sounds just fine.
I also thought on this possibility (and I’ve also build up a 5way crossfader for the wavesources)…
Using a svf~ with just graphical-feedback of filtergraph should be ok, does it?
By the way 2up-svf~ isn’t able to output it’s filterouts in parallel, or am I wrong?
I don’t use the filtergraph~ stuff unless
I’ve got no other choice, preferring to
*listen* to the filters and to map the
three or four faders’ worth of stuff I’d
use so it’s under my fingers instead of
eye candy on the screen. Your mileage
The plain old MSP svf~ object kicks out
parallel outputs from a single audio
input – see the help file – so it’s
perfect for morphery. Of course, if you
cannot live without eye candy, you can
use the more um… exotic outputs from
the filtergraph~ object to set things,
although they won’t be wildly useful
when morphing filtertypes.
yea, you’re right. I also once compared between filtergraph~/biquad and svf~ – liked svf~ much more… just get to much used to the graph-reference… it’s time to stop that now ;-)
by the way:
the 2up_svf~ Version doens’t support parallel filtertype-output
> perhaps somebody has a more smarter/simpler solution? here’s the test
Answering late, but the original question had not been answered:
Instead of the filter graph, store the coeffients in a pattr. Problem,
if you feed that back to the filtergraph for display, it will switch to
display mode and you can’t play with it easily anymore.
I guess Jeremy choose to store the type/freq/gain/Q values of a
filtergraph~ instead of the coefficients for this reason. In most cases
you would want to stay in edit mode if working with filtergraph.
My solution would use a second filtergraph~ only for displaying
purposes, but you can use transparency and "ignore clicks" to make it
into a nice userinterface. I switched on also "imitate analog flavour"
to make it sound better… I’d wonder how it compares sound wise with
svf~, for sure its way more flexible…
You could by the way also include the type/freq/gain/Q values into
pattr, but exclude them from interpolation, that way they would jump in
at the fixed preset points…