Steve Meyer

Partial solution using [latch] and [go.ramp2trig]:

comment

toggle

message

button

click~

live.scope~

gen~

latch

param

go.ramp2trig

phasor~

Given a continuously running phasor signal in the first/left inlet, I want to send the [gen~] patch an impulse to the second/right inlet which then follows the phasor signal for the 

 complete cycle and then automatically stops by returning to outputting a signal of 0 after one full phasor ramp has completed.

simple method to follow full cycles by toggling. I cannot work out how to automatically return the signal to 0.

Given a continuously running phasor signal in the first/left inlet, I want to send the [gen~] patch an impulse to the second/right inlet which then follows the phasor signal for the next complete cycle and then automatically stops by returning to outputting a signal of 0 after one full phasor ramp has completed.
I have worked out a very simple method to follow full cycles by toggling. I cannot work out how to automatically return the signal to 0.

Partial solution using [latch] and [go.ramp2trig]:
 
Given a continuously running phasor signal in the first/left inlet, I want to send the ... 

follow-mimic-duplicate-a-phasor-ramp-for-single-cycle-in-gen~

Your patch is missing "go.ramptotrig" and is there a specific reason you want this done in gen otherwise this seems to do the job?

<Edit> bang/press "prob 0" first after opening the patch in max

Your patch is missing "go.ramptotrig" and is there a specific reason you want this done in gen otherwise this seems to do the job?



<Edit> bang/press "prob 0" first after opening the patch in max

Thanks for sharing this, your version is a great reminder to be clever with the existing objects. The way I described this too myself (one shot phasor) blocked me from thinking in terms of subdividing and just using 1. Definitely saving your version in my examples folder for future reference!

The [go.ramp2trig] object is part of the package that accompanies the 

book. It simply produces triggers for the start/wrap around point of each ramp cycle.

My personal impetus for using gen~ is just because then I leave open the possibility to wire this into the other abstractions from the book, namely the unit shapers from chapter 3.

Eventually I also worked out a gen~ codebox solution. Since the go.* objects are not universally available, here's the screenshot.

image.png

The [go.ramp2trig] object is part of the package that accompanies the Generating Sound & Organizing Time book. It simply produces triggers for the start/wrap around point of each ramp cycle.

Follow / Mimic / Duplicate a Phasor Ramp for Single Cycle in gen~