On Sun, Jun 12, 2011 at 8:30 PM, Aaron Krister Johnson
> PianoTeq doesn't configure things when jack is running. It just detects and
would it be so hard to just run that very simple command i asked
about? you have absolutely no guarantee that the parameters presented
by Pianoteq translate directly into ALSA driver parameters, though
they probably do. i gave you a very, very simple way to make sure of
this but we still seem to be arguing about whether to run it or not.
JACK requires context switching out of the program woken by the device
driver (jackd) to the client (pianoteq) and back again. This tends to
expose just any weakness in your system setup that relates to process
scheduling. When an app (pianoteq) deals directly with ALSA, this
context switching is avoided. Its very cheap computationally
(relatively speaking), but it is subject to system-induced snafus.
>> yeah, its in the backlog at present. its functionality overlaps quite
well, JACK Session springs to mind. this should be taken up on the
jack mailing list rather than here.
Linux-audio-user mailing list