<div dir="ltr">ah yeah, sorry... i had assumed you meant different things on both sides of the crossfade. <div><br></div><div style>so yeah, you could just use one patch for the guts.</div><div style><br></div><div style>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)</div>
<div style><br></div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 14, 2013 at 4:21 PM, JF <span dir="ltr"><<a href="mailto:saintidle@yahoo.com" target="_blank">saintidle@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">> it's been a long time since i looked at rj, but from memory it uses<br>
> something similar to sssad for statesaving, doesn't it? So, you assign<br>
</div>> 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<br>
<div class="im">> 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.<br>
<br>
</div>Thanks!<br>
<br>
I presume this approach would mean having two copies of the 'meat' of the<br>
patch running side by side?<br>
<br>
Correct me if I'm wrong.<br>
<br>
I'm hoping to only have one copy of the guts running and have the<br>
crossfading done to the parameters. As my machine is getting older now.<br>
<br>
I'm not looking to crossfade audio at the end. This will be a midi note<br>
and CC generating patch for my synths and samplers to record and to play<br>
live with.<br>
<br>
Cheers,<br>
John.<br>
<br>
</blockquote></div><br></div>