<div dir="ltr"><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div>also you can have a look to moonlib/dinlet~, which (I think) does what you want.</div><div>source is there: <a href="https://github.com/MetaluNet/moonlib/blob/externals/moonlib/dinlet%7E.c">https://github.com/MetaluNet/moonlib/blob/externals/moonlib/dinlet%7E.c</a></div><div><br></div><div><br></div><div dir="ltr"><font face="arial, helvetica, sans-serif"></font><div dir="ltr"><font face="arial, helvetica, sans-serif"><br></font></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le jeu. 19 mars 2020 à 16:41, x nor <<a href="mailto:x37v.alex@gmail.com">x37v.alex@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>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.</div><div>Good to know about CLASS_MAINSIGNALIN float setting for the first inlet though!<br></div><div>Thanks!</div><div>-Alex<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 19, 2020 at 8:28 AM Christof Ressi <<a href="mailto:info@christofressi.com" target="_blank">info@christofressi.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Hi,</p>
<p>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. <br>
</p>
<p>For other inlets it's a bit more tricky. If you're ok with
including "m_imp.h", you can use <span style="color:rgb(0,0,0)">"obj_findsignalscalar"
which returns a pointer to the scalar value for the Nth signal
inlet.</span></p>
<p><span style="color:rgb(0,0,0)">Christof<br>
</span></p>
<div>On 19.03.2020 16:16, x nor wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hey Christof and dev list,<br>
</div>
<div><br>
</div>
<div>Christof,<br>
</div>
<div>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?</div>
<div><br>
</div>
<div>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?</div>
<div><br>
</div>
<div>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).</div>
<div>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 :)</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Alex<br>
</div>
</div>
</blockquote>
</div>
</blockquote></div>
_______________________________________________<br>
Pd-dev mailing list<br>
<a href="mailto:Pd-dev@lists.iem.at" target="_blank">Pd-dev@lists.iem.at</a><br>
<a href="https://lists.puredata.info/listinfo/pd-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/listinfo/pd-dev</a><br>
</blockquote></div>