[PD] Rewriting a unified phasor / metro object for reading tables
Ivica Ico Bukvic
ico at vt.edu
Thu May 9 03:09:19 CEST 2013
Assuming you want a pulse in non-signal domain, you could use disis_phasor~
(see http://l2ork.music.vt.edu/main/?page_id=56 for download links) which
outputs a bang every time ramp is crossed. This is only accurate to the
nearest sigvs size (by default 64 bytes) as there is no guarantee that you
will get a msg interrupt exactly at the time ramp has crossed.
From: pd-list-bounces at iem.at [mailto:pd-list-bounces at iem.at] On Behalf Of Ed
Sent: Wednesday, May 08, 2013 5:00 PM
To: PD List; pddev
Subject: [PD] Rewriting a unified phasor / metro object for reading tables
I'm rewriting phasor~ and unifying it with metro so that a pulse is
generated from the boundaries of each ramp - so that bars of music can be
read using tabread~ objects with a sample-accurate metro.
I'm sure someone will say this can already be done, but it has to be dropped
into the Ninja Jamm patch, so there isn't really time to rewrite the rest of
I don't fully understand the way phasor~ wraps, but I have the object firing
out bar numbers correctly. I'm putting clocks in for 16ths and 24ths of the
beat, initiated on each wrap. I need to minimise CPU, so what I want to know
Does phasor~ always start from 0 and go to 1, i.e. is there always a signal
value of 0 at the start of the ramp and a signal value of 1 at the end? As I
write this, my common sense tells me it should be "yes" but I want to make
sure. I suppose I should just try it really...
Ninja Jamm - a revolutionary new musix remix app from Ninja Tune and Seeper,
for iPhone and iPad
Gemnotes-0.2: Live music notation for Pure Data, now with dynamics!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list