ah yeah, sorry... i had assumed you meant different things on both sides of the crossfade.
so yeah, you could just use one patch for the guts. here, i'm attaching a little patch to show a possibility for xfade with sssad (you'll have to incorporate this into sssad yourself, but hopefully won't be too tricky) On Tue, May 14, 2013 at 4:21 PM, JF <sainti...@yahoo.com> 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. > > Cheers, > John. > >
xfade-sssad.pd
Description: Binary data
_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
