2018-03-07 15:42 GMT-03:00 Alexandre Torres Porres :
> by the way, here's an issue on github
>
> https://github.com/pure-data/pure-data/issues/259
>
which had been posted on this thread already, haha, sorry
___
Pd-list@lists.iem.at mailing list
UNSUBSCR
by the way, here's an issue on github
https://github.com/pure-data/pure-data/issues/259
I say it'd also be good to include this idea of using a float argument to
set a default value, but it's also interesting if this could be set via an
inlet as well, and now it seems all such enhancements would
how about an inlet~ object that has a secondary outlet for control data?
anybody done that as an external?
well, that's something we could maybe just include in vanilla's inlet, but
if there's any work torwards that direction, I can give a look and try
doing a Pull Request
cheers
2018-03-07 9:5
Long time ago I implemented [dinlet~] (in moonlib) , aka "default inlet~":
when the dinlet~ isn't connected, then it reverts to its default (constant)
signal value, which is given as an argument.
Maybe reading the code could give you some ideas:
https://github.com/MetaluNet/moonlib/blob/externals/m
I put up a related 'enhancement' PR a bit ago for [inlet~]
https://github.com/pure-data/pure-data/issues/259
I dug into the ugen graph code a bit and got lost trying to implement it
myself..
On Tue, Mar 6, 2018 at 9:22 AM, Miller Puckette wrote:
> This too is on my (almost infinitely long) doli
This too is on my (almost infinitely long) dolist... to somehow extend the
"dsp" message to allow objects to find out whether there are signals connected
or not (and perhaps also to be able to deal with unequal-sized arrays somehow).
Main reason I think this is needed is so that objects like "vcf~
the object doesn't know but the ugen graph algorithm does. if it sees that a
signal inlet is not connected it creates a new signal and adds a scalar copy
routine to the DSP chain.
the scalar value is stored in the inletunion in struct _inlet (m_obj.c) and
it's updated whenever you send a float
