How to make a basic signal attenuator
Hey everyone. I think this is really basic, but does anyone know how to make a simple attenuator ? I essentially want a slider/knob to control the amount of signal that is being sent somewhere. The higher the slider, the more signal being put out. When the slider is 0, there should be no signal coming out. Not audio signal, but integers
define "the more".
bigger numbers? or more frequently?
Bigger numbers :)
attach that slider or int box or whatever to sig~
source audio, that isn't working for me. I don't want audio signal . I want event signal in floating point numbers.
I thought that I'd try use a clip object, because that kind of signal limitation is what I'm looking for - where the min/max values can be set with say a slider/knob. But the problem with that, is when the numbers I'm outputting to the clip object reaches the maximum value I've set, the signal stops running until the signal number comes back down to the max. (the event signal is a steady LFO triangle wave in floating point numbers 0. to 1.) So say I set the max value on the clip object to 0.60, the output will stop at 0.60 until the signal goes all the way up to 1. and then back down to 0.60, and from there the clip object is giving output. I want the signal to be constantly running, so I want the frequency at which the numbers are outputting to be relative to the maximum number set, so that the cycle TIME of say 0. until 1. is the same as say 0. to 55. ... Does this make sense?
What is that event signal ?
Never heard of such a thing.
A floating point ?
In your first post you talk about integers
now it is floating signal ...
Are you trying to scale a value ?
then send input to * object with float argument
and multiply it with 0. to whatever maximum needed.

Hey man, thanks, this is what I was looking for. I knew it would be simple. Sorry for the confusion, I'm very new to Max. I use confused terminology like event signal because I come from a modular and Reaktor background... I was meaning floating point the whole time. Apologies and thanks!
Ha, ha that's great that this mistery got solved.
If you have a running oscilator, then pak object would not be necessary.
I put it there so that both sides of the multiplication update the result.
pak is too "pro" for here.
for starters we should do it the traditional way (and learn something about message order and triggering output at the same time)
reaktor user: int signal!
max user: what? int or signal?
reaktor user: i think int. no wait, float.
max user: ah, float numbers. so no signal at all.
c++ user: what´s a "signal"? do you mean stream?
eurorack user: hm, i just connect my music with patch cords and it works.