From: Andrew Gaydenko <a@et...> - 2004-02-25 20:30:40
As it was with "recording dialog eats all CPU", I'd want to continue to browse
your code :-) Now, the aim is to try to understand why JACK-recording behaves
such it bahaves (as was reported some times ago). I'm not C/C++ developer (use
java in everyday work), so it is rather difficult to find right direction. Will
you find some minutes to highlight the issue as you see it?