@ddw_music said:

I made a concrete example -- with scores!

which one exactly do you mean?

@oid said:

@porres No help file, usage notes in asStream.pd, this thread is the documentation.

You see, I'm interested in this thread, I suggested that it would be created. I'm interested in the problem and how to make it work in Pd. I read the thread. This that you're sharing is not enough for me. I get that you may be satisfied and that you worked a lot and just about as much as you care on this, but I just wanted to make this clear. Ok, I know, I could do more of my homework, but I'm born and bred in Pd-land, all this just sounds way too complicated and like explaining 'snow' to me, who's also born and bred in a tropical country (I was at the beach yesterday by the way), so more help would be appreciated.

I have brought myself into such Pd x SC challenge other times, it's not the first time that things don't get too conclusive. I hear that it's impossible to do something "x", or too hard, and I hear about complex programming paradigms, and then it comes down to a simple solution like using [value]. My idea is to maybe try and expand Pd to improve it and open it up to what some people that come from elsewhere struggle with, and maybe offer a new object in my ELSE library... but all I'm getting so far from this thread is that you can share the index of an array with [value] in multiple subpatches or abstractions.

I was interested in studying this abstraction and see if maybe I could add it if I really got what it did and what it is for, but for now it's just quite abstract and over my head.

cheers

@oid said:

Added some usage notes in the patch

don't see it, where are the help files?

Also thought of [v]

@ddw_music said:

If your primary frame of reference is patching, then this is going to seem a bit vague or weird.

Give us a working patch in SuperCollider with an example, not too complicated thoufh

I guess I'll have to build it out in Pd for this to make any sense, but I can't do it right now.

I could build it too, but give us a patch that actually makes sound please. Again, try to be as minimal as you can

If I get it, you got one sequence and 3 independent playing from this sequence. I can envision a simple [clone] with 3 instances...

I gotta say I'm kinda lost

for a compiled external solution, see else/receiver

@ddw_music said:

anArray.do { |item| ... some operations... } vs

Well, if you're gonna use Vanilla objects, live's definitely gonna be harder, but I say life's too short to stick with Vanilla. Being someone who is about to reach 600 objects in his library soon, you may assume what my view is. Pd with just the vanilla objects is simply not a complete set of tools for computer music, nor enough... I don't doubt that. Pd Vanilla is simply the bare minimum at best. But even so, you can build a list iteration object with your patch above just fine and use it as an object. Or use [else/iterate] and [else/loop] like I said....

A concrete weakness of patching is when you have a
stateful object that needs to be accessed in multiple places.

I don't think I know what you mean here, really. How is this not like using [value]? Or the "send" message to "float". Anyway, I bet one can think of an external solution for this. I'd like to try it if I get it. I also think of [else/retrieve]...

Anyway, your examples are not clear to me, but the discussion interest me. I wanna get what is deal with recursiveness, for instance, but hey, we're hijacking the thread

Feature request for sfload: provide file statistics
(sample rate, number of frames etc.) upon completion.

new version already does that

I wouldn't trust doing that on the fly.

no, Pd is not for Live Coding (something else i don't care for)

Maybe in a different thread...

sure, go ahead please

@oid said:

I really hate doing documentation.

It's not easy and sometimes it's quite the nightmare. I don't know why I like it

Miller is working on this, check it out

"To Pd announce:

A very preliminary version (0.1) of a VST3 plugin named PureVST is
available on msp.ucsd.edu/tools/purevst . As the name suggests, it runs
Pd within a VST host such as your favorite DAW.

I'm releasing it, so far, as source code and as a packaged VST3 plug-in
for MacOS (Apple silicon) . It compiles fine for linux and (I think)
for MacOS/Intel - somebody brave might want to see if it can work on
Microsoft Windows too

I'm sure there will be plenty of problems/questions/comments. Perhaps
for now it's appropriate to write these to the Pd mailing list, although
it might someday be worth setting up a different forum for that.

cheers
Miller"