| Tobiah wrote:
> As Csound comes out of the box, it selects /dev/dsp0
> for both input and output.
Could the -o flag be modified to allow you to really select a device? So
you could say -o /dev/dsp2 ?
> BTW, why can't I pipe csound's output samples into another
> process? It claims 'stdout audio not supported' or something.
> There are some nice purposes for this as well.
Yes, yes, yes! For example, I would like to be able to run a multitrack
recorder app (only takes about 10% CPU time if there's not too many
tracks or effects), and do an overdub track consisting of realtime
output from a simple midi-controlled Csound instrument. If I could do
that, I could be happy until the day I die. I think there's a way I
could do it by running half of a Y-cable into a headphone amp, and the
other half back into the soundcard mixer, and fiddling with the
soundcard mixer carefully; but that's a dumb kludge that adds an
unnecessary D/A -> A/D conversion, and it would still require being able
to select an output other than /dev/dsp0 since the multitrack recorder
is hogging that... No, wait, that won't work: the multitrack is using
/dev/dsp0 AND /dev/dsp1, I think. And it's closed-source and the author
doesn't respond to requests, I've found. :(
Even if I could simply pipe the output to a command-line recorder that
would be enormously useful. Currently, realtime output goes outside the
computer whether I want it to or not.
Another request: can we select a different midi input device? On linux
we have /dev/midi00, /dev/midi01 etc but most apps won't let you use
them...
|