[PD-dev] Default value for unconnected signal input, or connection detection in an external

Antoine Rousseau antoine at metalu.net
Thu Mar 19 19:55:30 CET 2020


>
> This is pretty adventurous :-)


admittedly  ;-)
but it works quite well since ... 2001! (although I remember I had to help
fixing one or two "bugs" in Pd to make it possible...)

Antoine


Le jeu. 19 mars 2020 à 19:38, Christof Ressi <info at christofressi.com> a
écrit :

> This is pretty adventurous :-)
> On 19.03.2020 19:17, Antoine Rousseau wrote:
>
>
> also you can have a look to moonlib/dinlet~, which (I think) does what you
> want.
> source is there:
> https://github.com/MetaluNet/moonlib/blob/externals/moonlib/dinlet%7E.c
>
>
>
>
>
> Le jeu. 19 mars 2020 à 16:41, x nor <x37v.alex at gmail.com> a écrit :
>
>> Ahh okay, these are not main signal inputs (the first inlet is used for
>> something already).. and I want to just use `m_pd.h` so I guess I'll add
>> the creation arguments.
>> Good to know about CLASS_MAINSIGNALIN float setting for the first inlet
>> though!
>> Thanks!
>> -Alex
>>
>> On Thu, Mar 19, 2020 at 8:28 AM Christof Ressi <info at christofressi.com>
>> wrote:
>>
>>> Hi,
>>>
>>> for the first inlet you can simply set the float field passed to
>>> CLASS_MAINSIGNALIN. This is actually done by many Pd objects, e.g.
>>> "phasor~", "osc~", etc.
>>>
>>> For other inlets it's a bit more tricky. If you're ok with including
>>> "m_imp.h", you can use "obj_findsignalscalar" which returns a pointer
>>> to the scalar value for the Nth signal inlet.
>>>
>>> Christof
>>> On 19.03.2020 16:16, x nor wrote:
>>>
>>> Hey Christof and dev list,
>>>
>>> Christof,
>>> I think it was you that did the work that allowed for a default value
>>> for unconnected [inlet~] in the inlet_features branch that didn't get
>>> merged?
>>>
>>> I'm wondering, is there a way to do that with externals as is without
>>> modifying the pure data source? Either that or a way to detect connectivity?
>>>
>>> I want to provide some audio rate controls to an external I'm writing
>>> but not *require* them for operation. 0 isn't a good default for some of
>>> these (amp or frequency multiplication).
>>> If its not possible to provide defaults or detect connectivity (so i can
>>> provide my own defaults) I'll probably just provide optional creation args
>>> to opt in to these audio rate parameters.. but that just ends up being a
>>> lot more work so I figured I'd ask first :)
>>>
>>> Thanks,
>>> Alex
>>>
>>> _______________________________________________
>> Pd-dev mailing list
>> Pd-dev at lists.iem.at
>> https://lists.puredata.info/listinfo/pd-dev
>>
>
> _______________________________________________
> Pd-dev mailing listPd-dev at lists.iem.athttps://lists.puredata.info/listinfo/pd-dev
>
> _______________________________________________
> Pd-dev mailing list
> Pd-dev at lists.iem.at
> https://lists.puredata.info/listinfo/pd-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20200319/3b8031fc/attachment.html>


More information about the Pd-dev mailing list