> I understand what you are saying but that still seems to me a roundabout > way to solving the core of the problem. My thought is if we already have > a capability of low-latency interaction between apps via JACK, we should > rework it so that JACK becomes a powerful kernel daemon which would be > capable of routing signal however we wanted it independent of apps......
Huh? Why? > If there is a better solution to this problem than what was originally > established by OSS, shouldn't we learn from our own mistakes and other's > successes (i.e. core audio and BeOs) and rework the way audio is handled > in Linux? Isn't the BeOS at this point open source? Maybe we could hack > their code and use that as a foundation? The BeOS media kit has its problems and I also think it's hard to program. And no, BeOS is not open source. --martijn
