[sugar] Re: ftable issue in csound/sugar
Fri Nov 3 17:34:33 EST 2006
I can see the issue here. The problem is that if the daemon is running
the soundcard will be blocked. I you want to start another app (like a
csound command line) you will be informed that the soundcard is already
There are two 'solutions' to that problem: One is to add dynamic loading
of instruments to csound5, which will take some time even so Barry and I
discussed this already. So for B1 this is not realistic.
The other one is to use the dmix mechanism of alsa to allow to have
virtual devices for your soundcard and are able to use the device from
different apps at the same time.
I had a look at dmix a few month ago and it worked ok - we would have to
test it again in a 'real' situation.
Jean Pich? wrote:
> Since we have now agreed that the csound server will be running
> univorc.csd from startup as a system deamon, a new issue arises with
> table and instrument numbers. We run the risk of encountering Ftable
> number collisions and instrument number collisions between apps.
> For the time being, and as to not get in the way of any instruments
> Barry and Richard are perhaps preparing, we propose to reserve
> instrument #s from 5000 to 6000 and table #s from 5000 to 6000 for
> the exclusive use of TamTam.
> Important: When your app closes, it is important that it free up its
> tables lest it hog ram when its not in use. We do this by running a
> ftfree instrument (instr 5000) in univorc.csd when tamtam exits. We
> need to figure out a way to make a general purpose instrument in the
> univorc.csd to kill any tables on exit. If we have time, we will
> propose a solution that everyone can use. For the trime being, it will
> be up to each application to do its house cleaning. We all agree that
> this is NOT a desirable way to do it and it will be changed for beta-2.
More information about the Sugar-devel