thats all well and good if whatever is on the output side of the dsp is
the final destination for your data but surely bouncing it around
between all those dsp chips is going to take time...
> dedicated coprocessor, so you can program your sound output chip to do speech
> synthesis or decompress MP3's. And latency becomes way less of a problem if
> you can dedicate a processor to it. (Think of a DMA channel that can run a
> filter program on the data it's transporting, and boom: you've got a DSP.)
> In theory, anything you can write as a filter that sits on a pipe could be
> done by a DSP, and in the Unix philosophy that's just about everything.
i have a high-end-ish soundcard that has four analogdevices SHARC DSPs
on it. using the (unfortunately windows/mac only) software you upload
synth/effects code to it, draw your signal routing on teh screen, then
control it through midi ports on the back of the card... (or with cubase
or similar.)
its a great system, and as you allude to the latency is fantastically
low. for more info, see http://www.creamware.com/. my card is a bit
old (the "pulsar" model) but all of their cards are built on the same
platform. i believe that with their proprietary bus and more expensive
cards you can use up to 45 SHARCs as one huge synth engine.
these days people are doing much the same thing in software (witness
cubase VST, buzz, fruityloops, rebirth, reason, logic, etc etc) but
while today's athlons et al. are getting fast enough for it there's a
few nice aspects of the dsp solution that make it a clear winner (in my
eyes at least). such as not hearing clicks/jitter when you move the
mouse too rapidly...
j.
-- R N G G "Well, there it goes again... And we just sit I G G G here without opposable thumbs." -- gary larson - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/