| Hi Alfred,
I think you are confusing the James’s. James Harkins is a composer and educator. James McCartney is the initial creator of SuperCollider, who open sourced the application in 2002. James McCartney is no longer part of the mailing lists, and while I believe everyone here respects and appreciates what he gave the computer music community, I don’t believe any one individual should have the ability to shutter a community that is over 20 years old and has many significant contributors.
If you feel shuttering the group is appropriate, you can remove yourself. I hope you don’t want to do that, but I also don’t think it is needed for you to hope that all of us lose this list or community (or SuperCollider) as a resource.
Best,
Josh
gives his own interpretation of how modern society is structured: whether actively or passively, consciously or unconsciously, he makes choices in this regard. He may be conservative or he may subject himself to continual renewal; or he may strive for a revolutionary, historical or social palingenesis." - Luigi Nono
*/
@james, does your work at Apple keep you busy with anything besides CoreAudio?
Alfred.
Please consider shuttering this group. that's awesome James, thanks so much for the help
I've ended up with something that always does
inval = <object>.embedInStream; (since it seems .embedInStream is a synonym for .yield?) -- when object is an event it works as I would expect, but if it's another nested routine it still works as long as on the lowest level it's still doing inval = <some event>.embedInStream
thankyou list
-adam
Thx James.
On Tue, Mar 12, 2019 at 10:16 AM <jamshark70@xxxxxxxxx> wrote:
>
> On Tue, Mar 12, 2019 at 9:30 PM <adam.a.juraszek@xxxxxxxxxxxxxx> wrote:
> > however just taking the duration values from the routine like so restores the normal nodeproxy functionality:
> > ~x = (instrument: \X, \buf, someBuffer);
> > ~kick[0] = Pbindf(~x, \dur, r.collect(_.dur));
> >
> > so it seems something about the routine returning events bypasses the normal nodeproxy roles and immediately plays the events 'outside' the nodeproxy context
>
> Ah, there's the clue.
>
> Routines receive an 'inval'. For events, you should modify the inval
> and yield it:
>
> (
> r = Routine { |inval|
> loop {
> ... do stuff to inval...
> inval = inval.yield;
> }
> }
> )
>
> You should (and this is a finer point that is not strongly documented)
> *not* simply do "myBrandNewEvent.yield". The above, with inval, is
> necessary.
>
> I'd guess the NodeProxy is passing the output bus into the
> pattern/routine using 'inval'. If your routine ignores inval, then you
> are ignoring the incoming parameters.
>
> hjh
>
> _______________________________________________
> sc-users mailing list
>
> info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
> archive: https://listarc.bham.ac.uk/marchives/sc-users/
> search: https://listarc.bham.ac.uk/lists/sc-users/search/
_______________________________________________
sc-users mailing list
info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/
|