| Newsgroups |
gmane.comp.audio.supercollider.user |
| Message-ID |
<[email protected]> |
> However, it appears that that OutputProxy never makes it to the server
> side representation
Yes, as I said, it's not a "real" UGen. In sclang, OutputProxies are not
added as children to the UGen graph (see "addToSynth"), they only appear
as inputs to other UGens and are converted to "input-specs" (UGen index
+ output index) in the actual SynthDef file.
On 02.03.2021 15:11, [email protected] wrote:
>
>
> On Tue, 2 Mar 2021 at 14:24, <[email protected]
> <mailto:[email protected]>> wrote:
>
>> But in any case, it would help to know cases of multiout ugens
> There are quite a few multiout ugens. Just open the SC IDE, open
> the help for MultiOutUGen and click on "Subclasses".
>
>> Meaning, each UGen must have it's number of outputs specified
>> somewhere else
>
> The ".ar"/".kr" methods for multi-output UGens return an Array of
> "OutputProxy" instances (or a single "OutputProxy").
>
> Generally, UGens have a "source" and "outputIndex" method. For a
> regular single-output UGen, "source" always returns the UGen
> itself and "outputIndex" always returns 0. "OutputProxy" is a fake
> UGen where "source" returns the source UGen and "outputIndex"
> returns the desired output index.
>
> Christof
>
> Yes, when parsing .scsyndef files I could see the double input spec
> with a first index referring to the ugen and a second index referring
> to which output of that ugen.
> However, it appears that that OutputProxy never makes it to the server
> side representation, so I'm deducing it must be a client side thing,
> not dissimilar to what I had in mind.