[sdiy] Moogey jitter - the old times were the oldest.

[Paul Maddox]

Tim,

> ***********
> Oh I can come up with even more. My Matrix 6 has a sound I love and an
> interface I hate. ;-) However, I was just generalizing.

yep, and that was why it was such a bad point.

> I guess my
> best example would be a patchable system or even something like a
> 2600. The "one knob per function" interface has a lot of appeal for
> hobbyists, and that was my real focus.

you can have too many ;- Jellinghaus programmer?

>> So you're saying, simpler = able to copy?
>>
> *******
> In a word, yup! I think hobbyists are much more interested in circuits
> they can understand and reproduce themselves. I know I am.
> *******

Hmmm, here I differ, sure I like to know something WAS done, but I've little 
interest in reproducing something that has been done before, unless it's to 
help facilitate something new.

> Absolutely agreed! I would LOVE to see more digital projects here.

I'm not even concerned if they're digital/analogue/dsp/chicken with 
microphone, I'd just like to see more 'new' and less 'old'.

> Again, learning to write code is an additional barrier for most
> people, but the rewards are many.

<bangs head on table>
Why IS IT that the mention of the word 'digital' implies codeing and DSP?
Walsh function generators, wavetables and so on, are digital but require 
little if any programming to be done.

> Figuring out the code (even well commented code) for a
> full on AVR Synth or even a CV-MIDI converter is a pretty daunting
> first project.

my first 'bit' of micro was in fact a 4 channel midi 2 cv converter.
the monowave was my first real major chunk of programming, and my second bit 
of coding ever.
Daunting is relative, I knew NOTHING about C programming or micros, but I 
knew what I wanted to do and I did it.

> How about a series of modules that use a micro to do
> just one or two simple tasks? I'd love to see the code to have an AVR
> just do one or two LFOs, or one or two EGs.

I suggested this, a couple of years back, got my head chewed off because it 
wasn't "analogue".
I even suggested a module that would do  several different things, based on 
a couple of jumpers and what knobs/switches you attached, same thing, "its 
not analogue, it'll stink, we don't want it"....

> Now with a micro, you
> could expand the functionality a bit (a micro based LFO could have a
> range and waveforms an analog unit could only dream about), but
> keeping the code simple could make it more appealing to beginners.

Also, check my webpage, you'll find the monowave and PolyDAC source code up 
there for people to see and learn from/expand on. You'll also find the 
monowave II DSP code up there.

One of the biggest problems is that for things like micro based projects, 
people seldom release code, which doesn't help 'de-mystify' the project at 
all..

Let's see more code.

Paul