sync-ing a phasor~
this is probably a wood for the trees thing, but how do I start a phasor~ from 0. every time I play a note or whatever ? the sync input of the saw~ is not to be found on the phasor~, but that’s what I need.
or am I being dense ?
phasor~’s second inlet?
Centre de Recherches et de Formation Musicales de Wallonie asbl
i hang my head in shame BUT
can anyone explain the difference, if there is one, between the phase input of phasor~ and the sync input of saw~, and while we’re at it, the difference between phase and duty cycle ?
‘d be much obliged
phase is a particular appearance or state in a regularly recurring cycle of changes
duty cycle is the high portion in the cycle of a pulse wave
it takes all of us
the tri~ and rect~ objects both have ‘duty cycle’ inputs, and all three of
‘saw’, ‘rect’, and ‘tri’ have a sync input. It’s important to keep aware of
duty cycle for ‘rect~’ changes the relative amount of time that the pulse is
up versus down. for ‘tri~’, at 0.5, you get an isoceles triangle wave, and
as you change the duty cycle, the relative amount of time that the wave
spends going up versus down changes, so that at a duty cycle 0 or 1 the wave
is a saw wave, and between 0. see the manual entry on triangle~.
as far as the difference between the phase input on phasor and the sync
input on saw~, one practical (if perhaps obvious) difference is that phasor~
takes a float-only input versus the signal-only input of saw~. taken from
saw~ entry in manual: "When the control signal crosses from below 0.5 to
above 0.5, the oscillator resets itself." This is equivalent to sending a
’0′ message to phasor – when phasor receives ’0′, it resets itself.
So in some ways, the ‘phase’ inlet of phasor~ is more flexible, but it is
subject to command processing timing restrictions, hence can’t be used to
crate traditional sync effects.
As far as your first question is concerned, if your events are triggered by
a command rather than a signal, the sending a ’0′ to phasor~ would
accomplish the task.