Messages per Month
|Subject:||Re: [PD] [PD-announce] metastudio 3 CRITICAL update|
|From:||Ed Kelly (morp...@yahoo.co.uk)|
|Date:||Aug 20, 2009 9:06:00 am|
Apologies for not being clearer. svf_fl~ is an abstraction within the metastudio
package, just a wrapped graph-on-parent version of svf~ with a GUI but not an
external in its own right. The reason I made this point is that I was using
bsaylor/svf~ in the metastudio previously, which is a different external and
causes PD to crash.
So don't panic, and carry on as before :> But please feel free to check out the
metstudio at http://sharktracks.co.uk/puredata
--- On Tue, 18/8/09, Phil Stone <pkst...@ucdavis.edu> wrote:
From: Phil Stone <pkst...@ucdavis.edu> Subject: Re: [PD] [PD-announce] metastudio 3 CRITICAL update To: pd-l...@iem.at Date: Tuesday, 18 August, 2009, 5:40 PM I'm sorry if I missed it in an earlier thread, Ed, but what is this svf_f1~ that you speak of? I've been using svf~ (many instances at once, in fact) for a couple of years without crashes, though sometimes the CPU climbs a bit when no sound is being made -- but again, no crashes.
Phil Stone pkstonemusic.com
Ed Kelly wrote:
I've updated the metastudio packages with the old svf~
external in the drumsynths (clinok~, clinoker~ and fmf_perc~) and svf_fl~.
The bsaylor/svf~ external has problems - denormals
cause the filter to max out the CPU and will crash any patch mid-preformance. I also found this problem with moog~ (in moog_fl~) so watch out for it crashing your patch! If it does, I recommend switching to svf_fl~ for a dynamic filter.
This is a critical update, so if you're using metastudio then head over to http://sharktracks.co.uk/puredata And save yourself some future embarrassment!