<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>On my side i would not say it is exactly trivial<br><br>JmAdrien</div><div><br>Le 16 déc. 2014 à 16:59, Jonathan Wilkes via Pd-list <<a href="mailto:pd-list@lists.iem.at">pd-list@lists.iem.at</a>> a écrit :<br><br></div><blockquote type="cite"><div><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div>That's definitely a workable solution.</div><div><br></div><div dir="ltr">But if it were truly "trivial" then [trigger] wouldn't exist.</div><div dir="ltr"><br></div><div dir="ltr">-Jonathan<br></div><div><span></span></div> <div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"> <font size="2" face="Arial"> On Tuesday, December 16, 2014 8:47 AM, IOhannes m zmölnig <<a href="mailto:zmoelnig@iem.at">zmoelnig@iem.at</a>> wrote:<br> </font> </div> <br><br> <div class="y_msg_container">On 12/15/2014 11:53 PM, Raphaël Ilias wrote:<br>> Ok, I get the trick, it seems similar to the one used to make delay line<br>> shorter than one block.<br>> However, I still feel that an object "give-me-RMS enveloppe-on-bang" (for<br>> the last N samples or blocks) would appear to me an easier way to handle<br>> this case.<br>> If it doesn't exist, I'll try to build something like this... one day !<br>> Many thanks !<br><br>oh, but that is just trivial:<br><br>messages and signals are always calculated one after each other (first<br>all messages; once they are done, signals are processed).<br><br>so an even easier way would be to use a latch ([f]) and [bang~]+[del 0]<br>to do the calculation in msg-domain.<br>[bang~] will output a bang before each signal block (or after; it really<br>will trigger a bang before the *next* signal block).<br>unfortunately, this bang can happen before or after the events sent out<br>by [env~], so we need to make sure to get an event *after* all [env~]s<br>have triggered.<br>the simplest way to achieve this is by using an additional [delay 0],<br>which will schedule an event at the same logical time NOW but after all<br>events already scheduled for NOW (e.g. those from [env~]).<br><br>see attached patch. (in the attached patch i wasn't able to trigger an<br>undesired behaviour without the [delay 0]; however i haven't tried hard<br>and i'm pretty sure that you *can*; thus you should use [del 0])<br><br><br>mfgadsr<br>IOhannes<br>_______________________________________________<br><a href="" class="removed-link" ymailto="mailto:Pd-list@lists.iem.at">Pd-list@lists.iem.at</a> mailing list<br>UNSUBSCRIBE and account-management -> <a href="" class="removed-link" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br><br><br></div> </div> </div> </div> </div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span><a href="mailto:Pd-list@lists.iem.at">Pd-list@lists.iem.at</a> mailing list</span><br><span>UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list">http://lists.puredata.info/listinfo/pd-list</a></span><br></div></blockquote></body></html>