Closed for Company Meetings: Between September 18 (5pm PDT) and September 22 (12pm PDT), Support and Sales requests will be delayed. Only time-sensitive issues will be addressed during that time. Thanks for your patience.
> Thanks Peter,
> I've been trying to brush up on my signal domain chops and had
> managed to completely overlook the thresh~ object.
here is yet another solution using only standard objects.
i did this years ago for a project, before thresh~ came to live.
it's simplicity doesn't reflect the time it took me to come up with
That's a lovely elegant bit of patching volker and it's just the kind of thing i was hoping to see so thanks for sharing it.
There is a slight issue with it however. If the input changes abruptly from below to above the trigger say from 0-1 (as the output from phasor~ connected to >=~ object might) your abstraction will not trigger. I played about with introducing a one vector delay between the different sides of the signal input to the >=~ and =~ side to go from 0-1 and conversely having a delay in the
> There is a slight issue with it however. If the input changes
> abruptly from below to above the trigger say from 0-1 (as the
> output from phasor~ connected to >=~ object might) your abstraction
> will not trigger.
ah ja. you're right. [sah~] doesn't get retriggered.
originally this was intended for envelope-signals, i.e. heavily
lowpassed signals without sharp edges.
thats probably why the flaw never occred to me.
havn't used it since [thresh~] came along anyway.
so we might better let it rest in peace...