Spogg wrote:Thanks for the explanation Adam. I did think that at first ,but I also saw the wavetable readers had a freq input each, so which one actually determines the pitch of the output? Sorry if this is too fundamental a question but I do like to understand stuff. At least where I think there's a chance for me!
Initially the wavetable reader code should only have one frequency input, but as I mentioned, to save cpu, I stripped out the ramp counter from all of them, and used a global one controlling all. Since the ramp is separate the wavetable reader still needs to know which frequency we are playing at, because it needs that information for the anti aliasing. So we have a freq input for the wavetable reader as well.