Re: [sc-users] two separate triggers > single counter value

[Daniel Mayer <daniel-mayer@xxxxxxxx>]

Am 19.12.2015 um 12:27 schrieb Ilya <ziblatilya@xxxxxxxxx>:

> ...but, as I have now added a reset argument to counter_two, I miss a reset
> argument for counter_one, otherwise sum_counter's value will 'jumps'
> sometimes (increase sum_counter in more then +1).

As I said, you have to tweak the sensitivity of the Amplitude ugen.
There's no 'perfect' sensitivity, it totally depends on attackTime and
releaseTime.
They determine how far you 'zoom' in and out from amplitude envelope
to waveform and back. Probably you want less sensitivity/response,
so raise these args. With default values it's likely that
one 'sound event' will cross the threshold several times,
which leads to the described multiple counts.

Watch the effect of changing these params
by plotting the Amplitude waveform of some of your input sources.

// evaluate and say something within 2 seconds

(
{ Amplitude.ar(SoundIn.ar()) }.plot(2);
{ Amplitude.ar(SoundIn.ar(), 0.3, 0.3) }.plot(2);
)

But I just realized another thing with this:
the effect of attack and release time args depends
if you take Amplitude with ar or kr,
with kr it's weaker smoothing !


// evaluate and say something within 2 seconds

(
{ Amplitude.ar(SoundIn.ar(), 0.3, 0.3) }.plot(2);
{ Amplitude.kr(SoundIn.ar(), 0.3, 0.3) }.plot(2);
)

// So if the Amplitude signal is needed in control rate you could do this

{ A2K.kr(Amplitude.ar(SoundIn.ar(), 0.3, 0.3)) }.plot(2)


I'm not clear about that behaviour,
I'll ask in a separate thread.


Regards

Daniel

-----------------------------
www.daniel-mayer.at
-----------------------------




_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/