Search results

The prepare method also calls the prepare method on each of the Device's inputs (similar to the way getValue calls getValue on all the inputs). For many devices, this would be all the prepare method does, but for some it would have to do more.

The prepare method would be called on the output device before each call to its getValue method.

First thing we do is add a second method to the Device interface, like so: interface Device{ public double getValue(); public void prepare(); }

Well you could do that too, but I have a more elegant solution which is more robust (i.e. if you decide you want to add another waveform, you can just add it without having to go back and change the number you divide by). And that solution is...

Well, you could do it that way, and it would avoid the issue, while being negligibly less efficient. And, if you were having two entirely separate instruments, that would probably be the way to go. However, I was talking about having two different waveforms in the same instrument (a la ptvoice).

Also, I demand an explanation of the connection between Ramsay Bolton and a... *wince* cheese grater.

Nope, the screwy bit is the fact that, since multiple devices are taking input from the oscillator, the oscillator's getValue() method gets called twice per sample frame, resulting in it cycling through its state twice as fast as it should. I'll share my solution whenever I go postcrazy again...

Well, the unusual feature of the block diagram is that it would no longer be a tree - there would be TWO devices taking input from the oscillator instead of just one (unless you had a separate oscillator for each waveform). I'll give you a hint: the way the Java program would fail is that the...

Yes, and, if you added the waveforms like that, then what unusual feature might a block diagram of the synthesizer have which would cause the corresponding Java program not to work (at least with the paradigm I described earlier)?

http://www.mediafire.com/?ta1vof1c5ybyrr2

I actually do, or at least I used to (I kinda stopped like a year or so ago). Hang on...

There were at least two. There was "post yer orgs" and "using music".

You were viewing ancient threads.

Having nostalgia day or something?

aaaaand... I just realized that, for some reason, I don't have those ptcops that I gave to Noxid for use in Hungry Mahins saved on my computer. It seems that they now only exist in pttune format.

I think you win the thread.

It's on my own profile cuz I'm morbidly obese.

http://www.mediafire.com/?hbe56uyn7zzkeia

Tually, since it seems ur online again, I'll drop a hint now. Consider what you might do if you wanted a synthesizer that plays two different waveforms simultaneously, at the same frequency.

For this particular synthesizer, this scheme works perfectly. However, there's a subtle flaw which makes it not work as expected for some synthesizers. I'm going to stop here for now and see if you can find said flaw on your own. A hint or two may be dropped along the way.

To use the synthesizer would then be a matter of, at each sample frame, setting the inputs to their correct values, and then calling output.getValue() and doing something with the result (probably either playing it or writing it to a wav file).

So, to set up the synthesizer, we'd do the following: Input pitch=new Input(); Input volume=new Input(); Oscillator osc=new Oscillator(pitch); Multiplier output=new Multiplier(osc,volume);

We'd also need some way of giving inputs to the synthesizer, for which we have the very simple Input device, which allows the programmer to freely modify the value it outputs: class Input implements Device{ public double value; public double getValue(){return value;} }

The code for the Devices themselves (not specific to this particular synthesizer) would be the following: interface Device{ public double getValue(); } class Multiplier implements Device{ private Device[] inputs; public Multiplier(Device... inputs){this.inputs=inputs;} public double...

Let's see how this would work with the first synthesizer we diagrammed.