[chuck-users] Electronic ChucK

[inventor-66 at comcast.net]

Mike, 

I'm open to any digital control interface that anyone wants to use.  Although I do have to define *some* standards, I'm trying to be as open and flexible as possible.  If you've got an Arduino and you want to connect it to EChucK, then I say go for it.  Just make sure you know what you are doing and don't fry another module, haha.  

Now having said that, I'm planning to actually *sell* PIC processor boards.  The dsPIC I have chosen is $3 US in low quantities direct from Microchip, and for that you get a stand-alone 40 MIPs DSP with 6 channels of oversampled audio in and a few PWM outputs.  That's a lot of processor for three bucks and it is only 18 pins so it is small too.  

The dsPIC is my next circuit board, and it will be programmable to be a do-it-all module.  Whatever you need, a SinOsc, an FFT/IFFT class, a delay line, a multiplier - if you can program it then you can load up one of those modules to do the job.  So some of the more digitally inclined folks will buy a bunch of dsPIC modules and code them up.  Others will prefer to buy true analog modules, both will be available.  

Now, since folks will be learning and using PICs, natually the PIC interface products like USB, UART, RF, etc. will become product options.  But that doesn't mean you can't use an Arduino if you want to do so.  Of course smart technical people, being resourceful and creative, will do whatever they want regardless of the standards I set anyway, lol.  So all I can really do is set standards for *my* boards and ask that people generally try to stick to them unless there is reason to do otherwise.  

I hope that clears things up a bit.  Take care, 

Les
(Inventor)