brendan mccloskey

at the centre of my continuing experiments in granulation lies a single [phasor~] driving everything. I have a variety of typical grain parameters correctly implemented, except one: interonset time. This can be achieved using the [line~] object to "silence" a grain ramp at will, but I don't wish to deconstruct my entire engine. So, I've been experimenting with ways to impose quantized gaps in my central [phasor~] and the simplest seems to be to multiply the output of that phasor with a [rect~] oscillator. Works fine, when both oscillators are in sync at the same frequency. In order to vary the interonset time between ramps then the frequencies must differ by some function, but if I vary the [rect~] frequency then, pretty much as expected, it all goes tits up. I would like to retain the [phasor~] ramp integrity and vary the duration of silence between 0.-1. ramps somehow. It could well be that I've incorrectly implemented syncing.

[edit] example patch now includes phasor ---> dynamic pulsewidth

hi
at the centre of my continuing experiments in granulation lies a single [phasor~] driving everything. I have a variety of typical grain parameters correctly implemented, except one: interonset time. This can be achieved using the [line~] object to "silence" a grain ramp at will, but I don't wish to deconstruct my entire engine. So, I've been experimenting with ways to impose quantized gaps in my central [phasor~] and the simplest seems to be to multiply the output of that phasor with a [rect~] oscillator. Works fine, when both oscillators are in sync at the same frequency. In order to vary the interonset time between ramps then the frequencies must differ by some function, but if I vary the [rect~] frequency then, pretty much as expected, it all goes tits up. I would like to retain the [phasor~] ramp integrity and vary the duration of silence between 0.-1. ramps somehow. It could well be that I've incorrectly implemented syncing.
All donations gratefully received chums.

muting-phasor-almost-there

I'm just getting my head round gen~ but it's not too difficult to achieve what you want to do. Maybe there is a more efficient way but this is not too bad and you can set the sleep time to any factor of the frequency which could come in very useful in lots of situations....

Hey thanks very much for this, it will serve two purposes: solving my problem and encouraging me to learn [gen~].

FYI I placed a phasor-driven [sah~] outside to avoid interruptions during a ramp. No doubt this could also be achieved inside [gen~]......

Inside Gen you could put a sah on input 2 triggered by the history object. You'll need a trigger value somewhere above 0. and below 1. for the sah.

Inside Gen you could put a sah on input 2 triggered by the history object. You'll need a trigger value somewhere above 0. and  below 1. for the sah.


Here's another way - I struggled to get my head round this a while back when trying to make a Vosimish patch (for which a ramp down was required, which is actually a bit simpler),

Here's another way - I struggled to get my head round this a while back when trying to make a Vosimish patch (for which a ramp down was required, which is actually a bit simpler),
Cheers
Roger


What on earth is Vosimish? Polish aperitif??

Polish? Nie znam, nie piłem, chętnie spróbuję. ;)

Maybe it has something to do with Kaegi's VOSIM?

Polish? Nie znam, nie piłem, chętnie spróbuję. ;)
Maybe it has something to do with Kaegi's VOSIM?


now I have two equally elegant but very different approaches to mull over; if you compare the two you'll notice that leafcutter's solution doesn't subtract the 0. (silence/sleep) portion from the phasor's cycle time, i.e. the period of the 0. - 1. ramp remains unchanged. Not clearly stated I'm afraid, but I've just opened my 4th guinness....

And variant of GEN solution. A little simpler, i think.

here's something I figured out a while back. uses gen to generate the ramp, hope it's of use...

the first outlet is the ramp, the second is the gate

here's something I figured out a while back. uses gen to generate the ramp, hope it's of use...
the first outlet is the ramp, the second is the gate


Thanks everyone; MSP means there are numerous solutions to such a problem. I guess [gen~] means there are countless solutions!

I'm re-awakening this old thread, as I continue to try to find my own non-gen solution - I have no aversion to gen at all, just being bloody-minded - and I am able to mute my phasor for a period which is a function of its duration or frequency, using the [rate~] object. The attached patch shows how I have done this, demonstrates my poor maths skills, and probably also proves why gen is the only way to go!

Hi
I'm re-awakening this old thread, as I continue to try to find my own non-gen solution - I have no aversion to gen at all, just being bloody-minded - and I am able to mute my phasor for a period which is a function of its duration or frequency, using the [rate~] object. The attached patch shows how I have done this, demonstrates my poor maths skills, and probably also proves why gen is the only way to go!

all the solutions above are very ingenious too, leafcutter's especially

"muting" phasor~; almost there