Search results

(I figured as much)

We will have rounded corners on things. And fewer spambots. And that's pretty much it.

Dasu's latest FB status makes a lot more sense now. Well, not really, but at least I know where it came from now.

Umm... dare I ask - like what?

Oh coolio.

tuhroni and cheese Which reminds me - I had us as a side dish with my dinner last night.

Did I kill Kenny?

We could, but I don't have much time at the moment. Tomorrow evening maybe? And in what way am I a bastard?

QFT

I think that's enough for now; next time we'll look at another more interesting and more important use of the Smoother device, which I didn't become aware of until quite a bit later.

In other news, I just now realized that it would be a lot easier, when making those block diagrams, to draw the lines BEFORE drawing the blocks, so I don't have to draw pixel perfect lines.

If the signal input had been something other than 0, the output would have asymptotically approached that value instead.

Then, the line "value+=ctrl*(input-value);" is executed. Since input is always 0, this can be simplified to "value-=ctrl*value;" This can be further simplified to "value*=1-ctrl;" Since ctrl is always .0001, this can be fully simplified to "value*=.9999;" So we can see that value will...

In this method, the values of the variables input and ctrl will always be 0 and .0001, respectively.

First, the number 1 is sent to the constructor, so value starts of as 1. During each sample frame, the Smoother's recalculate() method is called.

Let's look at what is happening internally in the Smoother.

In this diagram, the 0 is the signal and the .0001 is the controller. Notice the 1 in parenthesis on the Smoother block. This is the value that is sent to the Smoother's constructor.

Let's look at a block diagram which uses a smoother for exponential decay.

My original intent in making this device was to allow for easy calculation of exponential decay without the need for an expensive call to Math.pow().

If the controller value is 1, no smoothing is done, and the output is exactly the signal input. If the controller value is 0, complete smoothing is done, which actually causes the output to be a constant value. As neither of these extremes are particularly useful, usually values between 0 and...

Let's look at what it does. It takes two inputs: a signal and a controller. The controller is a value from 0 to 1, which indicates how much "smoothing" to do to the signal.

This Smoother device turns out to be very important, though I didn't realize it at the time.

class Smoother extends VolatileDevice{ private Device signal,controller; private double value; Smoother(double v){value=v;} protected void prepareSources(){signal.prepare();controller.prepare();} protected long recalculate(){ double ctrl=controller.getValue(); double...

I see your obsession with beard growing has at least briefly returned. Postathon time.