sequencersampler

The method that I'm using to derive triggers from signals is susceptible to inaccuracies with higher speed signals and can't lock onto 0. What objects should I look towards to improve the accuracy and flexibility of this method:

The method that I'm using to derive triggers from signals is susceptible to inaccuracies with higher speed signals and can't lock onto 0.  What objects should I look towards to improve the accuracy and flexibility of this method:


how-do-i-use-a-specific-point-of-a-signal-to-trigger-an-event-method-attached

I didn.t check, my patch has the same problem as yours. [edge~] is your friend

Thanks for the suggestion. [edge~] is great for working with 0, but what if the user needs to derive a trigger from a non-zero value with high accuracy?

Here's the problem with the [edge~] solution:

Is there any object that can lock onto 0 and a specific value? I'd reason that if an object can lock onto .52 (for example) it could also lock onto 0. like [edge~].

Thanks for the suggestion.  [edge~] is great for working with 0, but what if the user needs to derive a trigger from a non-zero value with high accuracy?

Is there any object that can lock onto 0 and a specific value?  I'd reason that if an object can lock onto .52 (for example) it could also lock onto 0. like [edge~].


i had tried using [-~] earlier but was monitoring the incorrect output of [edge~].

@JESSE - great solution, thank you.
i had tried using [-~] earlier but was monitoring the incorrect output of [edge~].  

Away from computer and can't see the patch, but it sounds like this could be the classic "trying to detect the beginning of a phasor~/square wave question."

Given the range of possible floating point values, it is unlikely that an exact value will be seen from an oscillator each cycle. (Phasor~ does not always return to 0!) Consequently, it's usually more effective to look for a transition to a range of values, which is why

Another way is to look for a big jump: with a phasor~, delta~ -> abs~ -> >=~ 0.5 will work for any phasor below half the sampling rate an will only output a single on value, which is handy for triggering things at signal rate.

Given the range of possible floating point values, it is unlikely that an exact value will be seen from an oscillator each cycle. (Phasor~ does not always return to 0!) Consequently, it's usually more effective to look for a transition to a range of values, which is why 

Another way is to look for a big jump: with a phasor~, delta~ -> abs~ -> >=~ 0.5 will work for any phasor below half the sampling rate an will only output a single on value, which is handy for triggering things at signal rate.


Makes sense. Thanks Peter. I have been working to narrow the selection method to the smallest range possible. There's nothing wrong with 

Makes sense.  Thanks Peter.  I have been working to narrow the selection method to the smallest range possible.  There's nothing wrong with 


how do I use a specific point of a signal to trigger an event [method attached]