cudnylon

Trying to decide which method has the most accuracy/flexibility. Is the global transport working in the scheduler or signal domain? The two methods I'm trying to decide between are:

1) send bpm value to [transport] with multiple [phasor~ @lock 1] objects running sequencers/lfos/etc, changing the speed of each [phasor~] using tempo-relative time values.

2) send bpm value (divided by 240.) to [phasor~] which is connected to multiple [rate~ @sync lock] objects, changing the rate multiplier of [rate~] to control speed.

there might be a third option here as well, which is [transport] to [phasor~ 4n @lock 1] to multiple [rate~ @sync lock] objects, but that all depends on the accuracy of [transport] as a master clock. Unfortunately, I'm having a hard time finding information on [transport], specifically how it operates and it's relationship to [phasor~].

1) send bpm value to [transport] with multiple [phasor~ @lock 1] objects running sequencers/lfos/etc, changing the speed of each [phasor~] using tempo-relative time values.
2) send bpm value (divided by 240.) to [phasor~] which is connected to multiple [rate~ @sync lock] objects, changing the rate multiplier of [rate~] to control speed.

there might be a third option here as well, which is [transport] to [phasor~ 4n @lock 1] to multiple [rate~ @sync lock] objects, but that all depends on the accuracy of [transport] as a master clock. Unfortunately, I'm having a hard time finding information on [transport], specifically how it operates and it's relationship to [phasor~].


master-transport-to-phasors-or-master-phasor-to-rates-for-global-clock

Did you ever get any kind of reply for this question? I am contimplating the same problem.

Master transport to phasor~'s or Master phasor~ to rate~'s for global clock?