Hi there peeps,

I'm building a basic granular synth type patch using [phasor~] and [tabread4~] to read an array.

What I want is to be able to have a bang go off every time the phasor hits zero... but I can't figue it out.

Any suggestions?

cheers

J

yes, hopefully it would ~ sounds like the right sort of thing, but where can I find it? doesn't seem to be in pd-extended's standard libraries.

Thanks Domien

for homemade [phasorshot~] use mod's example but instead of [metro] just use a bang object

On my pd-extended installation it's located in the extra/tof folder. I thought this was standard included in extended.

The tof library never loads properly for me after installing pd-extended.

To get it to be recognized i have to add the path manually -or- put "tof/" before the object name of all objects from the library.

For example: [phasorshot~] becomes [tof/phasorshot~]

I have started using the latter method because it makes it easier to share the patches with others or use with a fresh pd install.

Thanks guys ~ [tof/phasorshot~] works.

[phasorshot~] has a .dll extension in the tof folder, which probably explains why it's not recognised directly in pd.

Oops! having said that, it doesn't seems to be working... It recognizes [tof/phasorshot~] as an object but is not functioning ~ anything else I need to do?

Sorry, got it working now! Thanks for your help.

I've been comparing [phasorshot~] to [phasor~] when simultaneously modifying the frequency of the phasor and the length of samples that the output is multiplied by using a [samphold~] object (in order to speed up/slow down repeats without changing pitch).

There seem to be unwanted artifacts whilst modifying with [phasorshot~], but not with a [phasor~].

Anyone know why this might be?

freq is changed directly at the input, whilst sample length changes are only made at phase wrap around.

I want to be able to use phasorshot~ rather than phasor, but if it means additional artifacts, that puts me off.

I think there is a bug in [phasorshot~], at least in loop mode. Try sticking the output into a [tabwrite~] and look at it in an array. There's some ugly flat portions in it.