On 11 Aug 2009, at 07:16, Jens M Andreasen wrote:
If anybody would be interested in doing a concerted effort of
optimizing
PCIe transfers in jackd for cross platform CUDA audio processing,
then -
well - I am here, as well as over at the CUDA forums. I imagine
that, as
seen from say qjackctl, this should just look the same as any other
hardware you may have - like a sound-card - with 32 or perhaps 64
channels in/out. What happens at the other side, what those channels
connects to, would be up to the user/programmer. Running several
kernels
in succession, the one piped into the other has very little overhead,
although it might be a better strategy to do different parts of the
scene in parallel on neighboring processors. Very few people who does
not work at TU-Berlin actually needs more than 640 channel strips ;)
If that's what the CUDA interface to the outside world looks like then
wouldn't it be better to expose it as a JACK App, which loads CUDA-
specific plugins onto the graphics card?
I don't see why you'd want to embed it in the jack daemon.
- Steve