On Tue, May 14, 2013 at 12:21:10AM -0700, JF wrote: > > it's been a long time since i looked at rj, but from memory it uses > > something similar to sssad for statesaving, doesn't it? So, you assign > > keys to each of your abstractions and save according to those keys, yeah? > > > in that case, i would just bundle my entire 'scene' into a bigger parent > > abstraction, and use a $0 (or similar) prefix to all my state saving keys > > > so that state loading would be local only to that parent, and not to the > > > other channel's parent. > > Thanks! > > I presume this approach would mean having two copies of the 'meat' of the > patch running side by side? > > Correct me if I'm wrong. > > I'm hoping to only have one copy of the guts running and have the > crossfading done to the parameters. As my machine is getting older now. > > I'm not looking to crossfade audio at the end. This will be a midi note > and CC generating patch for my synths and samplers to record and to play > live with.
However don't rule out audio for speeding up the crossfade itself. Attached is a very fast way of interpolating two 64-element parameter lists using audio operations in a subpacth, that is suspended after each interpolation run using a [switch~] object. Drive this at your desired metro-speed and you have a nice and tidy interpolation system. By using a different block size in the subpatch and bigger tables, you can also extend this to bigger preset list sizes. And it still is very fast - much faster than if you would use a message based approach which involves list unpacking and so on. Ciao -- Frank Barknecht _ ______footils.org__
fast-interpolate.pd
Description: application/puredata
_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list